Release Notes

Enhancements

Organisations

Add Organisations to the API: You can now manage Organisations through the API. With this update, you can now create, retrieve, and update Organisation records programmatically. This enhancement provides more flexibility and automation capabilities for managing Organisations within the system.

Add Space and User to UI for Organisation & User Token Usages: This update enhances the token usage display by including the Space and User information for each token usage entry. For organisation tokens, the Space and User associated with the usage will be shown, providing better visibility into how tokens are being utilised across different Spaces and by different Users. Additionally, for guest user tokens, the guest User will be displayed, allowing for tracking of token consumption by guest users. This improvement brings more transparency and granularity to token usage tracking within the platform.

For example:

Remove billing user from display when billing mode is set to "Organisation Pays": When the billing mode is set to "Organisation Pays", the billing user information will no longer be displayed in the user interface, providing a cleaner and more streamlined Experience.

Make Organisation name on space page a link: The Organisation name displayed on the space page is now a clickable link that navigates to the Organisation's profile page. This enhancement improves the user experience by providing a convenient way to access organisation details directly from the space page.

Add billing account selector when creating a new Space from within an Organisation: This update introduces a new billing account selector when creating a new Space from within an organisation. Users can now easily associate the new Space with the appropriate billing account during the creation process, streamlining the setup and ensuring proper billing configuration from the start.

Experiences

Add ability to set pathname variables as if they were datums: This update allows you to set pathname variables via the link interface, similar to how you would set datums. This provides a more intuitive way to manage and link to different dynamically linked Experiences and Pathnames within your Space's Experience. Set the pathname variable by instantiating with a ':' and the variable name, e.g. :variable-name

1. Pathname variables can be added to the Pathname field in the Experience configuration section by adding a : and then the variable-name.
2. If pathname variables exist then Pathname Variable fields will be generated for each. This example shows you how you can set mocked data in these fields to view the contextualised experience in the Experience Designer interface (demonstrated at #3).
3. Demonstration of contextualised mocked data driven by populating the Pathname Variable fields shown at #2.
4. Link configuration can access Pathname Variables as though they were datums. This means that dynamic Experience links can be created based on configured data.

Update Content Sections to Correctly Handle Internal Value Changes in Experiences: Ensure that the content editor is cleared in the standard chat example when changed to content. This update improves the handling of internal value changes within Experiences, ensuring a consistent and expected behaviour for content editing in the standard chat example.

Timezones

Zoned Datetime storage in Schemas:

This update addresses issues reported regarding the display of time zone data from Schemas. The UI has been enhanced to correctly handle and display time-based information from Schemas, taking into account the appropriate time zones. This ensures that time-related data from Schemas is accurately represented in the user interface.

Fix Date w/ time Input Handling in Flow Execution: Resolved an issue where date and time inputs were not being handled correctly during Flow execution. This update ensures that date and time values are processed accurately, improving the reliability and consistency of Flow-based automations.

Flows

Fix input and output data from Sub Flow Execute nodes: The input data provided to the Sub Flow Execute node will be correctly passed and propagated to the triggered sub-flow, ensuring that the sub-flow receives the expected input data. Additionally, any output data generated by the sub-flow will be accurately captured and made available as output from the Sub Flow Execute node in the main flow. This improvement enhances the reliability and consistency of working with nested flows and sub-flows, enabling more robust and predictable data handling across complex Flow Experiences. Users can now confidently execute sub-flows and rely on the accurate propagation of input and output data, streamlining the development and execution of intricate Flow Schemas.

Add "createdAt" and "startedAt" to the data:context node: Introduced two new properties, "createdAt" and "startedAt", to the data:context node within the Space. The "createdAt" property captures the timestamp when the node was created, while "startedAt" records the time when the associated Flow or Experience was initiated. These additions provide valuable metadata for tracking and auditing purposes, enhancing visibility into the lifecycle of data nodes and related processes within the Space.

Add support for using standard schema properties with Flows: Introduces the ability to use the following standard schema properties within Flows: createdAt, updatedAt, createdById, and updatedById. These properties provide valuable metadata about the creation and modification times, as well as the user IDs associated with these events for each record in the Space.

API

Add openapi.json spec to an endpoint for automatic consumption: Introduces a new endpoint /api/v1/openapi.json that exposes the OpenAPI specification for the API. This allows developers to automatically discover and consume the API, facilitating integration and improving the developer experience.

Quality of Life

• Hide inaccessible tabs from non-admins in Space Settings screens.
• Improve list/bullet point experiences in Content editor.
• Improved UI and API Space deletion and access process.
• Fixed non-entity result labels in output table.
• Fix object:remove isArray result handle when "First match only?" is checked.
• Fix UX around indeterminate states on boolean input.
• Add default input field for initial Literal/Context selection.
• Improved the Log in and Sign up experience.