Below is a sample workflow of project status changes. A Project Accountant creates a project and manually sets the project status to Submitted. The workflow process is initiated. A Project Accounting Manager (Project Accountant’s HR supervisor) receives an email requesting his/her approval of a new project. If the manager approves and the workflow process is successful, the project status is changed to Approved.
Similarly, when a project needs to be closed, the Project Accountant will manually change the status from Approved to Pending Close. A second workflow process sends an email to the PA Manager, verifies that the manager approved the project closure, and changes the status to Closed.
Following are the required configuration steps to enable the Project Status changes by Workflow:
Enable Project Types for Workflow Project Status Changes
As Project Billing Superuser, navigate to Setup > Projects > Project Types. Define your project type, or update an existing one. Select the ‘Use Workflow for Project Status Changes’ flag to initiate Workflow for all workflow-eligible project statuses in projects with this project type.
Project Statuses for Workflow Status Changes
As Project Billing Superuser, navigate to Setup > System > Statuses. In our example above, we would need to enable following statuses for workflow: Submitted and Pending Close. The value for Item Type is always ‘PA Project Workflow’ for Process is ‘Project’. Using the Success Status and Failure Status is how you control the next status based on the approver’s action.
Few comments in closing. Using the Project Status Change Workflow is great if you create and approve a lot of projects, or project creation is de-centralized. It enforces consistent rules and keeps an audit trail of changes. Having an automatic emails and notifications sent out by the system brings transparency to the process.
Some of the features we did not like included users’ inability to â€withdraw” a project status change. Once you choose a project type that is enabled for workflow, the process is triggered and you cannot “roll it back”. Also, and this applies to any Oracle Workflow notification, if there is anything wrong with your setup, for instance an employee does not have a HR supervisor, or user account is not associated with an employee, or user name changes were not synchronized in the Workflow tables, the approval notifications are routed to SYSADMIN without any acknowledgement to you.
The workflow messages can be little misleading. After a successful status change, the message always says “Project Approved”, even though the status change was to close the project. It would be more meaningful to say: “…project status was successfully changed to ‘actual status name’…”