Building Automated Workflows

To build an Automated Workflow –

1. Select WORKFLOWS in the left pane. The following is displayed –

2. Click the + Add New button. The following is displayed –

The left pane provides a selection of building blocks for creating your Automated Workflow. There are three types of building blocks – Initiators (green), Conditions (orange) and Actions (purple). As you build the Automated Workflow, these building blocks become available for selection.

Each Automated Workflow can have a single initiator, multiple conditions (with an AND or an OR relationship between them) and multiple actions. Each condition can trigger one or more different actions.

In the Search field at the top left corner of the page, you can type any part of the name of an Initiator, Condition or Action in order to filter the list accordingly.

3. Define an initiator for this Automated Workflow – Initiators determine the condition to be matched with each item in order to trigger this Automated Workflow. Define the Initiator of this Automated Workflow by dragging one of the initiator cards from the left pane onto the Insert initiator card. For example, the following shows the Status card after it has been defined as the Initiator of this Automated Workflow –

A form appears on the right side in which you can define the parameters of the Initiator, as shown below. The card that you defined as an Initiator turns orange until after you have filled out this form.

Select a condition from the top dropdown menu, as shown below –

Select a value from the bottom dropdown menu, as shown below –

The conditions and values that appear are according to the type of Initiator that you selected.

For example, the following defines that this Automated Workflow is triggered when the Status of an item is equal to Removed.

4. Define one or more conditions of the function to be applied by this Automated Workflow [Optional] – From the building blocks pane on the left, drag and drop one of the orange Condition cards into the flow diagram.

For example, the Removed Content Count condition keeps track of how many times a user’s item was removed from your platform. This means that dragging the Removed Content Count condition card into the flow enables you to define that a user is suspended after they have published more than a certain number of violative posts. For example, the following shows that the condition less than 3 is defined in the form on the right.

You can define multiple conditions with an AND relationship between them by dragging each condition card one after the other. For example, as shown below –

You can define multiple conditions with an OR relationship between them, each which will have their own actions (described below). To define another condition (of the same type), click the Add Criteria option in the right pane. For example, the following displays –

Another form appears in the right pane in which you can define this new condition. In the following example a different action is activated according to whether the quantity of removed content is less than three or greater than three.

Note – Only the same CONDITION building block can appear in a flow diagram in an OR relationship, such as the one shown above.

The following describes the CONDITION building blocks that you can drag into the flow diagram. Each appears with a different icon to represent its type, such as for a list or for a date.

• Entity Type – The Alice T&S platform categorizes the data that you send to it (via API request or file upload) as one of the following entities – Content, User, Flag and Collection. You may refer to Entity Types for more information.

• Violation Types – Each item analyzed by the T&S platform that is in violation of your platforms policy is assigned one or more Violation Types. Click here to see an updated list of the supported Violation Types.

• Content Type – Specifies the type of content of the item, such as audio, text, video, image or file.

• Collection Type – Specifies a group of entities. A collection is composed of multiple items grouped together in a playlist, album, folder, group or channel on your platform. For example, a playlist of videos (holding a list of videos), an album (holding a list of audio files), a group (holding a list of posts), a folder (holding a list of files) or a channel.

• Risk Score – The T&S platform uses a combination of AI-powered Risk Scores and human analysis to analyze each item, as well as its context in order to provide a risk score of (between 0 – 100) that indicates the extent and confidence that the item is in violation of each Violation Type, as described above.

• Username – Specifies the username of the person of the item, such as the person who published an item, the owner of a collection and so on.

• Date Created – Specifies the time that the item was created on your platform (not in the T&S platform), such as when it was posted on your platform.

• Date Reported – Specifies the time that the item arrived at the T&S platform.

• Custom Fields – Specifies a custom field that you created in your T&S platform account. See Custom Fields for more information.

• Last Activity – Specifies the timestamp of the most recent activity of a User or in a Collection.

• Views – Specifies the quantity of views of this item on your platform.

• Flags – Specifies the quantity of flags on this item on your platform. See Flags for more information.

• User Uploads – Specifies the quantity of uploads performed by this user to your platform.

• Comments – Specifies the quantity of comments made on this item on your platform.

• Priority – Specifies the priority of this item as set in the T&S platform by a moderator clicking a button in Moderation View or by an Automated Workflow. This can be affected by the Set Low Priority, Set Medium Priority and Set High Priority actions.

• Title – Specifies the title of this item on your platform.

• Status – Specifies the status of an item in the T&S platform. See Status for more information.

• Removed Content Count – Specifies the quantity of content items removed from your platform by the T&S platform for this user. This is a calculated field managed by the T&S platform.

• Webpage URL – Specifies the URL of this item’s webpage.

• Number of Followers – Specifies the quantity of followers of this item on your platform.

• User’s Birth Date – Specifies the birthdate of the user of this item, which may be important for child safety purposes.

• Languages – Specifies the language of this item, which might be required for translation purposes.

• Expert Notes – Enables conditions (such as contains) on the text that was entered by Alice analysts to describe an item and/or the reason that it is violative. These notes may be provided as part of Alice’s curated services. For example, this item is part of an up-and-coming terrorist trend originating in Syria.

• Exchange Balance – Specifies the balance of social platform credits of the user that published the item.

• Text – Specifies the text of the item. For example, the contents of a chat message. For example, in order to define an action that is triggered when an item has at least one comment, you can define the condition as – if [content has] more than 0 comments.

5. Define one or more actions to be performed by this Automated Workflow – From the building blocks pane on the left, drag and drop one of the purple Action cards into the flow diagram. For example, to notify the user. This selection of actions is listed in the Action Management page. You can drop multiple actions one after another into the flow diagram and each will be performed in the sequence that it is displayed.

Tip! You can drag additional conditions and actions onto the of an existing flow.

Tip! Use the NAVIGATOR tool to navigate around complex flow diagrams and to zoom in/zoom out.

6. Save the workflow by clicking the Save workflow button in the top right corner of the page.

You can delete any of the cards from a flow diagram by clicking on the x in their top right corner.

If the workflow definition is not valid (for example when it is missing an Initiator), it can be saved, but it cannot be activated.

Note – The T&S platform prevents the definition of certain invalid Automated Workflows, such as an endless loop that is triggered by the status of an item being changed to Removed and whose action changes the item status to Removed (meaning to the same status).