...
| Info |
|---|
If you still use both the Universal Analyzer and the Universal Importer in "combined mode" (rather than using just the Universal Importer as explained above) you may find that the CAST Engineering Dashboard will report an incorrect number of Total Checks (see the Investigation - Quality Model Drilldown part of the CAST Engineering Dashboard - CED). . The number of Total Checks for a specific measure will be higher than the actual number of objects that really exist. This is because when you use the Universal Analyzer and the Universal Importer in "combined mode", objects are attached to two sets of projects at the same time (Universal Analyzer and the Universal Importer) and are therefore counted more than once. CAST has provided a workaround to resolved this issue. More information can be found in Advanced - Resolving erroneous number of Total Checks reported by the CAST Engineering Dashboard. |
...
To define the location of the source code files in your .UAX files, you can use either a relative path or an absolute path:
Relative | <CAST_CodeExpandable sourcePath="PageEvent_ACL_COMPONENT2.Activate.src.PSoft_PageEvent.ACL_COMPONENT2..Activate"/> |
Absolute | <CAST_CodeExpandable sourcePath="P:\PageEvent\PageEvent_ACL_COMPONENT2.Activate.src.PSoft_PageEvent.ACL_COMPONENT2..Activate"/> |
| Info |
|---|
CAST strongly recommends that you use relative paths to avoid any potential problems linked to the location of the source code |
...
This path will then be used to determine the location of source code files specified in the .UAX files. In the above code examples, you would need to ensure the Root Path as P:\PageEvent\