• State Verified Answer
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 1039 views
  • Users 0 members are here
Options
Related

Modern Request Properties as Fix with Value of HTML content

Ben

Is there anyway to stop HTML escaping of a Value for a Fix request property, or does the Angular side always escape it?

I dunno, something like:

Value.AsHTML = "<ol><li>List item 1</li><li>List item 2</li></ol>"

The main ones we really need are a, ol, ul, li, p and br.

Our use case is providing detailed information of specific requests to the end user by using request properties. But that information needs to be presentable as well as offering direct links to external resources.

The fact that "Description" of the request properties is not displayed in any fashion on the UI makes the UX a terrible one without useful guidance.

Parents
  • +1

    Hello Ben,

    Description fields are plain-text only. Angular escapes any HTML code by default, you can bypass this by customizing the Angular application code at your own risk.

  • 0 in reply to Hanno Bunjes

    Thanks  

    If the field's "description" was displayed with the field in Angular, this would assist (even though it is plain text).

    I was hoping for a similar option as to email templates (i.e. $Script(CCC_CustomFunction):HTML$) where certain strings, when specified, could be excluded from escaping. Obviously if the Angular code is doing it, then this is a problematic need.

    We've been using ReadOnly User Prompts that write a static Value in the Valuation script to provide static content to the end user, but this limits use with regards to email addresses and links to other resources.

Reply
  • 0 in reply to Hanno Bunjes

    Thanks  

    If the field's "description" was displayed with the field in Angular, this would assist (even though it is plain text).

    I was hoping for a similar option as to email templates (i.e. $Script(CCC_CustomFunction):HTML$) where certain strings, when specified, could be excluded from escaping. Obviously if the Angular code is doing it, then this is a problematic need.

    We've been using ReadOnly User Prompts that write a static Value in the Valuation script to provide static content to the end user, but this limits use with regards to email addresses and links to other resources.

Children
No Data