Skip to main content

Vendor Workflow Service

Legacy Flow Diagram​

Drafting the high level flow diagram for vendor create case

Overview:

  1. Procurement team login to VMDM portal ,if Procurement team member is access to VMDM_WRITE_ACCESS group , then procurement member can open the inbox and verify is any approval pending. If any pending task and procurement team member can approve/reject the creation of the vendor. Even whoever procurement member has write access they can create a new vendor based on the Request and WF action also can be performed. 1.1 If Approved , then vendor will be onboarded successfully. 1.2 If Rejected , then it will be soft deleted or It will send back to procurement for alignment.
  2. Procurement team login to VMDM portal ,if Procurement team member is belongs to VMDM_READ_ACCESS group then , procurement member can only submit a new vendor request.
  3. Once case id is created ,generate workflow to Data Steward for update the financial data. Data Steward should have access at cluster level VMDM_<CLUSTER>_ACCESS(VMDM_IBS_ACCESS) Here IBS is India, Bangladesh and Singapore belongs to one cluster. 3.1 Data steward can update the details and approve the record for next level. 3.2 Data steward can reject the workflow and step 1.2 will be repeated.
  4. After Data Steward approved the workflow , it will a create a task and assign to supplier(based on the email provided while creating the vendor) and alternatively it will also assign to VODM_WRITE_ACCESS group. Once supplier registered and logging into the VODM portal he can able to update the details based on the task that is assigned.
  5. Finally after updating Bank details , supplier can submit the task and it will send back to procurement team for approval step 1.

High Level Flow Diagram for Modern workflow:

BPMN File:

Created a BPMN file with flows, below are the pending tasks in the BPMN file

  1. we need to map each flow with API endpoints
  2. Read payload should be an execution listener we need to see the alternative of this in Camunda 8
  3. Exception Handler integration and mapping
  4. Access management
  5. Define the input payload to start the workflow
  6. Unit Testing

Note: MIM team approved for workflow OAS and workflow topic. https://github.com/Maersk-Global/smds-vmd-api-specifications/blob/develop/src/main/resources/spec/v1/VendorWorkflow-API.v1.yaml https://github.com/Maersk-Global/API-JSON-Schema-Definitions/blob/master/models/902-SMDS-Vendor/v1/cloud/WorkflowNotification.v1.avsc

Rahul Singh and Ramesh Varma Kutcherlapati , Please review and change status of this page

Was this page helpful?