C2026-008 - Re-Architect RO.FST to include RO Modification date/time and use those when updating ROs from the RO.FST #756

Open
mschill wants to merge 8 commits from C2026-008 into Development
Owner

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

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
djankowski was assigned by mschill 2026-04-28 09:13:19 -04:00
jjenko was assigned by mschill 2026-04-28 09:13:19 -04:00
mvickers was assigned by mschill 2026-04-28 09:13:19 -04:00
mschill added 1 commit 2026-04-28 09:13:20 -04:00
mschill requested review from jjenko 2026-04-28 09:13:20 -04:00
mschill added 1 commit 2026-04-28 13:43:37 -04:00
jjenko reviewed 2026-04-28 14:07:37 -04:00
@@ -13540,35 +13540,7 @@ GO
IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'[deleteAllDocVersionPdfs]') AND OBJECTPROPERTY(id,N'IsProcedure') = 1)
DROP PROCEDURE [deleteAllDocVersionPdfs];
GO
Owner

Does the Admin tool Refresh Word Attachments us this? or does it use a different SQL procedure?

Does the Admin tool Refresh Word Attachments us this? or does it use a different SQL procedure?
Author
Owner

Refresh Word Attachments uses "vesp_DeletePDFs" - it doesn't take the doc version id as a paramater.

Refresh Word Attachments uses "vesp_DeletePDFs" - it doesn't take the doc version id as a paramater.
jjenko marked this conversation as resolved
jjenko approved these changes 2026-04-28 14:24:01 -04:00
Dismissed
jjenko left a comment
Owner

all looks good.
once testing is successful, it can be merged into development

all looks good. once testing is successful, it can be merged into development
mschill added 1 commit 2026-05-11 14:41:06 -04:00
mschill added 2 commits 2026-05-11 14:41:33 -04:00
mschill requested review from jjenko 2026-05-11 14:42:39 -04:00
jjenko approved these changes 2026-05-11 15:10:19 -04:00
Dismissed
jjenko left a comment
Owner

updated changes look good. Will hold off on merging into development until after preliminary testing is completed.

updated changes look good. Will hold off on merging into development until after preliminary testing is completed.
mschill added 1 commit 2026-05-12 08:52:25 -04:00
mschill added 1 commit 2026-05-14 10:40:02 -04:00
mschill added 1 commit 2026-05-15 07:07:24 -04:00
--Fix for Blank popup box when completes updating ROs through Admin Tool & fix for updating ROs when fails part way through (if network error, etc…)
mschill requested review from jjenko 2026-05-15 07:08:07 -04:00
Author
Owner

Ready for Review again - but hold on merging into Dev until testing complete.

Ready for Review again - but hold on merging into Dev until testing complete.
jjenko approved these changes 2026-05-15 09:26:19 -04:00
jjenko left a comment
Owner

updated changes looks good

updated changes looks good
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin C2026-008:C2026-008
git checkout C2026-008
Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Volian/SourceCode#756