Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.5.1

Upgrading from Version 9.5.1

Configure Task Triggers For Subject Area Workflow Adapter

Configure Task Triggers For Subject Area Workflow Adapter

You must configure task triggers to use ActiveVOS workflows based on subject areas with the Task Manager. If you do not configure task triggers, the tasks do not appear in the Task Manager.
To configure triggers, use the Provisioning tool to edit the task configuration file from the Advance Configuration page. For more information, see the
Multidomain MDM Provisioning Tool Guide
.
You can configure the following
startWorkflow
attributes to configure task triggers:
process
The name of the ActiveVOS workflow process.
taskKind
Defines the type of user interface required for the process. Can be REVIEW, MERGE, or UNMERGE. The taskKind is returned by the ActiveVOS workflow engine.
taskTemplate
The name of the task template to use.
firstTask Type
The first task in the workflow. Optional. This parameter allows the task to be assigned when the task is created.
Two-step approval code sample
The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter based on subject areas for the two-step approval task:
<trigger name="DefaultApproval"> <startWorkflow process="IDDTwoStepApprovalTask" taskKind="REVIEW" taskTemplate="DefaultApproval" firstTaskType="AVOSReviewNoApprove"/> <event name="CreateBE"/> <event name="UpdateBE"/> <role name="*"/> </trigger>
One-step approval code sample
The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter based on subject areas for the one-step approval task:
<trigger name="DefaultApproval"> <startWorkflow process="IDDOneStepApprovalTask" taskKind="REVIEW" taskTemplate="DefaultApproval" firstTaskType="AVOSFinalReview"/> <event name="CreateBE"/> <event name="UpdateBE"/> <role name="*"/> </trigger>
Update with approval code sample
The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter based on subject areas for the update-with-approval task:
<trigger name="DefaultApproval"> <startWorkflow process="IDDUpdateWithApprovalTask" taskKind="REVIEW" taskTemplate="DefaultApproval" firstTaskType="Update"/> <event name="CreateBE"/> <event name="UpdateBE"/> <role name="*"/> </trigger>
Merge code sample
The following code sample shows the startWorkflow element configuration for the ActiveVOS adapter based on subject areas for the merge task:
<trigger name="Matched"> <startWorkflow process="IDDMergeTask" taskKind="MERGE" taskTemplate="MergeTaskGenerator" firstTaskType="AVOSMerge"/> <event name="MatchedBE"/> <role name="SYSTEM"/> </trigger>

0 COMMENTS

We’d like to hear from you!