Style sheets are used with XML documents to define the appearance of the data in the document. The purpose of the style sheet is to allow a single XML document to be re-targeted for different usages and audiences.
Within OnBase, you can assign different style sheets to a Document Type to change the appearance of the document depending on how its being used or viewed. These options are located in the XML Style Sheet Settings dialog box.
If the Keyword-Based XML check box is enabled in the Document Type Settings dialog box, OnBase automatically selects a style sheet for the document based on a specified Keyword Value.
When creating an XML style sheet there are few things that are important to note:
-
The style sheet must be accessible to the user and the workstation that the document is being viewed from via a UNC or URL path.
-
If the style sheet includes images, the style sheet must include the full path (via a UNC or URL) to the image file.
If the document is intended to be distributed via e-mail, images in the style sheet must be available via a URL.
-
If a style sheet is referenced in the XML file and it does not match the style sheet configured in OnBase, the style sheet specified in OnBase overrides the style sheet specified in the XML file.
-
If viewing the XML document in the OnBase Web Client, the style sheet must use UTF-8 encoding.
Note:It is recommended that the following line be placed below the XML declaration in the style sheet to ensure proper viewing: <!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp " "> ]> An example of an XML declaration is: <?xml version="1.0" encoding="UTF-8" ?>
-
Stylesheets that use an <xsl:include> tag are not supported by default, in order to ensure the highest level of security. While it is not recommended to reference external .xsl files, if your solution requires it, you can override this security feature by using the AllowInsecureExternalXsl key and set it to true. This key must be placed in the Application Server's web.config configuration file under the appSettings node.
<add key="AllowInsecureExternalXsl" value="true" />
Note: If you are using the Unity Scheduler’s scheduled service to convert EDI835s to PDFs, the AllowInsecureExternalXsl key must be set to true and placed in the Unity Scheduler’s web.config file as well. However, if the Unity Scheduler is not used for processing using an external .xsl file, the modified key must be placed only in the Application Server’s web.config file.