Transaction Configuration Center - Enhancement - Automated Enhancement Functional Points - Data Functions - Variation - Modified AEFP with UNCHANGED source code

Purpose (problem description)

This page explains the case when there is Modified AEFP for Data Function 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 Data Functions between the 2 successive snapshots(Transaction which is part of the snapshot n+1 but not part of snapshot n), If this is the case refer to the node Enhancement > Data Functions
   1. if there is MODIFIED Data Functions, then investigate the root cause by referring to Transaction Configuration Center - Enhancement - Data Function - Status Variation - Data Function status is MODIFIED with unchanged source code
   2. Else if there is no MODIFIED Data Functions 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