ScriptBuilder now warns users when a newer script version was saved in another session before their own changes are saved, giving release owners a direct control against accidental overwrites. In 26.09.105, teams can reload the latest version or deliberately save over it when that decision is approved.
Protect collaborative script changes
Concurrent editing is a practical delivery risk in shared automation repositories. A tester may spend time updating a script while another contributor completes and saves related changes. Without a save-time check, the later save can replace valid work and create avoidable investigation, retesting, and release delay.
The new version conflict detection introduces an explicit decision when Panaya finds that the saved script is newer than the version currently being edited:
- Reload Latest refreshes the work with the most recently saved version.
- Save Anyway intentionally overwrites the newer version.
For QA leaders, this creates a clearer accountability point in the authoring workflow. For regulated or high-control programs, teams should document when Save Anyway is acceptable, define ownership for shared business-process scripts, and retain review practices around material script changes.
Review visual differences with more context
Compare Mode now detects screenshot differences automatically and highlights them as regions in the compared images and in a dedicated list. Each detected region is classified as one of the following:
- Layout for structural or placement changes
