Transaction Configuration Center - AFP Calibration - Transactional Functions - Wrong Links

The main purpose of the page is to troubleshoot wrong links that lead to an unexpected transaction.

Here is an example of an unexpected transaction:

1. 1. If the link is bookmarked in the source code (the link is pointing on specific part of the source code) that means it has been resolved by the analyzer. If it is not expected, then this is a bug in the Analyzer. In that case, contact the support team and provide the Relevant input.
   2. If there is no bookmark, check the link property by selecting the link and push F12 and check the project related to this link --> If the project is AppView that means that the link has been added manually via Enlighten.
      
      If the link does not exist in Enlighten:

   3. The link that are appearing in the Transaction view are saved in the ctv_links view. To check that the issue is not a display issue, refer to SQL Queries - CAST Knowledge Base - Queries on Transactions - How to get the list of analyzed links eligible to be part of Transactions

   4.  If a row is raised, that means that the link exist before running the Function Point Computation. This means, that the link has been removed after running the Function Point Computation.
2. If the action above does not resolve the issue, contact support team with the below relevant input
   

Relevant input

• Sherlock export : Backup, log files and source code are required for investigation.
• Screenshot showing the wrong link in Enlighten and in the unexpected transaction and justification of why it is unexpected transaction.