Sequential test approval chains of up to six approvers now let release owners enforce who reviews test readiness and results, and in what order, before a regulated release proceeds. That matters when evidence, accountability, and segregation of duties must withstand internal or external scrutiny.
Govern test decisions with ordered approvals
Panaya Testing now supports multi-step approval workflows for both pre-execution test review and post-execution sign-off. Each approver completes their review in sequence, preventing later approvals from bypassing earlier control points.
For release governance, this creates a clearer decision record across QA, business process ownership, security, compliance, and release management. It also reduces the reliance on email-based approvals that are difficult to reconcile with the test record.
Key operating considerations include:
- Define which applications, release types, and risk classes require multi-step review.
- Map each approval step to a named role, not an informal individual dependency.
- Set escalation rules for unavailable approvers and overdue decisions.
- Retain approval evidence with the test cycle and release decision.
Multi-approver review is available through Panaya's Compliance Package, which includes electronic signatures and advanced regulatory compliance features. Teams should confirm package scope and control requirements before changing their release process.
Make recorded test evidence faster to assess
Video Recorder now produces AI-generated summaries for recorded manual test executions. The summary highlights principal steps and the overall outcome, allowing reviewers to understand the execution without starting with the full recording.
This is useful for test managers overseeing high execution volumes, release owners reviewing exceptions, and audit teams sampling evidence. The original recording remains important where detailed verification is required; the AI summary is an acceleration layer, not a replacement for source evidence.
Built-in feedback capabilities allow teams to report on summary quality. That feedback should be governed: assign ownership for reviewing recurring inaccuracies, identify test types that need full-video review, and avoid treating AI output as an unverified approval artifact.
Generate tests that better reflect business process flow
BPMN-based AI test generation now provides broader end-to-end workflow coverage while maintaining alignment with the defined process logic. Teams can add optional instructions to guide generated tests toward their business context.
The release also identifies transaction codes in uploaded BPMN files and creates dependencies based on the process flow. This gives test leads a better starting point for execution sequence, data preparation, and cross-process coverage.
The governance value is practical: process diagrams can be turned into traceable test assets more consistently. Still, process owners and QA leads need to validate generated scenarios, exception paths, authorization conditions, and local configuration differences. Generated does not mean approved.
Improve SAP remediation and impact-based testing
AI-Assisted Code Corrections is now generally available in all S/4Code projects. Seemore Intelligence analyzes identified issues and proposes corrections, with expanded SAP domain knowledge, additional correction scenarios, access to SAP resources, and feedback mechanisms for recommendation quality.
For SAP engineering leaders, the main outcome is a more structured path from finding to proposed remediation. Developers remain accountable for reviewing proposals, assessing side effects, applying coding standards, and proving the correction through required testing.
Impact Analysis projects also add AI-powered Unit Test Guidance. The new Summarize impact action reviews notes tied to relevant corrections and proposes testing scenarios based on impacted business logic and code changes.
Additional SAP delivery improvements include:
- Fiori impact analysis now detects Business Catalog, Business Group, and Business Role changes.
- Detected Fiori changes appear as dedicated corrections linked to relevant configuration and Unit Tests.
- High-volume ATC findings can be aggregated into one correction with an attached Excel report.
- Re-evaluation reasons include explanatory tooltips to clarify pending actions.
- The Delivered Support Packages page now uses the modern Panaya interface.
These changes reduce review friction in large SAP portfolios. But teams need clear thresholds for grouped ATC findings, because aggregation can simplify management while also hiding issue-level prioritization if the supporting report is not reviewed.
Strengthen identity and partner administration
Administrators can now designate any user to receive automatic notifications for scheduled and completed user deactivations. Security, compliance, and operations teams can therefore be included in offboarding visibility without relying on one administrator's mailbox.
A new optional System Integrator entity supports partners managing multiple customer accounts. System Integrator users can be associated with one or more customer accounts, and administrators can manage those associations in Panaya.
Both capabilities should be incorporated into access governance routines:
- Route deactivation notices to accountable security and service-management roles.
- Review partner-to-customer associations on a defined schedule.
- Document who can assign, change, and remove account relationships.
- Validate that customer access is limited to contracted responsibilities.
Users can also record their job title in profile settings, while administrators can manage titles. Panaya uses this information to provide role-relevant AI content, insights, and recommendations. Organizations should establish ownership for profile data quality and ensure job-title handling follows their privacy and HR-data policies.
Release-owner actions for July 2026
Release owners should assess the new functions as workflow changes, not simply interface enhancements. Start with the controls that affect production authorization, evidence review, and external-party access.
Recommended next steps:
- Pilot multi-approver chains on a high-risk or regulated release stream.
- Define acceptance criteria for AI video summaries and BPMN-generated tests.
- Add AI-assisted SAP correction review to existing development and code-review controls.
- Review deactivation notification recipients and System Integrator account associations.
- Measure approval cycle time, evidence-review effort, and test-coverage quality after adoption.
How Merito helps
Merito helps enterprises configure Panaya TestDynamix/Seemore capabilities around real delivery controls rather than default settings. We can design approval workflows, evidence-retention practices, SAP test and remediation governance, partner access models, and rollout metrics that fit your release model.
The goal is clear: faster review where risk permits it, and defensible controls where risk demands it. Teams get a workable operating model, not just features enabled.
Merito is an authorized Panaya reseller and services partner. Our Panaya TestDynamix/Seemore team can scope licensing, sizing, and rollout for July 2026, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.