B2017-019 Don’t cook applicability ROs (ex <u>) when displaying for editing

B2017-019 handle <u> in DisplayNumber
This commit is contained in:
John Jenko 2017-01-30 19:44:25 +00:00
parent 8defa23e65
commit 13ade8e0b7
2 changed files with 2 additions and 3 deletions

View File

@ -291,7 +291,7 @@ namespace VEPROMS.CSLA.Library
text = DoReplaceWords2(text);
ProfileTimer.Pop(profileDepth1);
}
if (_MyItemInfo != null)
if (_MyItemInfo != null && ROsShouldBeAdjusted) // B2017-019 - added check for ROsShouldBeAdjusted so that these token are not "cooked" on property pages
{
text = Regex.Replace(text, @"\<U\>", _MyItemInfo.MyDocVersion.DocVersionConfig.Unit_Number, RegexOptions.IgnoreCase);
text = Regex.Replace(text, @"\<(U(-|\\u8209\?)ID)\>", _MyItemInfo.MyDocVersion.DocVersionConfig.Unit_ID, RegexOptions.IgnoreCase);

View File

@ -2567,8 +2567,7 @@ namespace VEPROMS.CSLA.Library
//if (str.Contains(@"<S\u8209?ID>"))
// str = str.Replace(@"<S\u8209?ID>", MyDocVersion.DocVersionConfig.Unit_ID);
str = ConvertToDisplayText(str);
if (str.Contains("<u>"))
Console.WriteLine("it is still there");
str = Regex.Replace(str, @"\<[uU]\>", MyDocVersion.DocVersionConfig.Unit_Number); // B2017-019 - process "<u>" in section number
return str;
}
//get { return ConvertToDisplayText(MyContent.Number); }