Zeenyx Software

While it is not always necessary to name the selector when using it to select a row in a table, it is always good practice.  In the example below, the row is selected using the ‘customer id’:

The action to select the row uses the selector ‘SelectByCustomerId’, but it does not actually specify the selector. Instead only the value of the selector, represented by the variable ‘CustId’, is specified:

Because the name of the selector is specified, its relative order in the AppObjects definition will not affect the result.

That action only works because the seclector SelectByCustomerId is listed first under its corresponding row (see the right most arrow in the figure above). If the selector called ‘SelectByLastName’ were moved up one line so that it was the first listed selector, then the action would fail. A more robust way to define an action that uses a selector is to specify the name of the selector along with its value as in the updated example below:

Because the name of the selector is specified, its relative order in the AppObjects definition will not affect the result.