No Code Mapping & Transformation UI
One of the core capabilities of Micro-Integrations is to be able to apply light transformation & mapping capabilities directly in the Micro-Integration event stream, whether it be from an external service to the event mesh or from the event mesh to an edge service.
It is quite common to require a different layout to the payload and/or make use of provider-specific headers when integrating these edge services with your Solace-based EDA.
Solace introduces this new transformation capability to all PubSub+ customers using Micro-Integrations via a no-code user interface (UI) with the following features:
- Source and Target payload imports
- Supports JSON sample payloads in this beta
- Allows for access to the individual fields of a source payload for mapping
- Allows for setting of individual fields in the target payload
- Transform functions
- Common string and number functions to transform source values to a desired target format
- More functions being added after initial beta list to cover even more use cases
- User-defined Contants
- Perfect for static values used in transforms such as delimiters, prefix/suffix strings, and other custom, fixed values
- Smart Topic Destination target value
- Allows for dynamic publisher destinations set by a runtime transformation that overrides the fixed, design-time destination
- Any source value can be used to construct the Smart Topic Destination
- Source headers values
- Source payload field values
- User-defined Constant values
- The transformation UI is currently in Beta and has the following guidelines:
- Source and Target payloads must be a valid JSON document that provides a “sample” payload. This is used to identify the individual fields and structure of the expected source payloads and what the expected target payload should look like after mapping/transformation.
- Arrays can only be mapped to other arrays. Arrays cannot be transformed in this release.
- Mappings support a single transformation in this release.
Map With AI (experimental)
Also, part of this new UI is an AI Assistant to automatically map and transform your source payload items to your target payload.
How to use Map with AI
- Load a JSON payload to the Source Payload area
- Load a JSON payload to the Target Payload area
- Click the “Map with AI” button in the top right
- A dialog appears to warn you that this action will erase any previous mappings. Click to confirm (or cancel to preserve your mappings)
- The AI assistant will look at your source and payload and use an LLM to determine possible mappings and add transforms as needed.
Things to note:
- This feature is “experimental”. Expect some rough edges.
- Be patient - depending on the size of your payloads, the Map with AI can take several minutes to complete
- If you don’t agree with the mappings, you can highlight the ones you don’t want and delete them
- You can only do Map with AI on the creation of a Micro-Integration. It is not available in edit mode of an existing MI
- Map with AI only works on payloads at this time. Headers are not AI mapped
You can check out this new capability in a demo video here.
We are very interested in feedback on the mapping UI and Map with AI features. Let us know how you get on!