|
5.8 How to Model Events That May Go To Different Places It is possible to draw events on the diagram that are just there as documentation, ones that we would like to see be not generate anything from. A single button may go to several different pages depending on code run during the event. If you want to show all possible flows, and normally you should, but you don't want lots of different buttons to appear on the page, you can do this by setting the forwardId property on the event to refer to the principal event (the one you want the button to be created for). It doesn't actually matter which of the modeled events you decide to call the principal event, as long as only one of the events does not have the forwardId property set. All the other properties of the event, eg the userNameBase, the businessMethod etc will be take from the values on the principal event.
In effect if the forwardId property is set on an event, the event will be ignored. To make the event go to different places, add a business event to the master event (the one without the forwardId set) and add code (or get the application programmer to add code) to the event that conditionally sets the forward page to the alternative page. Links:
Copyright © 2001-2006 New Technology / enterprise Ltd. | |||||||||||||||||||||
