When you use the transformation in a publication workflow, you can notify the

Data Integration Hub

server that the publication process is complete and the published data is ready to consume. The

Data Integration Hub

server then creates child events for the subscriptions and triggers the subscription batch workflows for subscriptions that consume the data when it is published. Scheduled subscription events remain pending until the scheduled subscribers start to consume the data. The notification that the transformation sends is optional. Therefore, you can use the transformation to change the event status to error without triggering the subscriptions if the publication process ended with errors.

When you use the transformation in a subscription post-processing workflow, you must notify the

Data Integration Hub

server that the subscription post-process is complete and send the post-processing status to the server. The

Data Integration Hub

server then creates a child event for the subscription that evoked the post-processing workflow, with the status of the post-process.