When capturing applications, you can choose to attach a separate Login application to improve synchronization time to mobile devices. Create the Login application separately, and link it to the application.
Link two applications together through a “login” relationship. This is a new relationship in UA 8.0, in addition to the existing ones of “delete,” “insert,” “update,” and “verification.”. If an application is related to another via a “login” relationship, the following applies:
During Web Studio preview, when editing an application that has a linked “login” application, the login application is executed silently. As a result, any back-end Web server context is established prior to executing the main application.
During off-line spidering (via the map-xml command), any linked “login” application is executed – but only once, to ensure that any required context is set. As a result, the login step is executed just once, rather than for each iteration through the spidering.
During normal on-line playback, if there is a login application, the login application is executed at least once in the same context as the main application. Context is maintained through JSESSIONID session context objects in UA along with the ContextId parameter (see “ContextID linkage across applications”).
If the login application cannot be executed automatically (for example, if it requires input, then the main application does not execute either. In this situation, it is expected that the login application is executed as an application in its own right first, and then the main application is executed through application linkage (by passing context).
