SaaSphalt Help Center
 Search  


collapse all | expand all
Events
Solution No. 57

Applications have to wait for a user to do something before it can complete its task. For example: anytime you click the Save button, you are telling the application to save whatever is on the screen. Your mouse click is an example of an event

The following is a list of the Events that are used in SaaSphalt:


Click: This event involves a user using a mouse to click on an object. Obviously this is most common in buttons, but it can also be used elsewhere - text objects, icons, and even grids (see below).


Change: This is often used in text objects, if the user deletes or changes what’s in an input box.


Focus: Focus refers to which object is highlighted when a screen first loads. A user can give an object focus - for example, by moving the cursor to a text input box upon loading.


Lose Focus: It’s focus in reverse! If the user is finished with one input box and clicks away, the initial object loses focus.


Add Event: This might sound confusing because of the language we’re using, but for this instance we’re just talking about adding an event (like a birthday party or a meeting) to a calendar object.


Event Click: This event is also unique to the calendar object. If you click on an event (like a birthday party or a meeting) this is considered an “event click” event.


Edit: This event is unique to the calendar object too, and it refers to editing the calendar itself by dragging elements around to resize.


Selection:  This event is another calendar object, that refers to selecting a given aspect of the screen, like an activity. Selecting the activity can cause an action to be triggered.


Row Click: This is similar to a click event, only it pertains to grids - when the user clicks on the Row in the grid. For example: if you clicked on a contact in the Contacts grid, it might initiate an Action to take you to the View Contact screen. That’s a Row Click Event!


Custom Row Click: Unlike row clicks, the custom row click event pertains to dropdowns. For example: you have a dropdown for colors (say red, blue and green). What if you wanted to add a new color directly from that dropdown without having to manually navigate to the New Color screen? By adding a custom row click event, you can attach a Go To Screen action to that “row” in the dropdown, which will allow you to go to the New Color screen directly from there.


Load: This event refers to when a screen loads - for example, if you click the reload button or navigate to it for the first time. It’s important to note that returning to a cached version of the screen (say, by hitting the back button) doesn’t constitute a “load” event.


Before Update: An update happens when you load a screen containing data. For example: if you add a new contact and then load your Contacts list. SaaSphalt updates the data on that screen to reflect the new entry, so this event happens right before the update does.


After Update: Much as above, only the event is the update itself!


Active record change: This event refers to the screen as a whole. Basically, in order for a record to be considered “active” it has to be passed onto the next screen to load. For example: if you click on John Smith in your Contact list it redirects you to John Smith’s View Contact screen. That’s because the record associated with John has been forwarded to the View Contact screen so SaaSphalt knows which information to populate it with. This movement is an event!


Close: As you might imagine, this event is when the screen is closed.