This documentation supports the 21.3 version of Action Request System.

To view an earlier version, select the version from the Product version menu.

Exporting and importing shared workflow and integrated applications

Shared workflow is any workflow associated with forms both inside and outside the deployable application. When this is the case, the primary form determines the "owner" application for the workflow.

When developing deployable applications as modules of a larger application, you might need to have developers working concurrently on separate development servers. In this situation, previous releases of AR System server  required you to export and import any shared workflow not owned by the application separately, or to install all related deployable applications on each development server.

You can use the following features to help manage cross-server development of integrated deployable applications:

  • Include Shared Workflow option—Use this option in the Export wizard in Developer Studio  to include shared workflow not controlled by the application in the application definition file. See Exporting shared workflow not owned by the application below.
  • Create-Workflow-Placeholders configuration option—Set this option in the configuration file of the destination development server to allow the creation of placeholder forms for any external forms associated with shared workflow. See Importing shared workflow not owned by the application below.
  • Workflow Integration property for workflow objects—Set this property to allow the Export wizard to export only the integration workflow for two deployable applications.

In addition, when you import shared workflow that is owned by the application, the full list of associated forms, including those owned by another application, is now preserved.

Exporting shared workflow not owned by the application

Workflow that is in the application but not owned by the application is any workflow object whose primary form is in another application, but which is also associated with a form in the current application.  For example, consider the deployable applications and objects described in the following table:

AppA

AppB

FormA

FormB

ActiveLinkA is associated with FormA its primary form

ActiveLinkA is also associated with FormB (a secondary form)

In this example, AppA owns FormA and ActiveLinkA. Both objects are exported with AppA by default because they are owned by it. AppB owns FormB but not ActiveLinkA. By default, ActiveLinkA is not exported with AppB, but by using the Include Shared Workflow option of the Export wizard, you can include ActiveLinkA when you export AppB.

To include all shared workflow when exporting an application

  1. In AR System Navigator, right-click the application to export in the Applications list, and then select Export Application.
  2. In the Application Selection dialog box, enter a path and file name for the application definition file, and then click Next.
  3. In the Export Options dialog box, select Entire Application and Include Shared Workflow.
  4. Click Finish.
    The application is exported and any shared workflow not owned by the application is included in the definition file.

Importing shared workflow not owned by the application

When you import an application definition file that contains shared workflow not owned by the application, AR System server  can create a non-functional placeholder form for each external form associated with the shared workflow. This allows developers to modify the shared workflow owned by another application without installing the integrated application on the development server. It also ensures that the complete list of associated forms is preserved with any shared workflow.

Placeholder forms are created during application import in these cases:

  • The import definition contains shared workflow from another application that includes a Push Fields or Set Fields action. In this case, a placeholder is created for the external form used by the Push Fields or Set Fields action.
  • When the server configuration file (ar.cfg or ar.conf) contains the option Create-Workflow-Placeholders: T, a placeholder form is created for any external form associated with the shared workflow, regardless of the workflow action type. If the value is missing or is deleted from ar.cfg or ar.conf, it will be treated as False. The default value of Create-Workflow-Placeholders option is False.

A placeholder form has no fields and can only be deleted. If the actual definition of a placeholder form is imported, it replaces the existing placeholder. In the Forms object list in Developer Studio , placeholder forms are identified as form type None

When importing an application definition that contains shared workflow not owned by the application, the workflow object is created if it does not already exist. If the workflow object already exists, only the list of associated forms is updated. If the application that owns the shared workflow object is later imported, the workflow is replaced.

Was this page helpful? Yes No Submitting... Thank you

Comments