C2026-008 - Re-Architect RO.FST to include RO Modification date/time and use those when updating ROs from the RO.FST #756
Reference in New Issue
Block a user
Delete Branch "C2026-008"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
C2026-008 - Re-Architect RO.FST to include RO Modification date/time and use those when updating ROs from the RO.FST
Note - do not merge this through to development until after testing has completed and this has been signed off on.
A copy of this for testing has been placed here:
V:\Proms Versions\Test Version\Data to use for testing\C2026-008
@@ -13540,35 +13540,7 @@ GOIF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'[deleteAllDocVersionPdfs]') AND OBJECTPROPERTY(id,N'IsProcedure') = 1)DROP PROCEDURE [deleteAllDocVersionPdfs];GODoes the Admin tool Refresh Word Attachments us this? or does it use a different SQL procedure?
Refresh Word Attachments uses "vesp_DeletePDFs" - it doesn't take the doc version id as a paramater.
all looks good.
once testing is successful, it can be merged into development
updated changes look good. Will hold off on merging into development until after preliminary testing is completed.
Ready for Review again - but hold on merging into Dev until testing complete.
updated changes looks good
Testing has been completed with version 2.6.2605.1506. Everything works as expected with one item that occurs for me which is Test 5 from the April 15 Word document. When the program is stopped via task manager and I go back to update RO values, they are not updating. However, it does work when Matt does it. It is occurring in a table that I modified, but other updates are working and when this is done on another machine, it does work. Therefore, I'm considering testing complete after discussing with Matt and Devin. The original testing document from April 28 was updated by me during testing and is attached.