Workflows in Axpert

In Axpert, each transaction may need to go through an approval process wherein a  user or a role is assigned a task of approval. This is defined as a work flow and  is attached to a TStruct. A work flow consists of many levels through which the transaction moves. At each level a user role is attached. When a transaction comes to that level, the user attached to that role can approve or reject the transaction. If approved, it moves to the next level.

A work flow at its simplest level will be a list of user roles that will approve a transaction one after the other.

Points to remember

  • Each role in the workflow can do one of the following actions with a transaction
    • Approve
    • Reject
    • Review
    • Return
  • An approved transaction moves to the next role mentioned in the flow.
  • A rejected transaction is marked as ‘reject’ and does not flow to the next level.
  • Some transactions can flow to a role which has the authority to review or verify the data in the transaction.
  • Returned transactions are sent back to the role in the prior level in the work flow.
  • Notifications can be defined at each level in the work flow. The recipients of the notification and the notification message can be set. The mode of notification can be internal or through an Email. In case of an internal notification, the message will be sent to the to-do list of the recipient.
  • The max time that a transaction can be held by a role can be defined. In case the user does not attend to a transaction within the specified time then the transaction will automatically flow to the next level.
  • There can be many users attached to a role. So, when a transaction has to move to a role in the work flow, the specific user needs to be identified. This is called as user identification. A user is identified by binding the logged in user to the users attached to the selected role. The binding is done using fields in user management system.