Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 36 Working with the Approval Workflow in RMS : Working with the Approval Workflow—Overview

Working with the Approval Workflow—Overview
When business users have finished working with artifacts (decision tables or business rules), they submit them for approval. All business user actions, such as committing or deleting artifacts are committed to the RMS project only when a user whose role gives permission to do so approves the requests.
The approval permissions are set at project level using the ACL file for the project. Allow the approval action type for the user role in the ACL file to grant approval permission. See TIBCO BusinessEvents Administration for details on setting permission for a user role at project level.
This section explains the provided workflow for approving and rejecting business users’ commit requests.
See Committing Artifacts for Approval for business user procedures.
See Checking a Worklist and Taking Action for approver procedures.
Who Can Approve or Reject Commit Requests
In TIBCO BusinessEvents WebStudio users with Administrator role permissions can approve or reject commit requests, or delegate approval. They can also delegate the task of approving or rejecting commit requests to any specified user role and not to a specific user. In this case, the approval or rejection requests will be sent to all the users in that role. See To Delegate a Workitem.
Approval Status Values
COMMITED  When a user commits one or more resources for approval, the status of the request is set to Commited. The approver then sets the status as appropriate.
APPROVE  The request was approved. If the submission request was to add or change an artifact, that artifact is copied to the RMS project. If the submission request was to delete an approved artifact, that artifact is deleted from the RMS project.
REJECT  The change was rejected. If the submission request was to add or change an artifact, that artifact is not copied to the RMS project. If the submission request was to delete an approved artifact, that artifact is not deleted. It is up to the business user to make changes in their local project accordingly.
BUILDANDDEPLOY  The artifact is build and ready to be deployed. The artifact after approval is built and kept ready to be deployed at the location specified by a property in the RMS.cdd file. See RMS Server Configuration Property Reference for more details on property.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved