B2023-104 Import procedure and Go To RO
Added a check for a bad RO link when trying to do a Go To RO. A message box pops up telling the user to re-link that RO. Fixed the Import logic so that an old RO link reference can be replaced with the new one that is generated when a procedure is processed during the Import function. The Import caused the Bad RO link reported in this bug. This bug was introduced when the ROID was standardized in length and formatting (new RO logic in 2022).
This commit is contained in:
@@ -4116,6 +4116,11 @@ namespace VEPROMS
|
||||
|
||||
ROFSTLookup lookup = MyDocVersion.DocVersionAssociations[0].MyROFst.GetROFSTLookup(MyDocVersion);
|
||||
|
||||
// B2023-104 use this to replace RO Link information in the imported text
|
||||
// FormatRoidKey() was creating the roid with the new formatting introduce with B2022-088 & B2022-098
|
||||
// We need to save the ROID from the imported text in order to update it with the new RO link information
|
||||
string contentROID = roid;
|
||||
|
||||
// B2022-088: [JPR] Find Doc Ro button not working in Word Sections
|
||||
// B2022-098: [JPR] ROs not being resolved in Word Sections
|
||||
roid = ROFSTLookup.FormatRoidKey(roid, true);
|
||||
@@ -4135,7 +4140,8 @@ namespace VEPROMS
|
||||
rou.Save();
|
||||
|
||||
RoUsageInfo roui = RoUsageInfo.Get(rou.ROUsageID);
|
||||
string lookFor = string.Format("#Link:ReferencedObject:{0} {1} {2}[END>", rousageid, roid, oldRODbID.ToString());
|
||||
//B2023-104 use the ROID from the imported text (contentROID) to create the lookFor string
|
||||
string lookFor = string.Format("#Link:ReferencedObject:{0} {1} {2}[END>", rousageid, contentROID, oldRODbID.ToString());
|
||||
string replaceWith = string.Format("#Link:ReferencedObject:{0} {1} {2}[END>", rou.ROUsageID.ToString(), roid, newRODbID.ToString());
|
||||
_DidProcessROs = content.Text.Contains(lookFor); // B2017-076 RO link in the text so we will be processing it
|
||||
|
||||
|
Reference in New Issue
Block a user