Release Notes v5.16

What's new?

• Deployments within AWS now default to using AWS SES for transactional email. To enable this feature it is necessary to add the environment variable AWS_REGION whose value would take the format us-east-1, for example. SES needs to be activated within the AWS environment, which would involve granting the ses:SendEmail IAM permission to Ursa Studio.
• The legacy Data Review panel has been removed from all objects in Object Workshop.
• Multi-tab support for boards in Analytics Portal. Users can create tabs and position board tiles within tabs from the board edit screen. Any board with tabs enabled will show one tab at a time while in view mode. By convention, any board with tabs should have a tab element as its first element; if this is not in place then a tab entitled "First Tab" will be automatically added.

What improvements have we made to existing features?

• The Saved ELT trigger API endpoint will now return the ID of the created ELT, which can now be used in a new "status" endpoint to determine the status of the ELT that had been triggered. The status endpoint is available via a GET request
  https://your.ursa.url/ELTBatchJob/status?name=<saved ELT name>&token=<saved ELT token>&id=<ELT ID>.
• In Complex Timeline and Attribution Timeline objects, the leftbar item group representing the stack currently under focus will be replicated at the top of the leftbar, for ease of navigation.
• Package submission will no longer drag in related assets from other namespaces. Moving forward, if a package's assets depend on a second package's assets, that second package should also be imported.
• Semantic mapping template fields can be set up as required and/or as non-nullable. Being required means that they must be mapped by the semantic mapping object, although this requirement can be overridden at the object level. Being non-nullable means that a validation rule will be added to the semantic mapping object upon import to either throw a warning or an error if any records of the applicable field are null.
• The “Import Object Source” special field on semantic mapping objects will now capture the current source of the import object, instead of the source of the import object at the moment of import.
• The data effective and coverage date inputs for import objects have been moved from the Object Metadata panel to the Configuration panel.
• Packages have been renamed to Modules.
• Built-in length operators for object validation, which can be used to validate the length of any string field.