What is the correct sequence to update a Module after the application changes?

• A. Open the application page; Navigate to the Module to be changed; Right-click and select Rescan; Apply the changes to the control objects; Save the scanned Module.
• B. Open the application page; Right-click the Module; Rescan; Navigate to the Module to be changed; Save the scanned Module; Apply the changes.
• C. Navigate to the Module to be changed; Open the application page; Save the scanned Module; Apply the changes to the control objects; Rescan.
• D. Right-click and select Rescan; Open the application page; Navigate to the Module to be changed; Save the scanned Module; Apply the changes to the control objects.

Answer: (A)

Updating a Module after the application changes follows a specific order so Tosca can refresh the correct controls and keep the module in sync with the UI. Start by opening the application page to bring the app context into view. Then navigate to the Module you need to change so you’re targeting the right component. Next, perform a Rescan to refresh the discovered controls based on the current UI; this is how Tosca detects what has changed. After scanning, apply the updates to the control objects so the new or changed controls inherit the correct properties and locators. Finally, save the scanned Module to persist those updates.

This sequence ensures you scan in the right context, update the control information, and then save the results, which is why it’s the best fit. Other sequences skip or reorder these steps in a way that could update the wrong module, miss new controls, or fail to persist the changes.