Overview


Solodev Workflows allows administrators to monitor tasks performed on files, asset files and datatable entries. With workflows administrators can also create rules to notify departments in their organization of form submissions for marketing purposes. This article will provide administrators with a high level overview of Solodev Workflows. 

Types of Workflows

Administrators are able to create three types of workflows: 

File: A workflow triggered by any file that is saved as a draft (Save), placed on a staging server (Stage), or public facing (Publish). For example, administrators can create a workflow that notifies the QA team whenever pages are staged for live demonstrations. 

Task: A workflow that is triggered by any task that is completed by a user or completed by a user from a specific group. Tasks must be encapsulated in a datatable or an asset file. 

Form Submission: A workflow that is triggered by a form submission. For example, administrators can create a workflow that notifies the media team if the subject line in the form is ‘media inquiry’. The rules for the form submission are created using PHP.

Workflow Fields

File Workflow

The workflow fields for the File workflow are listed below: 

Select user: the user that is assigned to the task. 

Assign to: the user that the task is assigned to once the specified task action is executed. 

Tickler Information: the email address of the user that is notified once the specified task action is executed. 

Task workflow

The workflow fields for the Task workflow are listed below:

Completed by user

Select user: the user that is assigned to the task. 

Assign to: the user that the task is assigned to once the specified task action is executed. 

Tickler Information: the email address of the user that is notified once the specified task action is executed. 

Object Type: the object in which the task is encapsulated. Administrators can choose between Datatable and Asset Files. 

Notification Policy: The notification rules for the task once the specified action is executed. Solodev recommends setting the notification policy to both ways. Administrators can choose the following options: 

Forwards – The assign to user is notified once the specified action is executed. 

Backwards – The initial user receives a notification once the specified action executed. 

Both ways – The assign to user and the initial user receive notifications once the specified task action is executed.

Completed by user from group

Assign to group: the group assigned to the task. 

Assign to: the user that the task is assigned to once the specified action is executed. 

Tickler Information: the email address of the user that is notified once the specified task action is executed. 

Object Type: the object in which the task is encapsulated. Administrators can choose between Datatable and Asset Files. 

Notification Policy: The notification rules for the task once the specified action is executed. Solodev recommends setting the notification policy to both ways. Administrators can choose the following options: 

Forwards – The assign to user is notified once the specified action is executed. 

Backwards – The group receives a notification once the specified action executed. 

Both ways – The assign to user and the group receive notifications once the specified task action is executed.

Form Submission

Choose Datatable: this will be form that triggers the task in the workflow upon submission.

Variables: The php variables that will be used in if then conditional. For example, these variables can be email addresses or subject lines. 

If statement: the condition that triggers the task in the form submission workflow

Then statement: the action that is executed if the condition is true. For example, this is usually where administrators set the tickler information. 

Did this answer your question?