Web Determinations supports customization of the user interface displayed to users via the entry of HTML content for controls. In order to use this feature it's recommended that users have a basic working knowledge of HTML and web development. A good primer is available at http://www.w3schools.com/html/ .
Entry of HTML tags in this manner has certain security implications and by default the modeling and web determinations applications limit the set of HTML tags that can be entered via a whitelist. If extra HTML tags are required then this is configurable in both applications.
This whitelist in modeling is configurable via File > Project properties; Common Properties > General and then in the Web Determinations section HTML tags allowed in screen content field. If a tag is used that is not in this comma separated list, then a build error will occur. The error reads "The HTML tag 'tagname' is not an allowable HTML tag for use in a caption"
The current set of tags allowed are any of the following "b,i,del,s,div,p,span,pre,table,td,tr,ol,ul,li,blockquote,font,a,h1,h2,h3,h4,h5,h6,img,hr,br"
By default the set of tags includes tags that are known to not have security implications and can be safely displayed in Web Determinations. Notable absence is the 'script' tag which means javascript cannot be entered via the IsHTML option. If a tag is required that is not in the default set, it can be added by adding it to the list; for example, including the script tag would result in the following content "b,i,del,s,div,p,span,pre,table,td,tr,ol,ul,li,blockquote,font,a,h1,h2,h3,h4,h5,h6,img,hr,br,script"
As Web Determinations is deployed as an application which can host many rulebases, it has certain security requirements and if the tag is not supported it will fail to load the rulebase. If an additional tag is required then the tag is also required to be added to the whitelist for the Web Determinations application.
This is configurable in the application.properties and the property 'screens.html.tags.whitelist' property. If html validation should be turned off in entirety it can be turned off by setting the 'screens.validate.html' property to false
By default it looks like:
# Screens file content can include html authored by users in oracle policy modelling as static content.
# These options determine whether to scan the content at application start time and verify that the
# tags deployed in the rulebase are in the whitelist of allowable content.
screens.validate.html =true
# any tag not on this list will cause an exception to be thrown during rulebase loading and the rulebase will not be available.
# if additional tags are required they must be added to this list.
screens.html.tags.whitelist =b;i;del;s;div;p;span;pre;table;td;tr;ol;ul;li;blockquote;font;a;h1;h2;h3;h4;h5;h6;img;hr;br