VMS Required Flows

From 3B Knowledge
Jump to navigation Jump to search


This article provides a detailed overview of all the Salesforce Flows that need to be configured within the Vendor Management System (VMS). Each flow is described with its purpose, input variables, and interaction within the VMS platform, as well as a "blueprint" screenshot, showing what a basic, bare-bone version of that flow would look like.

Autolaunched Flows

Autolaunched flows are triggered automatically without user interaction. They handle background processes such as notifications and updates.

1. VMS - Email - Accept/Reject New Booking Request

  • Description: Sends email notifications to relevant users when a booking request is created, notifying them when a booking request has been accepted or rejected.
  • Input Variables: None
VMS - Email - Accept/Reject New Booking Request] Flow A basic overview of what the flow [VMS - Email - Accept/Reject New Booking Request] Flow should contain.

2. VMS - Email - New Proposed Worker

  • Description: Automatically sends an email notification when a new worker is proposed for a booking request.
  • Input Variables: None

3. VMS - Email - New Vendor Invitation

  • Description: Sends out email invitations to vendors when they are invited to join the VMS workflow for a particular client.
  • Input Variables: None
A basic overview of what the flow [VMS - Email - New Vendor Invitation] should contain.

4. VMS - Proposal - Convert Individual to Contact

  • Description: Converts an Individual record to a Contact record, mapping all of the fields accordingly.
  • Input Variables: None
A basic overview of what the flow [VMS - Proposal - Convert Individual to Contact] should contain.

5. VMS - Proposal - Place Proposed Worker on Automated Workflow

Note: This flow is not required, but it's probably needed if the client wants the automated workflow functionality.

  • Description: Automatically places a proposed worker when the sub-vendor confirms they are available, if we're in the automated wotkflow.
  • Input Variables: None
A basic overview of what the flow [VMS - Proposal - Place Proposed Worker on Automated Workflow] should contain.

Screen Flows

Screen flows require user interaction and provide interfaces for managing proposals, booking requests, and worker actions.

1. VMS - Proposal - Accept Proposed Worker

  • Description: Allows a user (client or master vendor) to accept a proposed worker for a booking request.
  • Input Variables:
    • ProposedWorkerID: ID of the proposed worker being accepted.
A basic overview of what the flow [VMS - Proposal - Accept Proposed Worker Flow] should contain.

2. VMS - Proposal - Create Proposed Worker

  • Description: Enables the creation of a proposed worker for a specific booking request.
  • Input Variables:
    • BookingRequestID: ID of the booking request for which a worker is being proposed.
    • IndividualID: ID of the individual being proposed for the booking.
A basic overview of what the flow [VMS - Proposal - Create Proposed Worker] Flow should contain.

3. VMS - Proposal - Reject Proposed Worker

  • Description: Allows a user to reject a proposed worker.
  • Input Variables:
    • ProposedWorkerID: ID of the proposed worker being rejected.
A basic overview of what the flow [VMS - Proposal - Reject Proposed Worker] Flow should contain.

4. VMS - Proposal - Retract Worker

  • Description: Enables a vendor or client to retract a worker previously proposed for a booking request.
  • Input Variables:
    • ProposedWorkerID: ID of the proposed worker being retracted.
A basic overview of what the flow [VMS - Proposal - Retract Worker] Flow should contain.

5. VMS - Request - Create New Booking Request

  • Description: Enables users to create a new booking request for staffing needs.
  • Input Variables:
    • ClientID: ID of the client creating the request.
A basic overview of what the flow [VMS - Request - Create new Booking Request] Flow should contain.

6. VMS - Worker Management - New Worker

  • Description: Allows sub-vendors to add new workers to their roster.
  • Input Variables:
    • AccountID: ID of the account to which the new worker belongs.
A basic overview of what the flow [VMS - Proposal - New Worker] Flow should contain.

7. VMS - Worker Management - Edit Worker

  • Description: Allows users to edit existing worker details.
  • Input Variables:
    • WorkerID: ID of the worker being edited.
A basic overview of what the flow [VMS - Worker Management - Edit Worker] Flow should contain.
Retrieved from ‘https://3bknowhow.com/index.php?title=VMS_Required_Flows&oldid=782’