Using BMC Remedy AR System, you can build a set of workflow operations once and then reuse the workflow across multiple forms. From an application standpoint, it is important that you build your workflow so that it can be shared by multiple modules and applications. To accomplish this, the workflow must use field IDs that are unique across all forms.
If the workflow can be called at different times, it should be encapsulated in a filter or active link guide so that the base code can be shared and specific code can be used to call the workflow (this makes the workflow more function-oriented). Building code in this manner makes the footprint of the application smaller because a smaller number of active links and filters exist in the application. Also, this approach makes the code easier to maintain because changes can be made in one place rather than in multiple places. For more information about guides, see Business logic objects.
When assessing your reuse, BMC suggests that you ask the following questions:
- Can this function exist in other forms or other applications?
- Are the fields used in this function unique across forms?
- Are the fields registered?
- Does the naming convention of the workflow indicate that it is shared (if it is a shared piece of code)?
- Is the workflow encapsulated in a guide so that it is easier to see the functionality grouping?