Allow URL links via Content Viewer

[suzie.devaughn]

HTML Content Viewer – Provide an option to enable links within the html email body source.  Currently these links are suppressed for security reasons.   Clients are receiving high volumes on emails ingested into Chorus providing links to additional information instead of including attachments.

We have tried these work-arounds and none of them provide a good user experience

1. Open in the default HTML CV, then select the option to open in native – which downloads it, requires a double click to open it, then launches a new tab where we have to manually close it later.
2. Create a resource to open in the native HTML application – which automatically downloads it and opens it in a new tab, where we still have to manually close it later.  But this is an all or nothing option.  Even for sources that don’t have links. 

Use an “EQM flow” where a service operation can retrieve the html source and load it into an “external” form so that the user can reply to or forward that original email as part of the workstep.  Although we don’t have a requirement to reply to our forward the email as part of this step, we determined that it doesn’t enable the link either.

[Karen_Hunter]

Monitoring site for votes and impact/value statements to support prioritization.  Adding Use Case to the Product Plan Watch list.  Beginning assessment of security risk to the environment.

Today, Content Viewer disables links contained in an html source as a security measure.  This enhancement request is to establish a secured resource that would allow those users with sufficient security the ability to, on-demand, enable the link within the viewer to support the business process.

BPMCM-I-5