1. Orchestrator Guide for Studio Version 8 and Prior
  2. Configuring Form Request and Data Request Processing

Configuring Form Request and Data Request Processing

In the Orchestrator Studio, you can configure settings that control how the AIS Server processes a form request or data request in an orchestration at runtime.

For form requests, these settings are available from the Options icon at the end of the first row of each form listed in the Available Actions grid.

For data requests, these settings are available from the Options button on the Data Request design page.

The settings include:

  • Maximum Records. 0 is for All Records.

  • Query Name. From this drop-down list, you can select a predefined query to use for the filtering criteria. You can use a query instead of or in combination with the filtering criteria defined in a data request. The queries that you can see in this list are based on UDO security permissions.

  • Output Type. Select one of the following format types for the format of the JSON response. Formats include:

    • Default. The default format is Version 2 output type for version 1 orchestrations (orchestrations created prior to Orchestrator Studio 5.0.1). The default format is Grid Data output type for version 2 orchestrations (orchestrations created in Orchestrator Studio 5.0.1 and higher).

    • Grid Data. Returns grid data in simplified name-value pairs. This is the default output type for version 2 orchestrations (orchestrations created in Orchestrator Studio 5.0.1 and higher).

    • Version 2. Returns cell-specific information for each grid row as well as information about each column such as column ID, whether it is visible, editable, and so forth. This is the default output type for orchestrations created prior to Orchestrator Studio 5.0.1, which are referred to as version 1 orchestrations.

  • Stop on Warning check box (form requests only). Click this check box if you want the processing to stop if the invoked EnterpriseOne form produces a "Warning" message. Keep this check box clear if you want processing to continue after a warning message.

  • Turbo Mode (form requests only). Use this option to reduce processing time of form requests. See "Using Turbo Mode" in the JD Edwards EnterpriseOne Application Interface Services Client Java API Developer's Guide for more information.

  • Caching: Allow. Click this check box to enable caching of the service request response. If the "Enable Caching by Default" option is enabled in Server Manager, this parameter is ignored and all responses for Read operations will be cached.

  • Caching: Force Update. Click this check box to force the system to fetch the data from the database for the service request. If the "Enable Caching by Default" setting is enabled in Server Manager, then this parameter for the individual service request is ignored.

  • Caching: Time Stored - Milliseconds. Enter the amount of time in milliseconds for the service request to use the cache for the response. This setting overrides the value in the "Default Read Cache Time To Live" setting in Server Manager.