This tutorial uses an EDI development workflow as an example of a complex business process implemented in ]po[
Working Message QC Approval Solution Support Technical Review QA Business Analyst UA Approval User Acceptance Release to Production MTP Success Project Finished 30 Days Maintenance and Solution Support Approved Project Business Analyst Message “Map” Message Developer Specs OK Report Specs not OK Message Developer Develop Message Check Specs Business Analysis QC Check Internal QC Team QC not OK Message Developer QA not OK UA not OK slow
The workflow “Inbox” contains a list of all assigned and otherwise associated workflow tasks in the user’s home page.
The inbox also contains the user’s own objects, so a user can track what is happening to his approval requests etc.
Action: The name of the Transition
Type: Name of the workflow
Status: Status of the underlying object
Assignee: Who else is assigned to the current transition?
Owner: Owner of the underlying business object
Object Name: Name of the underlying business object
Relationship: What is the relationship between the current user and the workflow? “Assignment Group” means that the current user is assigned (task), “My Object” means that the underlying biz object has been created by the current user (tracking). Only WF admins can see tasks with relationship “none”.