Defining Workflows
(40 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | {{page.name: Development | + | {{page.name: Development Solution: Defining Workflows for Objects and Workflow Types - Subscribe-HR Wiki}} |
{{page.head: Defining Workflows}} | {{page.head: Defining Workflows}} | ||
__TOC__ | __TOC__ | ||
− | ==What is a Workflow== | + | =Workflow Forms= |
+ | |||
+ | To create a workflow form: | ||
+ | # After logging into the Subscribe-HR HCM Cloud Platform, select <b>Development</b> from the left hand navigation. | ||
+ | # Select the <b>Objects</b> Folder. | ||
+ | # Select the Object that you wish to define a workflow form for. | ||
+ | # Select the <b>Workflow Form</b> sub folder | ||
+ | # Enter the <b>Form Name</b> | ||
+ | # Check <b>Document Approval</b> if this form is going to be used for contract, letter of offer, or canvas approval using the on boarding deployment or canvas deployment tools | ||
+ | # Select the desired <b>Document Field</b>, this is the document that you wish to be approved | ||
+ | # Select <b>Add Field</b> and from the first drop down, Select the name of that you wish to add to the form . You can add as many fields as required. | ||
+ | # Choose whether the set approver can edit the form, or only view it | ||
+ | # Choose whether the set requester can edit the form, or only view it | ||
+ | # Once the <b>Definition</b> has been completed Select the <b>Actions</b> on the top left | ||
+ | # Select the green <b>Add Action</b> button. You can add as many actions as required | ||
+ | # Add an <b>Action Name</b> | ||
+ | # Set who the action will be <b>Assigned To</b> | ||
+ | # Select from the drop down which Snippet you would like this form to trigger | ||
+ | # Select from the drop down which workflow you would like this form to trigger | ||
+ | # Once this workflow's conditions have been met, select the <b>Status</b> you would like it to be set too | ||
+ | # Check <b>Completes Workflow</b> if this action is the end of the task. | ||
+ | # Select the <b>Save</b> button | ||
+ | |||
+ | ===What is a Workflow=== | ||
A workflow consists of a sequence of connected steps, that are run when conditions are met. | A workflow consists of a sequence of connected steps, that are run when conditions are met. | ||
<br> | <br> | ||
− | The Dictionary definition is: It is a depiction of a sequence of operations, declared as work of a person, a group of persons, an | + | The Dictionary definition is: It is a depiction of a sequence of operations, declared as work of a person, a group of persons, an organisation of staff, or one or more simple or complex mechanisms. |
− | + | ||
<br> | <br> | ||
Workflows are triggered by meeting a condition, or reaching a step defined in the workflow process. | Workflows are triggered by meeting a condition, or reaching a step defined in the workflow process. | ||
<br> | <br> | ||
− | By looking at the | + | By looking at the SubTabs in the Workflow Tasks it can be said to be broken down into:<br> |
− | + | <b>General</b> - What type of Workflow am I.<br> | |
− | + | <b>Condition</b> - When do I start.<br> | |
− | + | <b>Reminder</b> - What do I do when I start.<br> | |
− | + | <b>Updates</b> - Do I need to update any fields in the system after I have started. | |
− | ==Defining Workflows for Objects== | + | ===Defining Workflows for Objects=== |
We first of all need to select the Object we wish to create the workflow for. Our choice of the object will be based on the information we are collecting. | We first of all need to select the Object we wish to create the workflow for. Our choice of the object will be based on the information we are collecting. | ||
− | <br> | + | |
− | ===Workflow | + | ===Creating a Workflow for an Object=== |
+ | # After logging into the Subscribe-HR portal, select the <b>Development</b> TAB | ||
+ | # Select the <b>Objects</b> Folder. | ||
+ | # Select the Object that you wish to define a workflow for. | ||
+ | # Select the <b>Workflow Tasks</b> SubFolder from the left side menu. | ||
+ | # Select the [Add new record] button. | ||
+ | # Decide whether the Workflow is Active or not<br>If this is set to Yes then the Workflow is active in the system, and when triggered the workflow will carry out its task. | ||
+ | # Enter the <b>Name</b> of the workflow you are creating. | ||
+ | # Select the <b>Workflow Type</b> as defined below. | ||
+ | # Select the <b>Workflow mode</b> as defined below. | ||
+ | # Select the <b>Create Task</b> Yes or No, as defined below. | ||
+ | # Select the <b>Task Type</b> as defined below. | ||
+ | # Select the <b>Enable External Approvals</b> Yes or No, as defined below. | ||
+ | # Select the <b>Anniversary Date</b> as defined below. | ||
+ | # Enter the <b>Description</b> for the Workflow. | ||
+ | # Activate <b>SMS</b>. Yes or No. You can Activate SMS for each Workflow individually or in bulk from the Activation Hub also. Doe this from the Push Notifications and Adding Functionality Widget. | ||
+ | # Select the [Save] button. | ||
+ | |||
+ | <b>Mandatory fields are marked with Red Asterisk, the record will not be saved unless mandatory fields are filled in first.</b> | ||
+ | |||
+ | =General TAB= | ||
+ | |||
+ | ===Active=== | ||
+ | <b>Yes</b> or <b>No</b> to whether the Workflow is turned on (Active) or not. | ||
+ | |||
+ | ===Name=== | ||
+ | Enter the Name by which the Workflow will be referenced. | ||
+ | |||
+ | ==Workflow Type== | ||
Workflow types define when an action should be triggered. | Workflow types define when an action should be triggered. | ||
The Workflow types are: | The Workflow types are: | ||
− | * Create New Records - Workflow is triggered when a new record is created | + | * <b>Create New Records</b> - Workflow is triggered when a new record is created |
− | * Update Existing Records - Workflow is triggered when an existing record has been updated | + | * <b>Update Existing Records</b> - Workflow is triggered when an existing record has been updated |
− | * Create New or Update Existing Records - Workflow is triggered when a new record or an existing record has been updated | + | * <b>Create New or Update Existing Records</b> - Workflow is triggered when a new record or an existing record has been updated |
− | * Time Based - Workflow is triggered when a time condition has been met. | + | * <b>Time Based</b> - Workflow is triggered when a time condition has been met. |
+ | * <b>Triggered by another Task</b> - Workflow is triggered by another Task. | ||
− | + | <i><b>Example:</b> An Example of a <b>Time Based</b> Workflow Type: Employee Birthdate<br> | |
− | An Example of a | + | We could setup an Employee Birthdate workflow with the conditions of where the Employee birthday is less than 3 days. When the condition of 3 days before the Employee Birthday is met an action is triggered.</i> |
<br> | <br> | ||
− | + | <i><b>Example:</b> An Example of a <b>Create New or Update Existing Records</b> Workflow Type: Employee Address Update Notification. | |
<br> | <br> | ||
− | <br> | + | When an employees address details are updated or a new record inserted, a notification can be automated.</i> |
− | + | ||
− | < | + | ===Workflow Mode=== |
− | + | Select the Mode for the Workflow: | |
− | < | + | * <b>Standard</b> - This should be used for most Workflows created where the conditions inside the workflow are adequate.<br>It will use the Standard Condition outlined in [[Creating-workflow-tasks-in-Subscribe-HR#Condition_TAB|Condition TAB]]. |
+ | * <b>Custom Condition</b> - This is available as some areas of the system have pre-programmed custom conditions that cannot be otherwise defined by the Standard Workflow Mode, if selecting the custom condition you loose the ability to define your own conditions. | ||
+ | |||
+ | ===Execute=== | ||
+ | This option is only visible when modifying a Workflow, not when Adding a Workflow.<br> | ||
+ | It is also only available if <b>Workflow Mode</b> is set to <b>Standard</b>: | ||
+ | * <b>Once</b> - Once Triggered the first time, this Workflow will not trigger it again. | ||
+ | * <b>Always</b> - This will Trigger every time the Conditions are met. | ||
+ | |||
+ | ===Create Task=== | ||
+ | <b>Yes</b> or <b>No</b> to create the <b>Task Type</b> selected below. | ||
+ | |||
+ | ===Task Type=== | ||
+ | Task Types define what the workflow type is when it is triggered. | ||
+ | The Task types are: | ||
+ | * <b>Reminder</b> - Send the recipient a reminder that a certain task or action is required within the system. | ||
+ | * <b>Request</b> - Send the recipient a request to be completed before the workflow can continue. Workflow Forms can be attached to requests. | ||
+ | * <b>Checklist</b> - Send the recipient a checklist of action and tasks that they are required to complete. | ||
+ | |||
+ | ===Enable External Approvals=== | ||
+ | <b>Yes</b> or <b>No</b> to Enables the recipient of the workflow to make an action on the workflow without having to log into the Subscribe-HR portal. | ||
+ | |||
+ | ===Anniversary Date=== | ||
+ | The Anniversary Date option in the "General" Tab allows you to set reminders based on a Anniversary Date.<br> | ||
+ | <i><b>Example:</b> Birthday, Start Date. Based on setting this, Subscribe-HR will send a notification every 12 Months from this original date.</i> | ||
+ | |||
+ | ===Description=== | ||
+ | Type in the Description of the Workflow. | ||
+ | |||
+ | ===Create Separate Inbox Items=== | ||
+ | Sends individual e-mails to each recipient in there are multiple recipients to receive. They will not be able to see all recipients in the e-mail To. Individual will see their own name only in the "To" in the e-mail itself. | ||
+ | |||
+ | ===Activate SMS=== | ||
+ | Activate SMS sending by selecting Yes. You can Activate single SMS through this field. One at a time. Of you can do this when Activating SMS through the Activation Hub. Through the Activation Hub, you can activate Single - at a time or all Workflows to send SMS. SMS will be sent to mobile numbers including the selected international prefix. For Team Dashboard Users Only. | ||
+ | |||
+ | ===Condition TAB=== | ||
+ | # Select the <b>Conditions</b> SubTAB. | ||
+ | # From the first drop down select the field that you want to trigger the workflow on. | ||
+ | # Select the condition that applies to the selected field.<br>If the selected field is a date field then the operator would be <b>Is Less Than</b> or <b>Was More Than</b>, If the selected field is a Yes / No field then the operator would be <b>Equals To</b>. | ||
+ | # Select the value from the drop down, The value changes depending on the field chosen, If the field chosen is a date field the value would contain date / time periods such as 1 hour, 1 day, 1 week. If the field chosen is a Yes / No field then the value is more likely to be Yes or No. | ||
+ | # Additional conditions can be added by selecting the <b>Add condition</b> link. | ||
+ | # Select the [Save] button. | ||
===Workflow Conditions Explained=== | ===Workflow Conditions Explained=== | ||
− | A Workflow needs to know when to start (when to be triggered) and | + | A Workflow needs to know when to start (when to be triggered) and that's what the conditions are for. Every condition that is added uses an AND statement meaning each condition must be met or the workflow is not triggered. |
<br><br> | <br><br> | ||
A considerable amount of flexibility exists in the Subscribe-HR system. You may notice the available fields in the conditions are not all from the same object. In fact the Subscribe-HR system allows you to select fields from the parent object as well as the child object.<br> | A considerable amount of flexibility exists in the Subscribe-HR system. You may notice the available fields in the conditions are not all from the same object. In fact the Subscribe-HR system allows you to select fields from the parent object as well as the child object.<br> | ||
+ | <i><b>Example:</b> Say you were creating a Workflow for <b>Employee Property</b>. The parent object is <b>Employee</b> and the child is <b>Employee Property</b> this means you have access to all fields in the Employee Object and the Employee Property Object. A further example could be Jobs and Job Benefits.</i><br> | ||
<br> | <br> | ||
− | + | To add a condition select a field from the drop down. You may notice that the drop down contains the field name and in brackets (the object name).<br> | |
− | + | <i><b>Example:</b> Date Allocated(Property) | |
− | To add a condition select a field from the drop down. You may notice that the drop down contains the field name and in brackets (the object name).<br>Example: Date Allocated(Property) | + | simply means that we are reading the Date Allocated field from the Employee Property Object.</i> |
− | simply means that we are reading the Date Allocated field from the Employee Property Object. | + | |
− | <br> | + | =Reminder TAB= |
− | + | ||
− | <br><br> | + | ===Key Dates=== |
+ | # Select the <b>Reminder</b> SubTAB. | ||
+ | # In the <b>Due Date Field</b> drop down select the date field that will define due date for the task or reminder. <b>NOTE: Setting this field will generate a calendar reminder. The reminder will be attached to the e-mail that gets sent out by S-HR. The user can click on the file (called an ICS file). Doing so will create a calendar entry for the reminder. </b><br> | ||
+ | <i><b>Example:</b> If we select Start date (Employee) then a reminder is sent on the Employee's Start Date. Training Reminder: When a training booking is done. Notification can be sent to the attendee (person who the training record is for). They can book this training event into their calendar by clicking on the ICS file attached to the e-mail</i> | ||
+ | |||
+ | ===Main Recipients (Managers and Approving)=== | ||
+ | # <b>Send to Employee Manager</b> - select Yes or No in the Look-up<br>If this is Yes then the Employee's Manager will receive the Main Template. | ||
+ | # <b>Send to Location Manager</b> - select Yes or No in the Look-up<br>If this is Yes then the Location Manager will receive the Main Template. (Location managers are defined under the Maintenance Tab, Locations Folder) | ||
+ | # <b>Send To Managers Manager</b> - select Yes or No in the Look-up<br>If this is Yes then the Employee's Manager's Manager will receive the Main Template. | ||
+ | # <b>Field On The Form (Email)</b> - This allows you to delegate an email address that is entered into a field on the Object form.<br><i><b>Example:</b> If the Object we are working with is the Employee Object then all email address fields found in the Employee object will be listed in the Field On The Form drop down. The email address that is saved on the delegated field is the email address that the Field On The Form Template will be sent to.</i> | ||
+ | # <b>Field On The Form (Mobile)</b> - This field will only show Mobile Fields for Applicant, Employee - User Profile. If the Workflow is set-up for Applicant, you will only see Applicant Mobile fields. If you set-up an HR Workflow you will see Employee or User Profile Fields. You can send an SMS to a User who is not an Employee. Select User Profile field for this purpose. | ||
+ | # <b>Send to Users</b> - select the users you wish to receive the reminder. The list of users are users of the Subscribe-HR System, any selected user will receive the Main Template. | ||
+ | # <b>Send to Groups</b> - select the user groups you wish to receive the reminder. The list of recipients will include all the users that belong to the user group/s selected, and will receive the Main Template. | ||
+ | # <b>Link Survey</b> - select the Canvas/Survey you wish to include/send to users via the Workflow. A link to that Canvas/Survey will be sent via the correspondence template linked to the Workflow. | ||
+ | <b>Note:</b> In Team Dashboards, Performance Reviews (Canvases/Surveys) are sent/deployed People & cultures Users via the Performance Management Widget only. They can't be sent via a Workflow. | ||
+ | # <b>Main Template</b> - select the template that you wish for Employee Manager, Location Manager, Manager's Manager, Users and Other Email Addresses to receive. | ||
+ | |||
+ | ===Other Recipients (Requesting Entities)=== | ||
+ | # <b>Send to Employee</b> - select Yes or No in the drop down<br>If this is Yes then the Employee Template will be sent to the employee. If No then nothing is sent to the employee. | ||
+ | # <b>Field On The Form (Email)</b> - This allows you to delegate an email address that is entered into a field on the Object form. The email address on the form will be sent the selected Template from the Other Recipients (Requesting Entities) Template drop down. | ||
+ | # <b>Field On The Form (Mobile)</b> - This field will only show Mobile Fields for Applicant, Employee - User Profile. If the Workflow is set-up for Applicant, you will only see Applicant Mobile fields. If you set-up an HR Workflow you will see Employee or User Profile Fields. You can send an SMS to a User who is not an Employee. Select User Profile field for this purpose. | ||
+ | # <b>Send to Record Creator</b> - This will allow the person who created a record from this form to be sent the selected Template from the Other Recipients (Requesting Entities) section. | ||
+ | # <b>Template</b> - The selected template will be sent to anyone who is delegated in the Other Recipients (Requesting Entities) section. | ||
+ | |||
+ | <b>Note:</b> It is important to know that when creating a <b>Request</b> Task Type Workflow that the Other Recipients (Requesting Entities) section is used for the employee making the request and the Main Recipients (Managers and Approver) section is used for the managers dealing with the request.<br> | ||
+ | <i><b>Example:</b> If we are setting up a Leave Request workflow, we use the Main Recipients Managers and Approver) section to delegate which managers receive the request to approve or deny, and what template they would receive.<br>We would then use the Other Recipients (Requesting Entities) section to delegate if we wish to send a template to the Employee, and which template to send them.</i> | ||
+ | |||
+ | =Updates TAB= | ||
+ | # Select the <b>Updates</b> SubTAB. | ||
+ | # From the first drop down select the field you wish to update as a result of this workflow being triggered. | ||
+ | # Select the Operator:<br>The operator changes depending on the field chosen, If the field chosen Is a Yes / No field then the operator would be <b>Equals To</b>, If the field chosen is date field the Operator is more likely to contain <b>Plus</b> or <b>Minus</b>. | ||
+ | # Select the Value<br>The value changes depending on the field chosen, If the field chosen is a date field the value would contain date / time periods such as 1 hour, 1 day, 1 week. If the field chosen is a Yes / No field then the value is more likely to be Yes or No. | ||
+ | # To update additional fields select the <b>Add update</b> link and select the field from the next drop down. | ||
+ | # Select the [Save] button. | ||
===Workflow Updates Explained=== | ===Workflow Updates Explained=== | ||
Updates simply refer to a nominated field being updated as a result of a defined value.<br> | Updates simply refer to a nominated field being updated as a result of a defined value.<br> | ||
− | After a workflow is triggered the update can be performed additional to the reminder. | + | After a workflow is triggered the update can be performed additional to the reminder.<br> |
− | + | A considerable amount of flexibility exists in the Subscribe-HR system. You may notice the available fields in the Updates are not all from the same object. In fact the Subscribe-HR system allows you to select fields from the parent object as well as the child object. | |
− | A considerable amount of flexibility exists in the Subscribe-HR system. You may notice the available fields in the Updates are not all from the same object. In fact the Subscribe-HR system allows you to select fields from the parent object as well as the child object | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | <b>This is not mandatory or is it necessary to have fields automatically updated as a result of a workflow being executed.</b> | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ===Workflow Delegation=== | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
+ | Employee records marked as recipients can set up the Delegation field to forward to emails if they will not be able to address the email themselves. This can be found [[Employee-file#Workflow_Delegation|here]]. | ||
+ | =Webhook TAB= | ||
+ | Workflows can be linked to a webhook. When condition of the workflow is met it will post an update to valid URL. | ||
+ | # Select the <b>Webhook</b> SubTAB. | ||
+ | # Set "Enable Webhook" field to Yes. | ||
+ | # Set Webhook URL to the URL where you want update to be posted. | ||
+ | # Set "Enable Basic Authentication" field to Yes if you would like to enable basic authentication. | ||
+ | # Set Username and Password fields if basic authentication is enabled. | ||
+ | # Select the [Save] button. | ||
− | + | <br><br>[[File:subscribehr_logo.gif]] | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | [[File:subscribehr_logo.gif]] | + |
Latest revision as of 01:08, 6 May 2024
Workflow Forms
To create a workflow form:
- After logging into the Subscribe-HR HCM Cloud Platform, select Development from the left hand navigation.
- Select the Objects Folder.
- Select the Object that you wish to define a workflow form for.
- Select the Workflow Form sub folder
- Enter the Form Name
- Check Document Approval if this form is going to be used for contract, letter of offer, or canvas approval using the on boarding deployment or canvas deployment tools
- Select the desired Document Field, this is the document that you wish to be approved
- Select Add Field and from the first drop down, Select the name of that you wish to add to the form . You can add as many fields as required.
- Choose whether the set approver can edit the form, or only view it
- Choose whether the set requester can edit the form, or only view it
- Once the Definition has been completed Select the Actions on the top left
- Select the green Add Action button. You can add as many actions as required
- Add an Action Name
- Set who the action will be Assigned To
- Select from the drop down which Snippet you would like this form to trigger
- Select from the drop down which workflow you would like this form to trigger
- Once this workflow's conditions have been met, select the Status you would like it to be set too
- Check Completes Workflow if this action is the end of the task.
- Select the Save button
What is a Workflow
A workflow consists of a sequence of connected steps, that are run when conditions are met.
The Dictionary definition is: It is a depiction of a sequence of operations, declared as work of a person, a group of persons, an organisation of staff, or one or more simple or complex mechanisms.
Workflows are triggered by meeting a condition, or reaching a step defined in the workflow process.
By looking at the SubTabs in the Workflow Tasks it can be said to be broken down into:
General - What type of Workflow am I.
Condition - When do I start.
Reminder - What do I do when I start.
Updates - Do I need to update any fields in the system after I have started.
Defining Workflows for Objects
We first of all need to select the Object we wish to create the workflow for. Our choice of the object will be based on the information we are collecting.
Creating a Workflow for an Object
- After logging into the Subscribe-HR portal, select the Development TAB
- Select the Objects Folder.
- Select the Object that you wish to define a workflow for.
- Select the Workflow Tasks SubFolder from the left side menu.
- Select the [Add new record] button.
- Decide whether the Workflow is Active or not
If this is set to Yes then the Workflow is active in the system, and when triggered the workflow will carry out its task. - Enter the Name of the workflow you are creating.
- Select the Workflow Type as defined below.
- Select the Workflow mode as defined below.
- Select the Create Task Yes or No, as defined below.
- Select the Task Type as defined below.
- Select the Enable External Approvals Yes or No, as defined below.
- Select the Anniversary Date as defined below.
- Enter the Description for the Workflow.
- Activate SMS. Yes or No. You can Activate SMS for each Workflow individually or in bulk from the Activation Hub also. Doe this from the Push Notifications and Adding Functionality Widget.
- Select the [Save] button.
Mandatory fields are marked with Red Asterisk, the record will not be saved unless mandatory fields are filled in first.
General TAB
Active
Yes or No to whether the Workflow is turned on (Active) or not.
Name
Enter the Name by which the Workflow will be referenced.
Workflow Type
Workflow types define when an action should be triggered. The Workflow types are:
- Create New Records - Workflow is triggered when a new record is created
- Update Existing Records - Workflow is triggered when an existing record has been updated
- Create New or Update Existing Records - Workflow is triggered when a new record or an existing record has been updated
- Time Based - Workflow is triggered when a time condition has been met.
- Triggered by another Task - Workflow is triggered by another Task.
Example: An Example of a Time Based Workflow Type: Employee Birthdate
We could setup an Employee Birthdate workflow with the conditions of where the Employee birthday is less than 3 days. When the condition of 3 days before the Employee Birthday is met an action is triggered.
Example: An Example of a Create New or Update Existing Records Workflow Type: Employee Address Update Notification.
When an employees address details are updated or a new record inserted, a notification can be automated.
Workflow Mode
Select the Mode for the Workflow:
- Standard - This should be used for most Workflows created where the conditions inside the workflow are adequate.
It will use the Standard Condition outlined in Condition TAB. - Custom Condition - This is available as some areas of the system have pre-programmed custom conditions that cannot be otherwise defined by the Standard Workflow Mode, if selecting the custom condition you loose the ability to define your own conditions.
Execute
This option is only visible when modifying a Workflow, not when Adding a Workflow.
It is also only available if Workflow Mode is set to Standard:
- Once - Once Triggered the first time, this Workflow will not trigger it again.
- Always - This will Trigger every time the Conditions are met.
Create Task
Yes or No to create the Task Type selected below.
Task Type
Task Types define what the workflow type is when it is triggered. The Task types are:
- Reminder - Send the recipient a reminder that a certain task or action is required within the system.
- Request - Send the recipient a request to be completed before the workflow can continue. Workflow Forms can be attached to requests.
- Checklist - Send the recipient a checklist of action and tasks that they are required to complete.
Enable External Approvals
Yes or No to Enables the recipient of the workflow to make an action on the workflow without having to log into the Subscribe-HR portal.
Anniversary Date
The Anniversary Date option in the "General" Tab allows you to set reminders based on a Anniversary Date.
Example: Birthday, Start Date. Based on setting this, Subscribe-HR will send a notification every 12 Months from this original date.
Description
Type in the Description of the Workflow.
Create Separate Inbox Items
Sends individual e-mails to each recipient in there are multiple recipients to receive. They will not be able to see all recipients in the e-mail To. Individual will see their own name only in the "To" in the e-mail itself.
Activate SMS
Activate SMS sending by selecting Yes. You can Activate single SMS through this field. One at a time. Of you can do this when Activating SMS through the Activation Hub. Through the Activation Hub, you can activate Single - at a time or all Workflows to send SMS. SMS will be sent to mobile numbers including the selected international prefix. For Team Dashboard Users Only.
Condition TAB
- Select the Conditions SubTAB.
- From the first drop down select the field that you want to trigger the workflow on.
- Select the condition that applies to the selected field.
If the selected field is a date field then the operator would be Is Less Than or Was More Than, If the selected field is a Yes / No field then the operator would be Equals To. - Select the value from the drop down, The value changes depending on the field chosen, If the field chosen is a date field the value would contain date / time periods such as 1 hour, 1 day, 1 week. If the field chosen is a Yes / No field then the value is more likely to be Yes or No.
- Additional conditions can be added by selecting the Add condition link.
- Select the [Save] button.
Workflow Conditions Explained
A Workflow needs to know when to start (when to be triggered) and that's what the conditions are for. Every condition that is added uses an AND statement meaning each condition must be met or the workflow is not triggered.
A considerable amount of flexibility exists in the Subscribe-HR system. You may notice the available fields in the conditions are not all from the same object. In fact the Subscribe-HR system allows you to select fields from the parent object as well as the child object.
Example: Say you were creating a Workflow for Employee Property. The parent object is Employee and the child is Employee Property this means you have access to all fields in the Employee Object and the Employee Property Object. A further example could be Jobs and Job Benefits.
To add a condition select a field from the drop down. You may notice that the drop down contains the field name and in brackets (the object name).
Example: Date Allocated(Property)
simply means that we are reading the Date Allocated field from the Employee Property Object.
Reminder TAB
Key Dates
- Select the Reminder SubTAB.
- In the Due Date Field drop down select the date field that will define due date for the task or reminder. NOTE: Setting this field will generate a calendar reminder. The reminder will be attached to the e-mail that gets sent out by S-HR. The user can click on the file (called an ICS file). Doing so will create a calendar entry for the reminder.
Example: If we select Start date (Employee) then a reminder is sent on the Employee's Start Date. Training Reminder: When a training booking is done. Notification can be sent to the attendee (person who the training record is for). They can book this training event into their calendar by clicking on the ICS file attached to the e-mail
Main Recipients (Managers and Approving)
- Send to Employee Manager - select Yes or No in the Look-up
If this is Yes then the Employee's Manager will receive the Main Template. - Send to Location Manager - select Yes or No in the Look-up
If this is Yes then the Location Manager will receive the Main Template. (Location managers are defined under the Maintenance Tab, Locations Folder) - Send To Managers Manager - select Yes or No in the Look-up
If this is Yes then the Employee's Manager's Manager will receive the Main Template. - Field On The Form (Email) - This allows you to delegate an email address that is entered into a field on the Object form.
Example: If the Object we are working with is the Employee Object then all email address fields found in the Employee object will be listed in the Field On The Form drop down. The email address that is saved on the delegated field is the email address that the Field On The Form Template will be sent to. - Field On The Form (Mobile) - This field will only show Mobile Fields for Applicant, Employee - User Profile. If the Workflow is set-up for Applicant, you will only see Applicant Mobile fields. If you set-up an HR Workflow you will see Employee or User Profile Fields. You can send an SMS to a User who is not an Employee. Select User Profile field for this purpose.
- Send to Users - select the users you wish to receive the reminder. The list of users are users of the Subscribe-HR System, any selected user will receive the Main Template.
- Send to Groups - select the user groups you wish to receive the reminder. The list of recipients will include all the users that belong to the user group/s selected, and will receive the Main Template.
- Link Survey - select the Canvas/Survey you wish to include/send to users via the Workflow. A link to that Canvas/Survey will be sent via the correspondence template linked to the Workflow.
Note: In Team Dashboards, Performance Reviews (Canvases/Surveys) are sent/deployed People & cultures Users via the Performance Management Widget only. They can't be sent via a Workflow.
- Main Template - select the template that you wish for Employee Manager, Location Manager, Manager's Manager, Users and Other Email Addresses to receive.
Other Recipients (Requesting Entities)
- Send to Employee - select Yes or No in the drop down
If this is Yes then the Employee Template will be sent to the employee. If No then nothing is sent to the employee. - Field On The Form (Email) - This allows you to delegate an email address that is entered into a field on the Object form. The email address on the form will be sent the selected Template from the Other Recipients (Requesting Entities) Template drop down.
- Field On The Form (Mobile) - This field will only show Mobile Fields for Applicant, Employee - User Profile. If the Workflow is set-up for Applicant, you will only see Applicant Mobile fields. If you set-up an HR Workflow you will see Employee or User Profile Fields. You can send an SMS to a User who is not an Employee. Select User Profile field for this purpose.
- Send to Record Creator - This will allow the person who created a record from this form to be sent the selected Template from the Other Recipients (Requesting Entities) section.
- Template - The selected template will be sent to anyone who is delegated in the Other Recipients (Requesting Entities) section.
Note: It is important to know that when creating a Request Task Type Workflow that the Other Recipients (Requesting Entities) section is used for the employee making the request and the Main Recipients (Managers and Approver) section is used for the managers dealing with the request.
Example: If we are setting up a Leave Request workflow, we use the Main Recipients Managers and Approver) section to delegate which managers receive the request to approve or deny, and what template they would receive.
We would then use the Other Recipients (Requesting Entities) section to delegate if we wish to send a template to the Employee, and which template to send them.
Updates TAB
- Select the Updates SubTAB.
- From the first drop down select the field you wish to update as a result of this workflow being triggered.
- Select the Operator:
The operator changes depending on the field chosen, If the field chosen Is a Yes / No field then the operator would be Equals To, If the field chosen is date field the Operator is more likely to contain Plus or Minus. - Select the Value
The value changes depending on the field chosen, If the field chosen is a date field the value would contain date / time periods such as 1 hour, 1 day, 1 week. If the field chosen is a Yes / No field then the value is more likely to be Yes or No. - To update additional fields select the Add update link and select the field from the next drop down.
- Select the [Save] button.
Workflow Updates Explained
Updates simply refer to a nominated field being updated as a result of a defined value.
After a workflow is triggered the update can be performed additional to the reminder.
A considerable amount of flexibility exists in the Subscribe-HR system. You may notice the available fields in the Updates are not all from the same object. In fact the Subscribe-HR system allows you to select fields from the parent object as well as the child object.
This is not mandatory or is it necessary to have fields automatically updated as a result of a workflow being executed.
Workflow Delegation
Employee records marked as recipients can set up the Delegation field to forward to emails if they will not be able to address the email themselves. This can be found here.
Webhook TAB
Workflows can be linked to a webhook. When condition of the workflow is met it will post an update to valid URL.
- Select the Webhook SubTAB.
- Set "Enable Webhook" field to Yes.
- Set Webhook URL to the URL where you want update to be posted.
- Set "Enable Basic Authentication" field to Yes if you would like to enable basic authentication.
- Set Username and Password fields if basic authentication is enabled.
- Select the [Save] button.