Properties View XSLT Tab

Use the Properties view XSLT tab to specify the location of your XSLT file so the predefined automation plug-in can access it. This tab appears for all plug-ins except for custom plug-ins.

You can use XSLT to perform some business logic against a task, and determine the exit status based on the processing results. XSLT enables you to model complex calculations, such as date-based calculations, mathematical expressions, calls to external systems, and so forth. Additionally, you can update the order data with the results from your XSLT calculations. Finally, you can use the XSLT style sheet to transform data when sending and receiving data from external systems.

Field Use

Script

Specify which XSLT style sheet you want to use to transform documents. Select from the following options:

  • Bundle in: Select this option, then click the Select button to identify a style sheet from the resources directory. Design Studio will bundle this XSLT file with the PAR file during the build.

  • Absolute path: Select this option and enter the physical location of the XSLT file. At run time, OSM retrieves the file from the server.

  • URL: Specify a URL to access the file.

Note: Oracle recommends that you select Bundle in for production mode, as this mode pulls the XSLT files into the OSM PAR file. As a result, you can deploy the EAR file (which contains the PAR file) to any server and, at run time, the application can locate the XSLT files. If you select Absolute Path or URL for production mode, you can deploy the EAR file (which contains the PAR file) to any server but are responsible for ensuring the XSLT files reside in specified location on the server.

Absolute Path or URL are optimal for testing mode because they do not require a rebuild and redeploy to pick up changes to the XSLT.

Maximum Number in Cache

Specify the maximum number of XSLT style sheets that can be maintained in the cache at any one time.

Cache Timeout

Enter the number of seconds before the OSM server refreshes the cache.

Exception

Select the exit status that the plug-in should use if it throws an exception. Status options include any status values you assigned to the task.

Note: This field does not apply to an automation plug-in for an order milestone automation event notification (at the order level); it applies to setting up an automation at the task level.

Transformer Factory

(Optional) If you have developed a custom TransformerFactory for XSLT transformation, specify the location. Design Studio provides a default TransformerFactory.

Update Order

Select this option if you want to update (add, change, or delete) the OSM order data with the data retrieved from an external system. This field appears for Automator automation plug-ins only.