Impact Analysis projects now deny direct, email-link, and API access while processing, preventing a release owner from inheriting conflicting project changes. The control also logs out active users until processing finishes, protecting the integrity of analysis results before downstream decisions are made.
Protect analysis results while they are being calculated
Impact Analysis often informs high-consequence decisions: remediation scope, regression-test selection, deployment timing, and release approval. Allowing updates while the analysis is processing can create uncertainty about which project state produced the result.
The new temporary restriction closes that exposure across the main entry points:
- Direct project access is unavailable during processing.
- Links from Panaya emails cannot bypass the restriction.
- API interactions are restricted during the same period.
- Active users are logged out until processing is complete.
For delivery leaders, this creates a clearer control point. Analysis output can be reviewed as a consistent snapshot rather than a moving target. Integration owners should account for temporary API unavailability in retry logic, job monitoring, and support runbooks.
Scale administration and strengthen account protection
New User Management APIs provide retrieval of individual user data, filtered user lists, and filtered user-project-role associations. This gives IAM, platform, and PMO teams a more practical way to reconcile access information with enterprise directories, role reviews, and internal administration processes.
The release also adds authenticator-app support for multi-factor authentication. Users can configure Microsoft Authenticator or Google Authenticator alongside email verification and select their preferred supported method.
These additions support two related governance needs:
- Better visibility into who has access to which projects and roles.
- More resilient account protection without relying only on email-based verification.
Organizations should define the authoritative source for user status, establish periodic role-certification reviews, and document offboarding timing. The APIs provide useful data access; they do not replace ownership of identity governance.
Reduce defect noise and improve traceability
AI Duplicate Detection identifies likely duplicate defects while a user is creating a new record. It displays relevant matches with similarity levels, allowing the reporter to link the issue to an existing defect or stop creation when the issue is already covered.
This changes the point at which duplicate control occurs. Instead of asking triage teams to clean up duplicates after they enter the backlog, teams can reduce unnecessary records at intake. The outcome is a more reliable defect count, lower investigation effort, and clearer accountability for root-cause work.
The defect list also now includes a Linked Defects column. Teams can see the number of linked defects directly in the list, report on that information, and drill into the Linked Defects tab.
For QA and engineering managers, linked-defect visibility helps distinguish isolated failures from related problem clusters. It can also improve release-risk discussions when one underlying issue affects multiple tests, components, or business processes.
Apply compliance approvals at the cycle level
Customers with the compliance package can define an approval workflow at the cycle level and have it applied automatically to tests in that cycle. Individual tests may use a Custom workflow when an exception is warranted.
Importantly, changes made later to the cycle-level workflow do not alter existing approval processes. That behavior matters for auditability: completed or in-flight work retains the approval context under which it was initiated.
This feature supports a practical balance between standardization and controlled exceptions:
- Set a default approval path for a regulated test cycle.
- Use Custom workflows only where risk or ownership differs.
- Retain historical process evidence for reviews and audits.
- Reduce configuration effort across large test inventories.
Teams should define who may create exceptions, what justification is required, and how exception use will be reviewed. A workflow alone is not governance; consistent administration is what makes it credible.
Put limits around AI-assisted SAP corrections
For S/4Code, S/4Convert, and S/4Accelerate projects, Panaya now blocks saving an Assisted Code Correction that changes 90% or more of the current source code. The user must review and refine the proposed fix before saving it.
The safeguard addresses a clear risk: a broad AI-generated correction may be technically plausible while carrying a change scope that is not suitable for automatic acceptance. Requiring review before save supports code-quality controls, segregation of duties, and accountable change approval.
Fix Summary is also simplified into four sections:
- Issue
- Root Cause
- Solution
- Open Items
This structure makes it faster for reviewers to understand the proposed correction, its rationale, and remaining follow-up. It is particularly useful when technical reviewers, functional owners, and release managers need a common record of the decision.
AI-powered unit-test impact summaries are now invalidated when relevant corrections or Notes change. The next generated summary therefore reflects newly added, removed, or out-of-scope corrections and Notes. This reduces the risk of planning or approving work against stale impact information.
Operational priorities for release leaders
September's features are most valuable when teams adjust the supporting operating model. Release owners should validate that controls, reporting, and integrations reflect the new behaviors before relying on them in a critical delivery window.
Recommended actions include:
- Update integration retry behavior for processing-time API restrictions.
- Review MFA enrollment guidance and recovery procedures.
- Establish duplicate-defect handling rules and measure duplicate avoidance.
- Define approval-workflow owners and exception criteria by test cycle.
- Add review checkpoints for large AI-assisted SAP corrections.
- Include linked-defect metrics in release-readiness reporting.
How Merito helps
Merito helps enterprises configure these capabilities within the wider delivery model: identity governance, test-process controls, defect taxonomy, approval evidence, SAP change management, and CI/CD operating procedures. We can assess current workflows, define control ownership, and support implementation so new product behavior produces measurable risk reduction rather than another isolated configuration change.
Merito is an authorized Panaya reseller and services partner. Our Panaya TestDynamix/Seemore team can scope licensing, sizing, and rollout for September 2026, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.