Each workflow in the Process Designer starts with an Event.
|Click on the Event element under Activities on the left side and drag & drop it into the drawing area in the center.|
|By double-clicking on the shape, the event selection assistant opens. You can also open it by clicking on the right side underneath Subscribe event / Publish event.|
Each category is sorted and searchable.
|Widget Events||Events that are available for certain widgets, e.g. button press event.|
|Screen Events||Events related to screens, e.g. onInit and onAfterShow.|
|onAfterHide||This event is triggered when the app has made the screen invisible. In the case of animated transitions, this event is triggered after the end of the transition. This screen will no longer be displayed and animated.|
|onAfterShow||This event is fired every time when the app has made this screen visible. In case of animated transitions this event is fired after the transition finishes. This screen is now being displayed and not animated anymore.|
|onBeforeHide||This event is triggered before the app hides the screen. For animated transitions, this event is triggered before the transition begins.|
|onBeforeShow||This event is fired every time before the app shows this screen. In case of animated transitions this event is fired before the transition starts.|
|onBeforeFristShow||This event is fired before the app shows this screen for the first time.|
|onNavButtonPress||This event is fired when Nav Button is pressed.|
|Custom Events||Individual events within an application that can be published and subscribed at any time.|
|System Events||Events related to devices, e.g. onDeviceGoesOffline and onOrientationChange.|
Create Custom Events
Publish Custom Events
|To use an event in other user stories, create a new Custom Event on the Publish Event tab.|
|A shortcut for creating Custom Events is located in the upper right corner.|
Subscribe to Custom Events
Subscribe to a custom event in another user story to connect the logic between different user stories.
You have a process in User Story 1 that contains a condition to check if an input field is filled out after clicking on a “Login” button. Afterwards, the user should be navigated forward to the next screen.
Imagine you have the other user story exclusively for the whole navigation of your application. So you want the end of the event from User Story 1 (the navigation) subscribed to User Story 2.
Therefore we published the new Custom Event “LoginButton” in User Story 1 and subscribed to it in User Story 2.
|User Story 1|
|User Story 2|