
When you model a business process, you can generate a UI component for message triggers, either via the process diagram editor and the properties view, or via the project explorer.
You have opened the Process Development perspective in the SAP NetWeaver Developer Studio, and have expanded your project in the Project Explorer view.
You have modeled a process containing start or intermediate message events.
You have created the necessary service interfaces and operations with data types assigned.
When you model a process, you use message triggers to assign them to the start or intermediate events in the process. At runtime, the message can be triggered via SOAP Web Service, BPM OData Service, or BPM Public API. The generated UI component uses the BPM OData Service to interact with the BPM system.
For more information about the prerequisites and details of interacting with BPM via OData, see BPM OData Service.
When you model a message event, you have the option to create a message trigger for it, using the Event Trigger tab in the event’s Properties view. The event trigger is automatically assigned to the event. You can also create a new message event trigger via the context menu of the Event Triggers folder in the Project Explorer view. Both options allow you to generate a UI component for the newly created message event trigger.
The generated UI component is based on the input message data type of the service operation selected for the message event trigger. For more information, see Creating Service Interface Definitions.
The UI component is generated automatically using SAPUI5 technology. It is created in the respective development component (DC), which is a Web DC. You can create the UI component in an existing or in a new DC. For more information, see Creating a Project.