Task Engine 10.11 | Task Engine Webhelp | webMethods Task Engine User's Guide | Administering Tasks | Administering Task Types | Administrative Considerations for Task Publishing | Considerations When Publishing Task Types with Duplicate Names
Considerations When Publishing Task Types with Duplicate Names
In some instances, it may be necessary to create two or more task types with the same task type name. For example, multiple process models might contain a user task step named “Cancel Order”, but, to accommodate different conditions in the order processing workflow for different departments, a different task type is implemented and invoked for each process model.
Programmatically, this is not a problem because the Task Engine tracks each task type by its task type ID, not its task name. However, the existence of duplicate task type names in the My webMethods user interface has two major ramifications:
*You will encounter problems when you publish task types with duplicate names unless you take the task editing precautions described below. Specifically, the most recently published task type will overwrite any existing task type with the same task type name.
*Duplicate task type names could be potentially confusing to task users. This would be especially true if multiple custom task inboxes are present, all with identical names.
For these reasons, whenever a task developer creates a task type with a duplicate name, before publishing the task type, the developer must use the task editor to manually rename the task application root page to make it unique among all tasks deployed to My webMethods Server; otherwise, the most recently deployed duplicate task type will overwrite the existing task application pages. This will also ensure that custom inbox page names will be unique. For information about modifying the task application root page, see webMethods BPM Task Development Help.
In addition, the Advanced tab of the My Inbox and Task List Management pages enables a user to filter the task results by task type name. In the event of task types with duplicate names, the list will contain an entry for each duplicate name, potentially making it difficult for the user to select the desired task. To alleviate this problem, the user can hover the cursor over a task name entry in the list; this displays a tooltip that contains the task type description text entered by the task developer as well as the unique task type ID.