Integrating Security Approval Workflow

A very common workflow situation is where a transaction must be approved by a certain group or individual. While you could model this using the workflow designer, WorkflowFirst make this even easier by supporting approval workflow as part of its security system.

This means that, as well as disallowing or restricting someone the rights to modify a certain area of the database, you can also require approval before that person can modify a certain part of the database. A specific user group is assigned a defined role to govern changes in that area, and they will be emailed for approval before the change will be committed. All of this is handled automatically by the system, all you have to do is add the permissions.

Because workflow involves collecting information from the user and setting fields, these same permissions can be applied to fields in the record on which the workflow is operating. This allows you to easily combine approval workflow with your process workflow.

For example, a user cannot change budget numbers without the approval from the CFO if it falls above a certain threshold. Here, you would set up a permission so that the budget field value cannot be set to a value larger than $5,000 without the CFO's approval. The budget value and the user group requiring approval would both be configured in the application after it is published.

For more information on setting up approval workflow, see Security Approval Workflow.


Next Topic:
v4.2.0.956 (beta)
Up Since 2/29/2024 12:02:23 AM