1.3.0

Release notes for version 1.3.0

• When working with simulation projects, you do not need to input physiological attributes such heart-rate (BPM) as this is handled for VHs by EDAA™ based on the data collected in the RDC phase.

• When working with simulation projects, it is not mandatory to always send audio clips. You can simply change the interaction type to text and enter the interaction value (text) directly.

• The FeedingDataId parameter is now added to the Interact API. It is an optional parameter that lets EDAA™ know about the action that occurred during data collection. Note: This is not related to the accuracy of contextual responses.

• We now support fixed summoning of entities of type Environment.

• The Broadcasting API is now available; You can use this API to broadcast an event that should impact all surrounding entities. This API has the following request parameters:

  • raised_By_Entity_Id is the entity that triggered the event.

  • impact_Entities_Id is the list of entities that should be informed about the event.

  • action_Feeding_Data_Id is an optional parameter that can be attached to the specific action that was triggered.

  • environment_Object_Id is an optional parameter that specifies the object impacted by the event.

• We have enhanced the performance on interactions by the environment for simulation projects. These interactions no longer result in errors.

• We have enhanced the overall response time of the platform.

• For data collection projects, you will not receive any responses from EDAA™ other than logic actions. This is because the project is meant for data collection purposes only.