Multi-approver test review and sign-off now lets release owners require up to six sequential approvals before test execution begins or results are accepted. That creates a clearer control point for regulated releases, where the order of review and the evidence behind a decision matter as much as the final test status.
Controlled approvals for regulated testing
The August release adds sequential approval workflows for both pre-execution test review and post-execution sign-off. Each designated approver completes their review in order, rather than relying on informal confirmation across email, chat, or disconnected tools.
For release governance, this can help teams:
- Establish accountable approval gates before critical testing starts
- Record who approved evidence and when they approved it
- Reduce ambiguity around test-result acceptance
- Support segregation of duties across QA, business, and compliance roles
Multi-approver review is available through the Compliance Package, which includes electronic signatures and advanced regulatory compliance functions. Governance teams should define which test cycles require the control, who can delegate approvals, and what happens when a reviewer is unavailable.
Faster review of manual-test evidence
Panaya Video Recorder now produces AI-generated summaries for recorded manual test executions. The summary highlights the key steps and overall outcome, allowing a test lead or release manager to assess a recording before deciding whether detailed playback is needed.
This reduces the time required to triage evidence during a release window. It does not remove the need for evidence standards: for high-risk scenarios, teams may still require the original video, linked defect records, and approval history. Built-in feedback on the AI summaries gives organizations a way to identify inaccurate or incomplete outputs and improve their use over time.
BPMN-based tests gain process context
AI-generated tests from uploaded BPMN models now provide broader coverage of end-to-end workflows while maintaining closer alignment with defined process logic. Teams can add optional instructions to guide generation for their own controls, process variants, or testing priorities.
The release also identifies transaction codes in BPMN files and populates them into generated tests. It creates test dependencies from the process flow, preserving expected execution order across related tests.
For SAP and business-process owners, this helps shift BPMN from a reference artifact into a more useful input for test design. Review remains essential: process models may not capture authorization exceptions, custom developments, data conditions, or local operating procedures.
SAP delivery intelligence expands
AI-Assisted Code Corrections is now generally available for all S/4Code projects. Seemore Intelligence analyzes issues and proposes correction approaches, with expanded SAP domain knowledge, additional correction scenarios, improved access to SAP resources, and a feedback mechanism for recommendations.
The operational value is not merely faster code changes. Development leads can use the proposals to standardize remediation review, focus experienced developers on exceptions, and retain a more consistent rationale for corrective work. Proposed code changes should remain subject to established peer review, security review, transport controls, and testing requirements.
Impact Analysis projects also gain AI-powered unit-test guidance. The new Summarize impact action reviews notes associated with relevant corrections and produces recommended testing scenarios based on affected business logic and code changes. This can improve early test planning, especially where developers need a concise view of downstream risk before building unit tests.
More complete SAP impact and ATC management
S/4Accelerate now detects Fiori configuration changes across Business Catalogs, Business Groups, and Business Roles. These changes appear as dedicated corrections with links to the relevant configuration and associated unit tests.
This is important because Fiori authorization and configuration changes can affect user access and process behavior without a conventional code change. Including them in impact analysis helps release teams bring functional, security, and QA review into the same planning flow.
For large S/4Code environments, high-volume ATC findings can now be aggregated into a single correction with an attached Excel report. This makes large analyses easier to manage without losing the detailed findings needed for remediation planning. Re-evaluation reasons also include explanatory tooltips, helping teams understand why processing is blocked and what action is required.
Administration, access, and partner operations
Administrators can designate any user to receive automatic notifications about scheduled and completed user deactivations. Security, compliance, and operations teams can therefore be informed without requiring a manual communication process for every change.
A new optional System Integrator entity supports partners managing multiple customer accounts. System Integrator users can be associated with one or more accounts, and administrators can maintain those associations from within Panaya. Organizations using this model should set explicit rules for account access, administrator authority, and periodic access review.
The release also introduces job-title fields in user profiles, managed by users or administrators. Panaya uses this information to tailor AI content, insights, and recommendations by role. Treat job-title data as governed profile information: define approved values, determine who may edit them, and assess privacy requirements before making the feature part of a wider AI operating model.
Recommended adoption sequence
Enterprise teams can reduce rollout risk by taking a staged approach:
- Identify regulated or high-risk test cycles for multi-approver workflows.
- Define evidence rules for AI video summaries and full recording review.
- Pilot BPMN generation on a well-maintained business process.
- Validate SAP AI recommendations through existing development and test controls.
- Update access-offboarding notifications and partner-account governance.
Measure results using approval-cycle duration, evidence-review effort, test coverage against process steps, remediation lead time, and the rate of AI outputs requiring material correction.
How Merito helps
Merito helps enterprises operationalize these capabilities rather than treating them as isolated product settings. We can assess current QA and SAP change controls, design approval and evidence workflows, establish AI-use guardrails, and define reporting that gives release leaders a defensible view of risk.
For teams working across SAP, QA, security, and external delivery partners, Merito also helps clarify ownership for access changes, process-model quality, generated-test review, and audit retention. The goal is practical adoption that fits existing delivery governance, not a parallel process people bypass.
Merito is an authorized Panaya reseller and services partner. Our Panaya TestDynamix/Seemore team can scope licensing, sizing, and rollout for August 2026, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.