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
- Style for visual presentation changes
- Content for displayed-value changes
Reviewers can also set comparison sensitivity from Strict to Relaxed. That matters because visual evidence needs context: a content change may identify an incorrect order total, while a style change may be an expected result of a UI library update. Classification helps teams focus triage on differences that could affect business controls or user outcomes.
Release managers should define tolerances by application type and test purpose. Strict comparison may be appropriate for controlled forms, labels, and critical approval screens. A more relaxed setting may be appropriate where rendering variation is expected, but it should not replace functional assertions for business-critical values.
Extend SAP change impact coverage to Fiori
Panaya now identifies SAP Fiori entry points covered during automated test execution. When a test launches a GUI HTML application from SAP Fiori Launchpad, Panaya captures the corresponding transaction code. For SAPUI5 applications, it captures the Fiori App ID.
These identifiers link automated coverage to SAP Change Analysis. This gives change and release teams a more complete view of which automated tests are relevant to proposed SAP changes across both traditional SAP GUI paths and Fiori applications.
The workflow impact is concrete:
- Change owners can identify affected automated tests earlier.
- QA teams can prioritize regression scope using captured application entry points.
- Release governance can show why a test was included or excluded from a change-validation decision.
- SAP programs gain better traceability as process flows move between GUI and Fiori experiences.
This does not remove the need to validate test relevance, especially for cross-application processes. It does provide evidence that makes scope decisions faster and more defensible.
Support multilingual SAP test execution
The SAP Connection configuration now includes a SAP Logon language setting. Panaya uses the configured language when establishing the SAP connection for automated testing.
For global SAP programs, language is not a cosmetic setting. It can affect labels, messages, data-entry behavior, and the evidence needed for regional business acceptance. Defining the language at the connection level reduces avoidable environment variation and makes intended execution context visible to teams maintaining test suites.
Organizations should govern language-specific connections alongside access controls, test data, and agent assignment. A small configuration difference can otherwise produce failures that look like application regressions.
Improve daily data-set maintenance
Users can now customize column order and widths in the Data Sets tab. The selected layout is retained for that user across tests and future logins.
This is a usability improvement, but it has operational value for teams managing wide, data-driven suites. Testers can keep high-use identifiers, environments, and business inputs visible without repeatedly adjusting the table. It reduces routine handling time; the underlying data permissions and controls remain unchanged.
Governance considerations for release owners
Version 26.09.105 adds useful controls and evidence, but outcomes depend on operating discipline. Teams should consider the following actions after adoption:
- Define when script overwrites require peer review or release-owner approval.
- Set visual-comparison tolerances for different test classes.
- Confirm Fiori entry-point capture is reflected in SAP change-assessment procedures.
- Standardize SAP connection language configurations by region and test purpose.
- Train reviewers to distinguish Layout, Style, and Content differences during triage.
These steps make the new capabilities part of controlled delivery rather than isolated product settings.
How Merito helps
Merito helps enterprise teams implement Panaya Test Automation controls in the context of their delivery model. We can map script ownership and review workflows, define evidence and comparison standards, connect SAP Change Analysis outputs to release gates, and establish governance for SAP connections, agents, and data-driven test suites.
The aim is practical: reduce rework from conflicting changes, improve confidence in regression evidence, and give release decision-makers a clearer record of what was tested and why.
Merito is an authorized Panaya reseller and services partner. Our Panaya Test Automation team can scope licensing, sizing, and rollout for 26.09.105, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.