Best Practices while Declaring Multiple Applications within Same Project

This section describes the best practices for declaring multiple applications within same project.

You can declare multiple SAP GUI applications within the same project. When you start the SAP GUI application, each of these declared applications will get a LOAD event as shown in the following screenshot:

Therefore, you can use these screens declared across different application declarations in single automation.

The following is the best practice we recommend while declaring multiple applications within the same project.

SAP Logon Capture

The SAP Logon Capture must exist inside all the declared applications even though they are mutually exclusive sets of screens. If SAP Logon Capture does not exist inside any one of the declared applications, there will be issues while generating the UNLOAD event of that application.

Refresh on Polling

  • If Refresh on Polling is set to “No” in at least one of the declared applications, the polling of SAP GUI will not start when the project gets downloaded into the agent.

  • When the automation starts, the polling can be started or stopped by using the Start Advanced Listening Screens and Stop Advanced Listening Screens activities on an SAP Logon screen of any declared application.

  • You must call the Start Advanced Listening Screens and Stop Advanced Listening Screens activities only in the beginning and the end of the main automation workflow. It is not recommended to call these activities in a sub-automation or a reusable package from the store since calling the Stop Advanced Listening Screens activity in the middle of the automation will UNLOAD all the SAP GUI pages and stop the polling thread.

Polling Delay

The minimum value of the polling delay will be considered across all the declared applications.