CMS Application - Current Version - Unexpected Results

 This page will help you to troubleshoot the problems you may face related to current version tab and have unexpected results without any errors or warnings.

• Official documentation:

  • CAST AIP 8.3.x Documentation : CMS - Current Version tab
• CAST MS help Online : CAST Management Studio - Help > Infrastructure > Editors > Application Editors > Current Version tab

1. If the problem is that the deployment path in the package is not agreeing with the path shown for the analysis unit, then do the steps below to resolve this issue as a workaround.  An example of this case would be for a deployment path like S:\Sources\Application\Technology\code and also having an analysis Unit path of something like S:\Sources\Application (instead of S:\Sources\Application\Technology\code)

   1. Reject the current version - CMS - Delivery tab

   2. Cleanup the current analysis units having the wrong path - CMS - Clean up Analysis Units

   3. Add a new version and edit the path in the new version - DMT - Add a new version

2. Else Select the section you are interested in:
   
   • CMS Application - Current Version - Duplicate Analysis Unit for Maven poject exported to Cast-MS when excluded from DMT
   • CMS Application - Current Version - Missing project path in the list of Analysis Units in packages
   • CMS Application - Current Version - Unexpected Results - Analysis Units added to CAST MS when shown as ignored in DMT
   • CMS Application - Current Version - Unexpected Results - Analysis Units not created after setting as current version
   • CMS Application - Current Version - Unexpected Results - Bad deployment path for some deployed packages
   • CMS Application - Current Version - Unexpected Results - Missing entries in the Analysis tab of the Analysis Unit
3. If the problem you are facing does not match any case listed in this page, contact CAST Technical Support with the following Relevant Input.