Load the EnterpriseOne Application Form Fields and Controls

1. In the Available Actions area, complete the following fields:

   • Application. Enter the application ID.

   • Form. Click the drop-down list to select the form.

   • Version. Enter the version ID.

     If you leave Version blank, the Orchestrator will use the default version when it executes the form request.

     Starting with Orchestrator Studio 6.1.0, leaving the version field blank with the Application Stack option selected gives you the option to pass in the version from an orchestration input. This enables you to configure an orchestration that includes rules with conditions so that clients can call different versions dynamically.

     When you add the form request to an orchestration, click the Add Inputs to Orchestration button to add the variable representing the version to the Orchestration Inputs area. The variable is displayed with the application ID followed by _Version, for example P03013_Version.

2. Click the Form Mode drop-down list and select the appropriate form mode: Add, Update, or Inquiry.

   At runtime, the controls that appear on an EnterpriseOne form are dependent on the form mode as specified in Form Design Aid (FDA). The form mode ensures that you can see all of the form controls in the Orchestrator Studio that are available in the form at runtime.

3. Select the following options as appropriate:

   • Application Stack. Application stack processing enables the form request to establish a session for a specific application and maintains 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.

   • Run Synchronously (Orchestrator Studio 6.1.0). 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.

     Caution: 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.

   • Bypass Form Processing. This option enables the form request to ignore event rules when loading the form fields and controls in the Available Actions grid. For example, some forms have event rules to perform a find on entry or hide certain fields, which can cause the load to fail or prevent certain fields from loading in the Available Actions grid.

4. Click the Load Form button.

   The Orchestrator Studio loads the controls and fields in the grid. The name of the form is displayed in the first row in the grid.

   If a form request needs to invoke more than one application to complete the desired task, you can load controls and fields for additional application forms as needed.