You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where rules-extension style advanced flow rule names include selected attributes enclosed in <> (e.g. ,, etc.) these are being stripped from the Attribute Flows table in the HTML report (Mapping Type column).
e.g. a VB rules extension file might have the following code under the MapAttributesForImport mapping to the advanced flow rule cd.user:<dn>->mv.person:domain:
Select Case FlowRuleName
Case "cd.user:<dn>->mv.person:domain"
...
However, in the HTML report this will appear (incorrectly) as the following Attribute Flow:
Rules Extension - cd.user:->mv.person:domain
The downside of the report doing this is that searches of the code base for the above Rules Extension name will return no matches.
The text was updated successfully, but these errors were encountered:
I just realised that in the act of writing up the issue above, I discovered that the same happens with the markdown text ... I could only get my text appearing correctly by HTML-escaping the < and >
I can also confirm that in the raw HTML I can see the problematic (unescaped) text is present in the td innerHtml ... so this is simply a rendering issue where we there should be an HTMLEncode applied to such strings to ensure they are rendered correctly (visually) in the browser.
Where rules-extension style advanced flow rule names include selected attributes enclosed in <> (e.g. ,, etc.) these are being stripped from the Attribute Flows table in the HTML report (Mapping Type column).
e.g. a VB rules extension file might have the following code under the MapAttributesForImport mapping to the advanced flow rule cd.user:<dn>->mv.person:domain:
Select Case FlowRuleName
Case "cd.user:<dn>->mv.person:domain"
...
However, in the HTML report this will appear (incorrectly) as the following Attribute Flow:
Rules Extension - cd.user:->mv.person:domain
The downside of the report doing this is that searches of the code base for the above Rules Extension name will return no matches.
The text was updated successfully, but these errors were encountered: