Process: Approve or reject supplier user
Flow
Objective
To approve or reject the registration of a supplier user.
Description
A supplier user will be in the pending state after registration. The supplier user cannot logon to the supplier hub until his or her registration is approved by the supplier organization.
Customization
Approvals can be enabled or disabled by a particular organization. By default, approvals are enabled for supplier user registration at all organizations.
Edition
Professional, Enterprise
Tasks
| Task | Description | Role |
|---|---|---|
| Approve registration |
If the Seller decides to accept the registration request, then the customer is put in approved state. A notification is sent out to let them know that their request has been accepted and that they can now shop in the store. |
Channel Manager |
| Find approver group |
Start with the organization to which the user registers, the system walks up the hierarchy looking for an organization with an associated approver group. When the first approval group is found, the members of that group are resolved and a notification is sent to them that there is a request pending their approval. If a disable approval group is the first group found, then we know that approvals have been disabled on this subtree, and we auto-approve the user. |
System |
| Reject registration |
If the Seller decides to reject the registration request, then the customer is not approved -- and cannot shop. A notification is sent to the customer that their request has been rejected. |
Channel Manager |
| Review approval request |
The Seller navigates to the administrative UI, finds the pending request, and chooses either to approve or reject it. |
Channel Manager |
Business artifacts
- Approval required notification
- Approved registration notification
- Approved supplier
- Pending supplier
- Rejected registration notification
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.