CDR Tickets

Issue Number 5258
Summary New Macro to SWAP CDR IDs of Summary Fragment Refs
Created 2023-06-27 17:56:00
Issue Type User Story
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2023-07-05 16:02:58
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.349767
Description

As a summary editor, I would want to be able to run a CDR macro on a new draft summary, to swap the (internal) Summary Fragment Ref ID (CDR ID) of the existing (old) summary to the CDR ID of the new or draft summary so that I can save time without having to change each one manually.

When a summary needs to be comprehensively revised or reformatted, the existing (old) summary is copied in almost its entirety into a newly created summary. The copying brings along all the CDR IDs of the existing summary including the Summary Fragment Refs.  Keeping the (old) IDs in the newly created summary makes the link targets in reports go to the old summary. To prevent this from happening, the CDR IDs are manually changed, or the Summary Fragment Refs are recreated. This macro, like the Spanish ID Swap macro, will save us a lot of time by programmatically replacing the CDR IDs so that they reference the current summary.

Scenario: CDR has the ability to swap summary fragment ref ids

Given: I am a CDR summary editor

  And I have permission to create or edit summary documents in the CDR

When I create a new a new draft summary

  And I copy the content of an existing summary into the new summary

Then I want to be able to run a macro that will swap the CDR IDs from the old summary to the new summary

Comment entered 2023-07-05 16:02:58 by Kline, Bob (NIH/NCI) [C]

Installed on CDR DEV. Ready for testing. As a reminder, this is a release-independent change, so we'll march it up the tiers, and once it's on PROD we'll merge it into the master branch so we can clear the decks for the next CDR XMetaL macro change.

Comment entered 2023-07-06 13:24:51 by Osei-Poku, William (NIH/NCI) [C]

Verified on DEV. Ready for QA. Thanks!

Comment entered 2023-07-06 14:47:35 by Kline, Bob (NIH/NCI) [C]

Installed on QA. Once you have verified it there, we can deploy to STAGE and PROD.

Comment entered 2023-07-07 11:43:42 by Osei-Poku, William (NIH/NCI) [C]

Verified on QA. Please install on PROD (and STAGE).  Thanks!

Comment entered 2023-07-07 13:29:26 by Kline, Bob (NIH/NCI) [C]

Installed on STAGE and PROD. Please verify and close.

Comment entered 2023-07-10 11:04:01 by Osei-Poku, William (NIH/NCI) [C]

Verified on PROD. Thanks!

Elapsed: 0:00:00.001792