Processing Settings

The settings include:

• Application Stack. (Options menu for form requests.) Application stack processing enables the form request to establish a session for a specific application and maintain the session across calls. With application stack processing, the form request can invoke multiple forms in different applications to complete a business process. Without the application stack processing, each form in the form request is opened independently.

  If you use the Application Stack option, you must configure the form request with the actions to navigate between forms. Without this navigation, additional forms will not be called. There are other considerations when selecting values to return from forms in an Application Stack, as described in Configuring Form Request Actions.

• Return Data From All Forms. (Options menu for form requests.) Enabled by default if Application Stack is not enabled. This option specifies whether to return data from all forms or just the last form.

• Run Synchronously. (Options menu for form requests.) Enabled by default, this ensures that the form request completes all actions before the Orchestrator executes the next step in the orchestration. It also ensures that the events in the EnterpriseOne application are run synchronously. This option is recommended if there are steps that follow the form request in the orchestration or if you configure the form request to return a response.

  Note: If the form request involves invoking a control that launches an asynchronous report or any long running process, it is possible that the Orchestrator could time out if Run Synchronously is enabled.

• Maximum Records. 0 is for All Records.

• Page Size. 0 is for Disabled. For a form request, page size is only available if the form request is defined as an application stack.

  The page size value works directly with the max records value:

  Max Records	Page Size	Behavior
  0 - All records	0 - Paging is off	System will attempt to get all records in one request.
  0 - All records	>0 - Size of page defined	System will attempt to get records in sections for the defined page size until it gets all records.
  >0 - Set number of records	0 - Paging is off	System will attempt to get the max number of records defined all in one request.
  >0 - Set number of records	>0 - Size of page defined	System will attempt to get records in sections for the defined page size until it gets to the number of max records defined.

• 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.