1.To edit a system search object, users load the list of existing items by calling the System Search view within the Visual Designer mode of PackDesigner.
2.To edit the root element of a system search task, users left-click that root object, and access its details, which are displayed within the edit pane at the right-hand side of the application screen
3.To edit a child element of a system search task, users left-click the specific child of the root task object. There may be one or more child objects per root item, since each search type required different key criteria to operate.
System Search - Root Object Properties
When a system search root object is selected for edition, users may change the property which will be used to store the search result at run time.
Please enter the name of an existing, public property of the current packaging project.
System Search - Criteria Object Properties
File
If a search task is defined for a specific file, the root item should always consist two child items: One file and one path, registry, component, or ini item. The file item defines the criteria required to look up the matching file itself, whilst the other item defines where to find the path to the file users want to search for.
Please refer to the Add a custom search topic (steps 2a and 2b) for further details about the settings available for target file property definitions.
Path
Please refer to the Add a custom search topic (step 3: Folder location options) for further details about the settings available for folder related system search criteria.
Registry
Please refer to the Add a custom search topic (step 3: Registry location options) for further details about the settings available for registry related system search criteria.
Component
Please refer to the Add a custom search topic (step 3: Component location options) for further details about the settings available for component related system search criteria.
INI
Please refer to the Add a custom search topic (step 3: INI location options) for further details about the settings available for INI related system search criteria.
|
Be aware: Each system search tasks needs at least one child item to define what exactly the search task has to execute. If there are too many or too few of these child objects defined per system search root task, there may be unforeseen search results during package run-time. |
To Add a Child Element to a System Search Task Root Object
Once a system search root element has been created by either adding a predefined or a custom system search, users may add further search term child elements of not already added types to that root element.
1.To do so, users have to right-click the root item of the affected search task, and select Add from the context menu.
2.The New System Search wizard is displayed, with the property already present as read-only information derived from the root system search object.
With a click on the Next button, users get the overview of system search types.
3.If the root item has already been extended with a child item of a specific search type, that type is no longer available for an additional selection. This means that each parent search item can have only one child per search type. To proceed, users have to select one of the available search types, and click Next.
4.Finish the wizard by entering the requested search criteria as described within the help topic Add a custom system search.
|
WARNING RayPack actually allows to define system search tasks with more or less criteria definition items than recommended. It may be necessary to extend the standard system search operations with more complex structures in order to fulfill more complex searches. However, to provide high-level package quality, any non-standard system search definition needs to be tested thoroughly before it is used in a productive software package. |
