| Status | ||
|---|---|---|
|
...
This example
Process Description
This diagram describe on boarding process for the new customer
Process Scheme
Participants
Process name | DescriptionRequester | ||
Main process | The user who requests a day offApprovercompany for the onboarding process | ||
Supervisor | A user or group of users who have permission to approve a day off in the company | Slack Action Receiver | The technical process for receiving and processing button responses from Slackstop on boarding process if something was wrong |
Requester | A user who request the boarding process into the company |
Activities
Activity name | Activity type | Activity description | Forms |
|---|---|---|---|
| Manual request | Empty start event | Requester ask about new access and fill Manual request Form | Manual Request |
| API request | Message start event | Onboarding process can be started from 3d part API | |
| Record customer | User task | In this form user needs to define the workflow requirement. | Record Form (Google Form) |
Validate Workspace | User task | This task is for the validators, they need to define 2 main aspects: 1) requested workspace id is not taken, 2) a valid license file should be uploaded. | Validate workspace form |
| Valid Gateway | Exclusive Gateway | ||
Create Production Workspace Create Sandbox Workspace Create Development Workspace | Service task | These tasks can be performed depending of the initial request to create the workspace with requested information. | |
| Generate Summary | Script task | This activity is executed by ProcessMaker I/O engine an is a script to generate a PDF with the information about the workspaces and credentials. | |
| Verify Onboarding Data | User task | This activity is created to validate for the same user has approved all information generated by the other activities. | Verify Onboarding Data |
| Gateway 1 | Inclusive Gateway | - | |
| Gateway 2 | Inclusive Gateway | - | |
| Boundary Event | Intermediate Event Type(Timer) | ID Name Intermediate Event type Timer Definition type (Calendar Date, Duration) | - |
| Notify Supervisor | Intermediate Event Type(Email message) | ID Name Intermediate Event type Script type (expression, connector, external, etc) Script name Script body Message id | - |
| Notify Requestor | Intermediate Event Type(Email message) | - | |
| End event 1 | End event (Empty end event type) | - | |
| End event 2 | End event (Empty end event type) |
Messages
Message Title | Item | Type | Content |
|---|---|---|---|
Notification to requester | "Verify Onboarding Data" User Task /Notify Requester Message event | email message | Hello {{Requester name}}, You request was approved and implemented. A workspaces for {{ClientName}} was created Please find the summary document with Credential report in the attachment Best regards! |
Notification to supervisors | "Validate workspace" User task /Notify Supervisor Message event | email message | Hello {{Supervisor name}}, We just wanted to inform you , that {{Requester name}} request for creating workspaces for {{ClientName}} wasn't validated during dedicated time Best regards! |
Documents
Document name | Item | Type | Template |
|---|---|---|---|
Credential report | Generate Summary |
Process Items
The tasks in the process are listed in the table below:
A user who have permission to stop on boarding process if something was wrong
Task | Type | Process | Connector | Description |
Time Off Request | Start Event | Requester |
| Starts the Requester process |
Initiate SlackBot | Script Task | Requester |
| This technical task runs script and sets up the Slack application parameters, such as AppNumber, Dates, Slack bot token and Slack channel name |
Send Time Off Request | Service Task | Requester | Slack\APIConnector | This is where the user requests the time off. |
Slack Request Sent | Intermediate Message Event | Requester |
| This message event sends the request for approval |
Approve Request | Start Message Event | Approver |
| This start event is initiated by the Slack Request Sent message event and launches the approver process |
Slack Response Received | Start Event | Slack Action |
| This event launches the Slack API when the "Approve" or "Reject" button is clicked |
Parse Payload | Script Task | Slack Action |
| This script decodes json and prepares the data to send in the Slack API response to the approver |
Get Slack Callback | Intermediate Message Event | Slack Action | CorrelationKeys | Gets the callback and sends the Slack response to the appropriate process instance |
Response Confirmation | Service Task | Slack Action | Slack\SendMessageConnector | This connector sends the Slack webhook |
Get Slack Response | Intermediate Message Event | Approver |
| When the approver gets the response from the Slack webhook, the approver can continue with the approval process |
Send Approval/Send Decline | Service Task | Approver | Slack\APIConnector | This is where the approver makes a decision |
Send Confirmation Request Accepted | Service Task | Requester | Slack\SendMessageConnector | This is where the requester gets a message notifying them that their request is being reviewed |
Decision Made | Intermediate Message Event | Requester | CorrelationKeys | This message event sends a notification to the requester with the approver's decision |
...