October 8, 2015 at 9:36 am #802
The “On Boundary Event” event is a bit of a misnomer I’m afraid. Certain SPARK controls (like buttons, icons, navigation event, etc…) trigger boundary events that cause navigation in the service diagram. Any number of things can be modeled in the service diagram when a boundary event is fired (e.g. call 1 Server Script, 1 Web Service, 1 General System Service, strung together and ending in a Stay-on-Page event. “On Boundary Event” exists for navigations that end in a Stay On Page event. Due to the asynchronous nature of boundary events, one cannot predict when the Stay On Page event may be reached. The “On Boundary Event” exists for this purpose. It is fired asynchronously and only when the “Stay on Page” event has been reached.
You must be logged in to reply to this topic.