To enable events tracking and use a custom ID for a given flow in Mule 4. As per the Mule-4-business-events there is only a check-box to enable this for a flow and no way to customise the ID used as was the case in Mule 3 Business Events.
In order to set the transaction ID for Business events then you will need to utilise the new connector "Set Transaction ID" available in the palette, which will allow you to specify the value for the Transaction ID as was previously the case in the Flow configuration in Mule 3. There is no need to enable the default event tracking check-box on the flow when utilising this connector.
This is configured exactly as was the case with Mule 3, you may enter an expression to create a unique ID for each flow invocation or a static value as is required.
Do be aware that this connector should be placed near the start of the flow, otherwise if an exception is raised in the flow before this connector is triggered it may result in the transaction logging a default ID instead of the custom ID configured.
001116036

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.