Transaction Configuration Center - Enhancement - Automated Enhancement Functional Points - Transactional Functions - Variation - MODIFIED AEFP with UNCHANGED code source

Purpose (problem description)

This page explains the case when there is Modified AEFP for Transactions in the evolution node, while there is no change in the analyzed code source.

Observed in CAST AIP

Observed on RDBMS

Step by Step scenario

1. Run at least 2 snapsots
2. Connect to TCC
3. Observe the variation

Action Plan

Perform the below actions

1. Check if there is MODIFIED Transactions between the 2 successive snapshots (Transaction is part of the snapshot n+1 but not part of snapshot n), for this refer to the node Enhancement > Transactional Functions
   1. If there is MODIFIED Transactions, then investigate the root cause by referring to Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transaction status is MODIFIED with unchanged source code
   2. Else if there is no MODIFIED Transactions then contact CAST Technical Support. with the following Relevant input
2. If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input

Notes/comments

Related Pages