Customer users can now build and deploy their own custom components, and can use those custom components in integrations they build in your embedded marketplace. This is handy if your customers need to build custom components to interact with their own internal systems, or if they need to build custom components that interact with third-party apps that you don't already support.

Read more about customer-scoped custom components on the Embedded Designer article.

Two new features were added to embedded designer:

1. You can now issue a prismatic.showDashboard() to give users a holistic view of their integrations, instances, executions, logs, and more. See docs for more information.
2. You can now filter the list of components that are available to your customers. See docs for more information.

Your customers may want to build integrations for themselves between your product and the other apps and services they use. Embedded designer allows your customers to log in to your app and build integrations using Prismatic's integration designer. You can provision your customers access to private components that you have built, and can provide your customers with "templates" that they can use as a starting point for building their own integrations.

Read more about the embedded designer on Embedding Integration Designer docs page.

If you're interested in using embedded designer, please contact support to discuss enabling embedded designer for your organization.

The newest version of the embedded SDK changes the Marketplace default of screenConfiguration.marketplace.configuration to allow-details instead of always-show-details. See docs for information on the integration configuration detail screen options.

Along with embedded designer comes a new embedded SDK. If you are currently using @prismatic-io/marketplace for embedded marketplace, swap it out for the new @prismatic-io/embedded NodeJS package to begin using the embedded designer features. @prismatic-io/marketplace will continue to work, but @prismatic-io/embedded is a superset of features and new features and enhancements will only be added to the new embedded SDK.

You now have options for configuring how and if a marketplace user should access the integrations configuration details screen. This includes the ability to prevent a marketplace user from accessing the instance configuration details screen. This is useful if your customers should not access the Test, Executions, Monitors or Logs functionality. Check out our docs for more information.

Your customers can now enable multiple instances of an integration through embedded marketplace. This allows your customers to set up several copies of an integration of themselves, each with different configurations.

Check out our docs for more information.

Granular config variable and connection input settings allow your org to better control who can see and set integration configurations values. Read more in docs.

You can now use logical operators like and, or, startsWith, notEqual and more to filter the integrations in your embedded marketplace. For example, if you would like to show all integrations that have a category "ERP" and label "paid", and would also like your Dropbox and Slack integrations to be displayed, a filter could look like:

[
  BooleanOperator.or,
  [
    BooleanOperator.and,
    [TermOperator.equal, "category", "ERP"],
    [TermOperator.in, "labels", "paid"],
  ],
  [TermOperator.equal, "name", "Dropbox"],
  [TermOperator.equal, "name", "Slack"],
];

Read more about advanced filters in the docs.

Not all of your customers speak English. You can now offer translations for embedded marketplace, so your customers can enable integrations in their native language.

See Embedding Marketplace for information on how to offer i18n support to your customers.