This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Using join forms in workflow

When you use join forms in workflow, all of the typical execution conditions that apply to objects in non-join forms also apply.

To enable the "data entry" functionality of a join form, data created or updated for a particular field must be associated with the appropriate database. The administrator must create workflow that defines how data should be pushed into the database when entered through join forms.

Filters and join forms

Filters are used to enforce the integrity of the system. When you use filters with join forms, the filters for the join form execute first, and then the filters for the underlying forms execute.

The following figure illustrates the execution order of the join forms and their primary and secondary forms.

Execution order of filters with join forms
(Click the image to expand it.)



As you go down the execution order of the filters, all of the forms on the left side (the primary forms) execute first, and then forms on the right side (the secondary forms) execute. For more information, see Filter processing in BMC Remedy AR System server.

Transaction control in database operations

All of the operations performed on join forms, such as querying, displaying, and workflow operations, are executed as a single database transaction. For example, if you update data in one form that affects the data in multiple forms, all of the changes are performed as a single transaction in the database. This process ensures the integrity of the information.

The completion of the database transaction for a hierarchy of forms is all or none. For example, in Joining several forms, if a filter returns an error on form I, none of the updates for the other forms is written to the database.

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

Comments