With this release, we bring you generated members, pipeline success rate, and more!

Generated members

Team Owners, Team Admins, and permitted Contributors can now generate members to test your Multimodal projects without inviting additional users. Generated members are created as Contributors and can be added to projects with any project role, including Project Admin.

Users can then switch to these generated members from a project’s Data tab or the Editor to view and work on items as that member. Actions performed this way are recorded under the generated member and linked to the original acting user.

Explore

You can now investigate your data directly from Chart view. Select a chart value to open its corresponding items in List view, zoom into the data using another Breakdown parameter, or add the represented items to a subset.

Your existing Explore filters are preserved as you investigate and drill down into chart data, allowing you to continue your analysis without recreating the same filters manually.

Pipeline success rate

You can now monitor each pipeline's Success Rate directly from the Pipelines list and its settings. The rate shows the percentage of successful runs from the last 24 hours, or from when the pipeline was most recently enabled if that was less than 24 hours ago.

Pipelines with a 0% success rate are automatically disabled after accumulating enough failed runs within the applicable evaluation period, helping prevent repeatedly failing pipelines from continuing to trigger. Auto-disabled pipelines can be investigated and re-enabled at any time, which starts a new success-rate and evaluation window.

Test items deprecation

The Test items feature will be leaving the multimodal project, as you can now use generated members to test things out more dynamically.

Other features & improvements

• Event nodes in Orchestrate now show example Event and Context JSON of their payloads directly in the right-side configuration panel, making it easier to write JSON paths and downstream logic without leaving the canvas.
• The Python SDK now supports authenticating with Organization API Keys using SAClient() by providing a team_id.
• The Python SDK now also supports the new SAORGClient() client to work across teams for organization-related functions with an Organization API Key.
  • You may now use SAORGClient.list_teams() to return the teams in a given organization.
  • You may now use SAORGClient.get_team_client(team_id) to return a standard SAClient.

What do you think of the update? We'd love to hear your feedback.