Feeding actions and attributes
Learn how to create and manage actions and attributes for your project using the Portal
When running a solution, at different moments, based on the conditions predefined in logics, Affective Computing (powered by Virtue) performs or delivers actions. For example, you can create an action to display a personalized greeting when a (real or virtual human) user enters a room.
Attributes shape and classify actions. Related or similar actions can be grouped under the same attribute, similar to putting them in a common folder. For example, an attribute can contain multiple questions about the same matter framed in different ways ("Are you OK?", "How are you feeling?", "Do you feel good?").
To learn more about how actions and attributes work hand in hand with logics and help to incorporate personalization in solutions, see:
Feeding attributes
Log in to the Portal.
In the top navigation bar, select the Project for which you want to create attributes.
In the left sidebar, navigate to Action Feeds > Feeding Attributes
Navigate to one of the following tabs depending on the type of attribute you want to create:
Contents
Interactions
Triggered Actions
In the upper-right corner, click + Create.
Enter the following details:
Name
The name of the attribute.
(Mandatory) Enter a name.
Action Type
Type of action (for example, playing a sound or asking a question)
(Mandatory) Select an option.
For Diagnostics only?
Determines whether the actions grouped under the attribute needs to be used only in diagnostics mode (i.e. when obtaining psychological profiles of users). For example, a specific question can be asked during the diagnostics process to increase personalization.
If you want to use the actions in the attribute only for diagnostics, select this checkbox.
The Action Feeding section lists available actions. You can select the actions that you want to group under the new attribute. For any listed action that you want to add to the attribute, in the Actions column, click Add.
Click Save.
Feeding actions
Log in to the Portal.
In the top navigation bar, select the Project for which you want to create actions.
In the left sidebar, navigate to Action Feeds > Action Feeding
In the upper-right corner, click + Create.
Enter the following details:
Action Category
The category of the action
(Mandatory) Select one of the following options:
Content
Interaction
Triggered action
Action Type
Type of action (for example, playing a sound or asking a question)
(Mandatory) Select an option. The values you can select depend on the action category you selected previously.
Identity
The ID (name) of the action
(Mandatory) Enter a name
Executable Action
The action that EDAA™ needs to execute.
(Mandatory) Depending on the action category and type, do one of the following:
Upload a file that contains the audio that needs to be played when executing the sound or music content action.
Enter the details of the action. For example, when creating a question interaction action, you can enter the question that needs to be asked when executing the action.
Keep it secret
Determines whether the action is available only for you as a tenant and not to other clients
If you want to keep the action secret, select this checkbox This ensures that the action is used only in the current project.
Click Save.
Auto-feeding of actions
To make the feeding process easier, the Portal offers two ways of automation: importing the feeding and auto-feeding from an uploaded document.
You can also feed actions in an automated manner when using the Portal in the following ways:
Importing an action feed
Auto-feeding actions by uploading a document
Importing a feed from a channel
Log in to the Portal.
In the top navigation bar, select the Project into which you want to import actions.
In the left sidebar, navigate to Action Feeds > Action Feeding.
In the upper-right corner, click + Import.
Enter the following details:
Request URL
The URL from where the feed must be imported
(Mandatory) Enter the URL.
Request Method
Type of request (for example, GET)
(Mandatory) Select an option.
Request Header
The header for the request
(Optional) Enter the request header Notes:
Separate rows by entering them in new lines.
Separate keys and values using ":".
Request Body
The body of the request
(Optional) Enter the request body in JSON format.
Response Attributes
The response of the request
(Optional) Enter the response attributes Notes:
Separate rows by entering them in new lines.
Separate keys and values using ":".
Expected Response Code
The expected response code for a successful request (for example, 200)
(Mandatory) Enter the response code
Enter the details of the imported attribute:
Action Category
The category of the action
(Mandatory) Select one of the following options:
Content
Interaction
Triggered action
Action Type
Type of action (for example, playing a sound or asking a question)
(Mandatory) Select an option. The values you can select depend on the action category you selected previously.
Click Start Connection.
Auto-feeding actions from a PDF file
Log in to the Portal.
In the top navigation bar, select the Project into which you want to import actions.
In the left sidebar, navigate to Action Feeds > Auto-Feeding
In the upper-right corner, click + Create.
In [File path], upload the document.
Click Save
The document must contain two identifiable columns: identity and executable action.
Verifying actions
Whenever an automated feeding method is used to create an action, the action must be manually verified to ensure proper feeding. Do the following to verify your actions through the Portal:
Log in to the Portal.
In the top navigation bar, select the Project that contains the actions you want to verify.
In the left sidebar, navigate to Action Feeds > Action Feeding.
The list of all actions created is displayed. You can review the Verified column to understand whether the action has been validated.
To verify an action, in the Actions column, click Verify.
Related documentation
Action and attribute feedingLast updated
Was this helpful?