Advanced Design Search tab
This tab contains particular search patterns, which can be standardly provided or implemented by users through an Eclipse extension point in the RPP API.
General information about the advanced search
The search runs in an asynchronous mode. You can then keep on working while it runs in the background. If you stop an ongoing search, the search results at the time of the interruption are displayed. You cannot start a new search if the previous search is not complete.
It is recommended to limit the search scope. For example, you can run a search on a hierarchy of projects or on a project.
Description of the tab
- Folder
- Select the entity that the search applies to. The entities displayed are the entities that are associated with a search pattern.
- Select a pattern
- Select a pattern that is associated with the selected entity. The patterns displayed are the
standardly provided patterns or user patterns.
- For a Data Element search, the following patterns are standardly provided:
- RPP - List of Data Elements from relational name
Select this pattern for a Data Element search based on the relational name that is indicated in the Data Element -D Lines tab, on R-type lines. You can specify part or all of the searched relational name in the Search string field.
- RPP - List of numeric Data Elements
Select this pattern to find the numeric or non-numeric Data Elements, according to your selection in the field under Select a pattern. By default, the search finds the numeric Data Elements.
- RPP - List of Data Elements by format
Select this pattern for a Data Element search based on the internal format that is indicated in the Data Element Definition tab. You can specify part or all of the searched format in the Search string field.
- RPP - List of Data Elements from relational name
- For a Screen search, the RPP - List of Screens from transaction code pattern is standardly provided. The transaction code is indicated in the Screen Definition tab. You can specify part or all of the searched transaction code in the Search string field.
- For a Data Element search, the following patterns are standardly provided:
- Search in
- You can limit the search scope by selecting one or more projects. This field displays the hierarchy of the design projects as it is indicated in the design compilation path. You can select projects in different ways by clicking one of the Checking mode modes:
- One or more separate projects in the hierarchy. If you select a project, its hierarchy is not taken into account.
- A project with its upper hierarchy.
- A project with its lower hierarchy.
- All the projects of the hierarchy.
- Criteria for the search pattern
- The criteria vary according to the search pattern:
- Search string for a search on a character string, complemented by the
Case sensitive field.
Enter the character string that you want to search for. You can indicate part or all of the string.
You can use the following wildcard characters:- An asterisk matches one or more characters of any value.
- A question mark matches a single character of any value.
- Is or Is not for a boolean search.
- Value and Operator (>, >=, =, < or <=) for a search on an integer.
- Combination of several of the criteria above, or other criteria from the user search pattern. The label, presentation, content, and purpose of this field depend on the search pattern. Then, they reflect the implementation of the extension point in the API.
- Search string for a search on a character string, complemented by the
Case sensitive field.
- Location scope
- By default, the search applies to all the locations of the workspace. However, you can limit the search to only one location. You must open the locations to search for the instances that they contain.
- Diagram scope
- The
diagram represents the hierarchy of the projects that are contained in the location. It is defined
in the design build path wizard. You open this wizard by right-clicking a location in the
Design Explorer view and selecting Properties. The
notions of application domain and level (position in the diagram) are associated with each project.
You can limit the search scope to some Domain and
Level values that exist in the build path.
A domain groups the projects according to application criteria. You can indicate one or more existing domains.
In a tree organization, the level implicitly corresponds to the position of a project in the tree. The root node has a level 0. The child nodes of the root have a level 1. The final leaves of the tree have the highest levels.
In a layer organization, the level is associated with each layer. The layer that groups the projects that are required by all the other projects has a level 0. The layer that groups the projects that are not required by any other project has the highest level.
You can enter a level in the input field and select a position in relation to this level (>, >=, =, <, or <=).