Consider the following guidelines and best practices when you design human tasks, processes, and configure workflows.
Human tasks
Consider the following guidelines when you design human tasks in Application Integration:
•Users or roles configured as Potential Owners, Excluded Owners, and Stakeholders when you design human tasks are not considered for workflows. This is because workflow assignments happen dynamically.
•Define AssetName as an input field and configure AssetName in the Display Settings tab as a dynamic parameter in the Subject field. This helps you identify the asset for which the task is created.
•Human tasks in a process must have at least one outcome. You can't select processes that include human tasks without outcomes when you configure workflows in Metadata Command Center.
•Define labels for all human task outcomes. If you don't define labels for outcomes, the name of the outcome appears as a Task Action in tickets. If you define labels, the label values appear as Task Actions.
Processes
Consider the following guidelines and best practices when you design processes in Application Integration:
•Add Milestone as the first step after the Start step in a process.
•Select the Allow anonymous access option in the Start step properties.
•A Start step must have input fields of Human Task Assignment type to assign dynamic roles to each human task when you configure workflows in Metadata Command Center.
•You can map an input field with multiple human tasks based on business requirement.
•Informatica recommends that you make all input fields mandatory so that when you configure the workflow, Metadata Command Center renders the input fields as mandatory.
•A Start step must have an AssetName input field of Text type. This is required to display the asset name on each task created in Data Governance and Catalog after you start the workflow.
•A Start step must have an allStakeHolders input field of Human Task Assignment type. This is required to control stakeholder roles that can view the tasks created for an asset.
•Define a dedicated input field for stakeholder assignment in the Start step of a process and map the Stakeholders task role with the allStakeHolders input field for each human task configured in the process. Based on the roles you select in Metadata Command Center, ongoing tasks are visible to the respective stakeholders when the tasks are generated.
•Output Fields and Temp Fields have no impact on workflow configuration. You can ignore these properties when you configure a process.
•If a process has input fields of types other than Human Task Assignment and Text, ensure that the fields are non mandatory at the process and human task levels. If you make input fields of other types mandatory, you cannot save the workflow configuration in Metadata Command Center.
•Design processes with at least one human task.
•Map the Potential Owners and Stakeholders properties with the correct input fields for each human task configured in the process. If you don't map these correctly, you can't assign dynamic roles to human tasks when you configure workflows in Metadata Command Center.
•Don't include sub-processes in a process.
•If more than one outcome of a human task has common text, Informatica recommends that you use the EQUALS operator in decision-making steps while creating workflow paths. For example, assume that Outcome1 and Outcome2 of a human task are labelled as Approver1 and Approver2. If you include the CONTAINS operator in the decision step with the value "Approver," the navigation of the workflow path at run time can become unpredictable. Instead, if you use the EQUALS operator with a specific value, the workflow operates seamlessly.
•You can select only published processes when you configure workflows in Metadata Command Center.
•To publish a process, the process must be successfully validated. No asset must be in an invalid state. A workflow gets outdated if you modify the published process or the human task included in the published process. Reconfigure the outdated workflow in Metadata Command Center with a valid and published process to start the workflow.
•Republishing a process without changes at the process or asset level does not affect the existing Metadata Command Center configuration.
•If no changes are made at the process or asset level but you rename and publish the process, then the existing Metadata Command Center configuration becomes invalid.
Workflows
Consider the following guidelines and best practices when you configure workflows in Metadata Command Center:
•Map the workflow task outcomes with one of the predefined actions for each human task.
•Configure at least one action of the task outcome as "Publish" when you configure workflows in Metadata Command Center.
•Assign the "All Stakeholders" role to at least one of the input fields to ensure that associated stakeholders can view ongoing workflow tasks. The "All Stakeholders" role allows you to dynamically assign the stakeholders of a human task.
•If an input field is of Human Task Assignment type, map the input field to a role from the Roles list. Ensure that all Human Task Assignments are mandatory at the process level.
•If an input field is of Text type, select "Asset Name" as the asset attribute for the input field. The asset name appears in the Workflow Inbox page, and you can perform a search with the asset name in Data Governance and Catalog. Input fields of Text type are not mandatory at the process level.
•If you select the task outcome as Publish for a human task that starts at the beginning of the workflow, the asset lifecycle status changes to "Published" and the associated ticket moves to the "Resolved" status. Informatica recommends that you map the task outcome of the last human task in a path to Publish. This is to ensure that the asset can only be published after all stakeholders for each human task in that path have responded.