Prismatic Changelog

You can now control how many concurrent executions are allowed for individual flows within an integration. This allows you to prevent overwhelming third-party APIs with too many simultaneous requests, or to limit resource usage for particularly intensive flows.

Previously, you could configure a flow to allow only one execution at a time by enabling FIFO (first in, first out) processing. Now, you can set a specific maximum number of concurrent executions for each flow.

See Flow Concurrency for more information.

You can now create and assign instance profiles to customize resource allocations and execution constraints for specific integrations and instances. This allows you to increase memory limits for memory-intensive integrations, control step result and log retention, and enable quickstart to reduce cold start times for synchronous invocations.

We've redesigned the integration landing page to provide a one-stop shop for all information related to a specific integration. When you as an organization team member opens an integration, you'll see information about deployed instances, recent executions, marketplace configuration, and more.

You can now enter listening mode when testing webhook-based triggers in code-native integrations. This allows you to quickly set up temporary webhooks in third-party applications and capture incoming webhook requests from the third-party from your IDE.

Read more in Testing Code-Native Integrations.

Prismatic is now available in a new public region in South Africa (Cape Town). This new region provides low-latency access for customers in Africa and surrounding areas.

See the deployment regions documentation for more information about accessing this and other regions.

You can now switch between Prismatic tenants without logging out.

If you have access to multiple tenants (Dev, Prod, Staging, etc.), you'll see a new Tenant Picker in the left-hand sidebar. It shows which environment you're working in and lets you switch between environments instantly. No more juggling browser sessions or credentials.

Also in this release:

• Single identity across tenants - Use the same email and password for all your Prismatic environments. No more email aliases.
• SSO works seamlessly - If you're using SSO, it now works seamlessly across multiple tenants in the same region without workarounds.

Two new instance lifecycle events are now available for custom connector triggers: webhookLifecycleHandlers.create and webhookLifecycleHandlers.delete. These functions run when an instance is deployed or disabled, and also when you enter or exit listening mode.

Listening mode is a new feature in the integration designer and embedded workflow builder that allows you to quickly test webhook triggers without deploying an instance. When you or your customers enter listening mode, the webhookLifecycleHandlers.create function is executed to create a temporary webhook in the third-party application that points to your integration designer's test instance. When you exit listening mode, the webhookLifecycleHandlers.delete function is executed to remove the temporary webhook. While in listening mode, you can see incoming webhook requests in real-time and save webhook payloads to use as test data for your trigger.

You can now convert low-code integrations to code-native directly within the Prismatic UI. This allows you to prototype a new integration quickly using the low-code designer, and then switch to code-native when you need more flexibility or control.

To get started, open any low-code integration and click Convert to Code. You'll get a preview of the generated code, and can choose to download a zip file containing the code-native TypeScript project.

You can now embed a dedicated connections management screen in your application using the new prismatic.showConnections() function. This screen provides your customers with a centralized location to view and manage all of their reusable customer connections for both marketplace integrations and custom workflows.

What's new:

• Unified connections view: Display all reusable connections in one place with the prismatic.showConnections() function
• Connection details: Customers can click on any connection to view which instances and workflows use it
• Full management capabilities: Edit or delete connections directly from the embedded screen
• Seamless experience: Consistent connection management whether customers are working with marketplace integrations or custom workflows

Benefits:

• Simplified connection management for customers who use the same credentials across multiple integrations
• Better visibility into where connections are being used
• Reduced need for custom connection management UI in your application

This feature requires @prismatic-io/embedded version 4.2.0 or later. See the embedding the connections screen documentation for implementation details.

We are pleased to announce the following component has been recently added to the Prismatic library:

• Okta - Okta is an identity and access management platform that provides secure authentication and authorization services. Use the component to manage users, groups, applications, and access policies.