Use Metadata in Integrations

You can access the integration name, identifier, and version instead of hardcoding those values in integrations. You can also access runtime data and environment data inside the integration.

The following metadata is exposed in integrations. This metadata can be used in the mapper and actions that include the Expression Builder such as assign, log, notification, and others.

• Integration
  • Name
  • Identifier
  • Version
• Runtime data
  • Instance ID
  • Invoked by name
• Environment data
  • Service instance name
  • Base URL

The following use case provides a high-level overview of using metadata in an integration.

1. Create and design an orchestrated integration.
2. Add an action that includes an Expression Builder.
   For this example, a log action is added.
3. In the source tree, find the integration metadata.
4. Add the required metadata to the Expression field. For this example, a concat function is used to include the integration name metadata.
   
   
   Description of the illustration metadata-log-action.png
   
   
5. Complete design of the integration.
6. Activate and run the integration.
7. Go to the Track Instances page.
8. Click the business identifier of the integration.
9. Select View Activity Stream from the menu in the upper right corner.
10. Scroll down and note that the log message in the activity stream shows the integration name (for this example, Hello-World).
    
    
    Description of the illustration metadata-activity-stream.png