1.3.1.1

Release notes for version 1.3.1.1 - 14-Aug-2024

The following new features are available in this version:

Support for group interactions

During data collection and simulation, you can implement and manage group interactions. You can use the following new endpoints to initialize and dissolve group interactions:

New endpoint for initializing interactions

Error while loading OpenAPI operation — Failed to fetch OpenAPI file

New endpoint for dissolving interactions

Error while loading OpenAPI operation — Failed to fetch OpenAPI file

New request parameter: Group_ID

For both data collection and simulation, you can use the new parameter, Group_ID. This parameter is optional and its value determines the following:

• If you haven't provided a value for this parameter in an ongoing interaction session that contains an active group interaction, EDAA™ checks whether the session belongs to an active group conversation. If yes, the interaction is marked as a group interaction. If not, it is considered a solo interaction.

• If you have provided a null value for this parameter, EDAA™ ignores the group interaction even if the current session belongs to an active group conversation.

• If you have provided a valid active group interaction ID, the interaction is marked as part of it.

New request parameter for simulations: Next_Participant_InteractionSession

For simulations, in addition to Group_ID (the group interaction ID), you can also use the new Next_Participant_InteractionSession parameter.

If you have created a group interaction of type "Directed" (where you must select the session ID that interacts next yourself), providing a value for this parameter is mandatory.

If you have created a group interaction of type "Automated", this parameter is not required. You must provide a null value as EDAA™ automatically chooses who speaks next.

New response attribute for simulations: next_participant

A new long data type response attribute, next_participant, is now available. During an automated group interaction, the value of this attribute is the session ID that performs the next interaction.

New Interaction API endpoint for understanding the psychological evolution of entities

Error while loading OpenAPI operation — Failed to fetch OpenAPI file

New response attribute for interactions: interaction_identifier

A new response attribute, interaction_identifier, is displayed for successful interaction requests to the Interact endpoint of the Interaction API (POST /api/v2/Interaction/Interact)

This attribute is a combination of the interaction session ID and stage, and has the following format:

{Interaction_ID}_{Stage}

New FeedingData API endpoint for verifying actions generated by EDAA

When EDAA™ generates actions, they initially have an "Un-verified" status. EDAA™ ignores unverified actions and doesn't use them as part of any experience. The actions are only used when they are verified. We have included this step in the process to ensure that the actions generated by EDAA™ are correct and meet the quality you require.

You can use this new endpoint to mark EDAA™-generated actions as verified actions.

Error while loading OpenAPI operation — Failed to fetch OpenAPI file

Parameter value validation

We have included validations in the following stages of working with EDAA™ so that only valid parameter values are accepted:

• Creating projects

• Creating logics

• Creating feeds. Only feed values that match the selected feed type are accepted/

• Initializing new interaction sessions. The validation check whether the purpose of the interaction session project is defined as "simulation". If yes, Entity ID is a mandatory parameter. If the project's purpose is defined as "data collection", then User ID is a mandatory parameter.

We have also enhanced the content of our error messages to clearly communicate the issues and facilitate their quick resolution.