Using Integration Designer
You can create Integration flows in Event Designer under a project of type T24 Integration Project and you store the artefacts as XML documents with .event and .flow extensions.
This type of project is a versionable item that is typically stored in a source control as a model artefact. When required, an individual project is published in Transact along with all flows and events through an option provided in the event designer.
You need to prepare your environment creating new events and flows.
Creating an Event Designer Project
You need to create the Integration Framework project and specify the most important connection parameters.
When you create an event, you need to determine the exit point, its type and the application, version, component or service it will be attached to.
You need to define an Integration Framework flow and select the data to be collected in the integration events.
After you have defined an event and the flow for the event, you can publish the project to Transact. Publishing creates the necessary records in Transact applications.
You can delete a flow after publishing. You can delete a single flow or all the flows that are available in your Event Designer project.
Several applications are updated after the Event Designer project is successfully published to Transact.
Defining Events and Flows For a Specific List of Companies
Events and flow definitions are normally valid for all companies. There is a new requirement to define events and flow definitions for a specified list of companies.
Creating an Event Designer Project From Existing Flows and Exit Points in Transact
The Event Designer plugin allows you to use existing events and flows in Design Studio and publish them to Transact.
Selecting Multiple Application and Version Exit Points
You can select multiple application and version exit points.
This section allows you to correlate the asynchronous messages as the value is mapped from the request to Integration Event.
In this topic