Business Negotiation Management Process

/ Workflow Apps / Information Control
Business Negotiation Management Process 20221228
This is the process of creating a user ID for a customer at the time of a business meeting. The service to be provided is determined according to the sales representative’s proposal. At the same time as the proposal is decided, a preparation request is automatically sent to the service representative.
Operators (Number of Swimlanes: 3)
  • Sales Manager
  • Service A Manager
  • Service B Manager
Workflow (Workflow diagram complexity: 26)
  • 11. Lead Registration
    • Sales representatives register lead information, such as the name of the client company.
  • 62. Business Records
    • Sales representatives will describe the services they propose to introduce and record their activities.
  • 83-1. Service A Demo Environment Construction
    • The person in charge of Service A records the results of the demonstration environment construction.
  • 93-2. Service B Demo Environment Construction
    • The person in charge of Service B records the results of the demonstration environment construction.
  • 7x1. Set the Subject
    • The workflow platform stores the subject.
  • 25x2. Subject Change
    • The workflow platform stores the subject line.
  • 11x3-1-1. Construction Status Update
    • The workflow platform updates the construction status to “completed”.
  • 3x3-1. Demo environment A construction begins
    • The workflow platform awaits building instructions from the sales representative.
  • 15x3-2-1. Construction Status Update
    • The workflow platform updates the construction status to “completed”.
  • 4x3-2. Demo environment B construction begins
    • The workflow platform awaits building instructions from the sales representative.
  • 28x4. Activity history added
    • The workflow platform adds the results of activities to the history.
  • 29x5.Clear Activities
    • The workflow platform clears the activity.
Workflow Diagram (click to open) Clears the dynamic content.
Business process variables to be passed (number of data items: 24)
  • ◆ Lead Information 0
  • Lead No. q_lead_number 1
    • A unique number will be stored in this app.
    • L-#{#sformat(‘%06d’, processInstanceId)}
  • Lead generation date q_lead_date 2*
    • The date when the lead occurred is stored.
    • processInstanceStartDatetime
  • Company Name q_corp_name 3*
    • The customer company name is stored.
  • Name of person in charge q_person_name 4*
    • The name of the customer representative is stored.
  • Contact person’s e-mail address q_person_email 5*
    • The customer representative’s e-mail address will be stored.
  • Contact person’s phone number q_person_telno 6
    • The customer representative phone number is stored.
  • Sales Manager q_sales_person 7*
    • The sales representative is stored.
    • ${processInstance.initQuserId}
  • ◆ Business meeting activity information 8
  • Negotiation Status q_status 9*
    • The status is stored according to the negotiation status.
    • action
  • Proposal Type q_demo_create 10*
    • The proposal type scheduled by the sales representative is stored.
  • Activity Record Date q_action_date 11*
    • The date and time of the record of the business meeting activity are stored.
  • Activities q_action_info 12*
    • The details of the negotiation are stored.
  • Activity History q_action_history 13
    • Past business meeting activities will be added and recorded.
  • ◆ Information on Service A Responsibilities 14
  • Service A: Demo Environment Status q_sa_demo_status 15*
    • Stores the construction status of the demo environment for Service A.
    • serviceA_demo_yet_create
  • Service A: User Information q_sa_account_info 16*
    • The results of building the demo environment for Service A (created user IDs, etc.) will be stored.
  • ◆ Information on Service B Responsibilities 17
  • Service B: Demo Environment Status q_sb_demo_status 18*
    • Stores the construction status of the demo environment for Service A.
    • serviceB_demo_yet_create
  • Service B: User Information q_sb_account_info 19*
    • The results of building the demo environment for Service B (created user IDs, etc.) will be stored.
  • ◆ System Information 20
  • Service A: API Key q_sa_api_key 21
    • The API key required to start creating a Service A demo account is stored.
    • #{#randomString(12)}
  • Service B: API Key q_sb_api_key 22
    • The API key required to start creating a Service B demo account is stored.
    • #{#randomString(12)}
  • Communication History q_communication 23
    • The history of interactions between the personnel in charge within the workflow is stored.

Field Name, Num, Initial Value

Download

This archive contains the BPMN icon, which is only available in the Professional edition.

Notes

  • Associate the processor settings with the organizational structure during import
  • “e1. Construction start request”, “e2. Construction start request” Message Throwing Intermediate Event (HTTP)
    • At runtime, a Webhook is applied to each of “x3-1. Demo environment A construction begins” and “x3-2. Demo environment B construction begins”.
      • “x3-1. Demo environment A construction begins” and “x3-2. Demo environment B construction begins” automatically move to the next process.

Capture

See also

Receive Task (Webhook)

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from Questetra Support

Subscribe now to keep reading and get access to the full archive.

Continue reading

Scroll to Top