In general, the approval process includes the following user interactions, all of which is carried out with an HTML browser. Approvers receive notifications of all approval requests via e-mail.
- The system determines whether approval is required for the organization performing the particular action.
- An approver is selected from the appropriate approver member group.
- If approval is not required, pre and post-processing tasks are initiated.
- If approval is required, the pre-approve command is invoked and the approval request is stored. E-mail notifications are sent to approvers.
- An approver checks the list of approval requests awaiting approval and approves or rejects them. If desired, the approver can add comments.
- If approved, the post-approve command, if any, is invoked. If rejected, the post-reject command, if any, is invoked.
- The submitter can check the approval status throughout the process and view the approver's comments.
Note: When an approvable action enters the approval process, the submitter sees it as an "approval submission" or "submission" in the user interface. The approver responsible for approving the action sees it referred to as an "approval request" or "request" in the user interface.
More specifically, when an organization signs up for a specific approver member group, users having a particular user role are implicitly placed in that group. Any user with the default role for that organization becomes an approver for the corresponding action. The four approver member groups and their associated default roles available for WebSphere Commerce are as follows:
Process subject to approval | WebSphere Commerce default approval groups | Default role with authority to approve |
---|---|---|
|
|
Sales Manager |
|
|
Buyer approver |
|
|
Reseller or Buyer administrator |
|
|
Sales Manager |
|
|
Buyer administrator |
The table also lists the flows for disabling the inherited approval authority for each of the contract, order, reseller and buyer registration, RFQ, and user registration approval processes. Disabling the inherited approval authority that a child organization has inherited from its parent organization means that a the child organization no longer has the same approval access as its parent. To allow an organization to override the parent organization's approval requirement, the disable member groups are included in the list of approval levels for an organization. The Site Administrator can log onto the Organization Administration Console, select Access Management > Find Organizations to find organizations to work with. From this list, the Site Administrator can select an organization and click Approval to view a list of approval groups for the organization and select approval groups from this list and move them to the Selected approvals list.
By default, the root organization has the User Registration Approvals group added to the Selected roles list and the default organization has the DisableInherited User Registration Approvals group added to the Selected approvers list. The implication of this default setting is as follows:
- A user registering to any organization except the default organization requires approval, unless this organization explicitly disables the approval.
- A user registering to the default organization does not require approval.
Note: If an organization administrator does not sign up for an approver member group, approval will not be enabled for the associated business process. This means that all instances of that particular process are automatically approved.