Secured scripting for Reports

You can execute Optiva Scripting functions in a secured mode. This feature limits the amount of damage a malicious user could inflict should they gain access to your scripts by running all scripting in a “sandbox” environment that has very limited permissions. Customers who are concerned about security or who are exposing Optiva to the internet should consider running in this mode.

A parameter in the Web.config file controls whether you run Scripting in a secured or unsecured environment. For complete details, see the Infor PLM for Process Installation Guide.

In “secured” scripting mode, the workflow is not allowed to communicate directly with the Report Server. Instead, it must use these API’s to complete these tasks:
  • SaveReportData - Sends.xml files to the Report Server.
  • SaveReportSchema - Optionally, send .xsd files to the Report Server.
  • ReadReportFile - Retrieve any files (e.g., .xslt files) that are required by the workflow.

    These API’s require you to configure the name of your Reporting Server in the Web.config file. You must also expose two shared folders on the Report Server: SessionXml and Source. On the Report Server, these folders are within the FsWebReports folder.

    For more information about the parameters in the Web.config file and to learn how to expose the SessionXml and Source folders, see Infor PLM for Process Installation Guide.

    For more information about these APIs, see theInfor PLM for Process Scripting Administration Guide.