Which action triggers updating a Module to reflect application changes?

• A. Right-click the module and select Rescan.
• B. Open the module and click Save.
• C. Delete the module and re-import.
• D. Rename the module.

Answer: (A)

Rescanning the module is what refreshes its element definitions to mirror changes in the application. When the UI evolves—new controls appear, existing ones change properties, or some disappear—performing a rescan rereads the live application and updates the module accordingly. This keeps the automated references accurate without needing to recreate the module from scratch.

Opening the module and saving simply preserves the current state and would not pull in new elements that occurred after the last scan. Deleting and re-importing would recreate the module from scratch, which is unnecessary for routine updates and more disruptive. Renaming the module only changes its label and does not affect the underlying UI mappings.