Currently supported entity types:
...
Design Studio Reports
...
Lumira 2.x Documents
This function can be started out of Analyze/Compare. When When the buildup of a Design Studio or Lumira Report is displayed, you can then select the component whose reference in other components should be checked. The function is initiated via the context menu of the respective component, where you can choose if the references should be checked in this specific report or in the whole BO system.
...
As a result, System Scout generates the following list:
As you can see in the illustration above, both
...
Both the direct use, such as in Data Binding or in the Chart Reference and the use in coding are checked. When a component references the source component, you can obtain information about the component type, the technical name of the component, the type of reference, the section of the source code, and the exact line number. If the last two points are not meaningful enough for you, you can call up the entire source code via the “context menu” of the respective component.
...
If you want to deactivate the use in comments within the source code, you can filter and adjust the results by activating the button “Hide all references in comments“. In this area, you can also use the Excel button to initiate an Excel export.
...
From the result view, it is also possible to carry out further Where-Used Analysis. The results are then displayed in a new tab so that previous results are not overwritten.
Advantages about over “Find References” in Design Studio
As already mentioned, it is also possible to perform a similar Where-Used Analysis in Design Studio. In the following we would like to present to you the advantages of the new BO function of the System Scout:
...
Detailed results
...