Excerpt | ||
---|---|---|
| ||
Understand the usage of Workflow Rules within CRM.COM |
Panel | ||||
---|---|---|---|---|
| ||||
Table of Contents
|
What are Workflows?
Workflow Rules govern the behavior of specific entities in the system and the way specific actions may be applied on these entities. The actions are triggered from specific events if certain conditions are fulfilled. Each Workflow Rule refers to a specific Entity.
The following entities may be added in workflow rulesA Workflow is a set of tasks which are necessary to complete a bigger task, involving the definition, execution, and forwarding of the task amongst users for action, according to a set of Workflow rules. Workflow Rules support business workflows and automate tasks required to complete business processes, triggering System actions provided certain events or conditions occur. Workflow rules can be set up for the following modules:
- Activities
- Service Requests
- Jobs
- Subscriptions
- Reward Offers
Status colour Yellow title Available from CRM.COM R11.0.0
Workflows GlossaryGlossary
Term | Description | ||
---|---|---|---|
Workflow Rules | Workflow Rules are used to apply actions on specific entities, triggered by specific events, provided the conditions are fulfilled.
| Alerts | Alerts are used in order
|
Alerts | Alertsare used to communicate information to CRM.COM usersUsers, either through email or SMS. Each alert consist a content template (the text that will be send) and a list of recipients that will receive the alertorSMS,and can be automatically triggered when certain events occur in the System. | ||
Alert Tags | Alert tags are dynamic Dynamic information , that can be used, within the alert subject or alert content, in order to dynamically generate information, based on data kept on the entity that is communicated through the alertcommunicated entry. | ||
Webhooks | Webhooks are used in order to Webhooksare used to pass information to third party systems , without being that are not integrated with CRM.COM. Webhooks consist of the URL that will be used to send the information and a selection of the actual information that will be passed over | Approvals | Approvals are used in order to block a specific record from being edited, unless it is approved by an authorised user. Each approval consist of a list of groups, units or users that are authorized to approve each entity and the number of required approvals |
Secret Key | A module used to generate keys and register them to specific URL endpoints. The keys are used by Webhooks to generate a code used by third party systems to authenticate the received data. | ||
Approvals | Approvalsare a mechanism used to control the creation and update of entries in the System by requesting approval from specific Users before granting access for further editing. | ||
Status Transitions | Status Transitions define the allowed or disallowed transitions between statuses of a specific entity based on a set of conditions that include the initial and destination status value, the type of the entity Transition defines how the Status of an entity can be changed, depending on its initial value, its Type, and the user or unit who is performing the status transition. | ||
Workflow Rules | Workflow Rules are used in order to apply actions on specific entities, triggered by specific events and considering that the specified conditions are fulfilled |
modifying the Status. |
Workflows Key Processes and Concepts
Processes / Concept | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
Alerts | Alerts are a way of communicating to users certain events that occur in the system. For example whenever a new Installation request is created for a new subscription you can set up an alert so that the event will be Automatically Scheduling Activities | Activities can be automatically scheduled when other events such as the creation of a new Subscription, Job or Service Request occur in the System. | |||||||
Automatic Communication of Newly Assigned Tasks to Users via Email or Sms | Alerts communicate certain System events to the appropriate users. Alerts can be configured for: Using Webhooks you are given
| Webhooks |
Alerts can be configured to be triggered automatically through Workflow Rules. | ||||||
Third Party System Updates through Webhooks | Webhooks offer the option to create an HTTP POST as a response to an event that happens. You can use webhooks along 3rd party systems without the need of integration to CRM.COM | ||||||||
Status Transitions | Status Transitions allow you to protect the users from erroneously changing the status of entities, such as an activity a job or a service request. For example you can set it up in such a way that an activity for an installation can only be changed from its initial status to specific status following a logical sequence, rather than jumping between statuses. | ||||||||
Approvals | Approvals allow you to protect data from being updated by adding Approval requests required from specific users or units. In this way you have the option to control the updating of newly created entities, or updating existing entities. Editing of an entity and in particular the update of a subscription using any subscription action is not going to be allowed if any pending approvals exist. | ||||||||
Automatically Scheduling Activities | System allows activities/tasks to be automatically created when specific events take place in the system, given that certain conditions are met. |
Workflows Network Characteristics
a CRM.COM event.Web hookscan be used with third party systems without CRM.COM integration. Webhooks can be configured for:
Webhooks can be configured to be triggered automatically through Workflow Rules. | |||||||
Controlling Status Change | The transition of the Status in Activities, Jobs and Service Requests can be forced to follow a logical sequence rather than jumping between Statuses. | ||||||
---|---|---|---|---|---|---|---|
Approval of Entries Before Further Processing | The processing of newly created or modified entries can be controlled through the addition of Approval Requests. While unhandled Approval Requests exist on an entry, further processing is not allowed. The permission to approve the requests can be granted to specific Users or Users belonging to particular Units, which are predefined through the Approval Definitions. Approval Requests can be configured for:
Approval Request can be configured to be triggered automatically through Workflow Rules. |
Workflows Access & Viewing Controls
Business Network Characteristics define the level of access for each record. i.e. Whether , whether it will be available for selection, for viewing or editing e.t.c.
Entity | Network Characteristics | Description |
---|---|---|
Approval Requests | Approval Requests have no access restrictions. They can be viewed and selected by all users. | |
Alerts | Alerts have no access restrictions. They can be viewed and selected by all users. | |
Webhooks | Webhooks have no access restrictions. They can be viewed and selected by all users. |
Workflows Related Related Modules
Entity | Interaction of Workflows with the EntityHow | ||||||
---|---|---|---|---|---|---|---|
Jobs |
| ||||||
Service Requests |
| ||||||
Activities |
| ||||||
Subscriptions |
| ||||||
Security Keys |
| ||||||
Reward Offers
|
|
Workflows - Business Examples
The following section provides business examples to help you understand of how CRM.COM Workflows module module is used.
Alert Installers when a new Installation Activity is createdCompany ZX - New Subscription Order Workflow
Panel | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
Business Requirement Company ZX would like to inform its installers via email, every time a new installation activity is created based on the area that they are responsible for. There are exists Installation departments in 2 areas, North and South London. The first installer available is then responsible for completing the taskfollows the Business Workflow below when a new customer calls in the Call Centre to request a new Subscription.
CRM.COM Solution
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Related Areas
|
|
name | grey |
---|