Server 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. For a server search, this
selection significantly reduces the search running time and limits the traffic between the client
and the server. For a local or server design search, 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 the Checking mode buttons:
- 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.
For a server artifact search, the list of the projects in this field includes all the projects of the selected streams. The projects that contain the design files and the projects that contain the generated files are displayed according to their alphabetical order, without any hierarchical level. Only the projects that you select explicitly are browsed upon the search.
Note: For server searches, if you select All streams in Server scope, then the list of the projects is irrelevant and only the line Search in all projects is available.
- 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
- You can limit the search to one location only. To do so, select the
Location radio button. A list that displays all the local locations becomes
available.
If the location where you want to search for instances does not locally exist, you enter its name (as on the server) in the input field. The search is then run on the instances that are present in this location on the server.
- 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 <=).
- Server scope
- You can select a stream to limit the search scope.
A stream is the equivalent of a work session. It is a repository object that is created in the Rational Team Concert™ server to integrate the work that is done in workspaces.