ICA FECHA_M HORA_M PARAMETRO VALOR_T UNIDAD

You should create your own query trees based on your organization’s needs and on any

customizations you’ve made. Remember that the sample trees we provide may be replaced when you upgrade to a subsequent PeopleSoft release, so if you modify the samples rather than create your own trees, you may lose your customizations.

Every record component that you want users to be able to query must be in a query tree.

However, they don’t all have to be in the same query tree. One strategy is to use the sample query trees to provide access to the standard PeopleSoft record definitions, but create separate query trees for record definitions that you add in the course of customizing the system. This way, you take advantage of the sample trees but avoid overwriting your changes during future upgrades. How you organize the contents of your query tree depends on the needs of your organization and your users. For example, you might want to create small trees that are not intimidating to non- technical or casual users. The sample query trees provided in your PeopleSoft application are divided by functions, but to simplify the trees, you may want to create separate trees that contain subcategories of each function. For example, you could create separate trees for U.S., Canadian, and international record components in order to grant users in each region security access to only those record components they should use.

Note. You should consider adding record components to your query trees in a hierarchy that matches the parent/child relationship of records in your database. Though you don’t have to organize records this way—Application Designer actually controls the parent/child hierarchy in your database—you’ll probably find it helpful to keep your query trees consistent with your database structure.

It’s a good idea when creating your tree to have an access group that includes all components of the tree makes. This makes it easier to give users access to all tables—you only need to add one row on the Access Groups tab in Query Security.

JA N U A R Y 2 0 0 1 PE O P L ETO O L S 8 . 1 2 PE O P L ESO F T QU E R Y PE O P L EBO O K

PE O P L ESO F T PR O P R I E T A R Y A N D CO N F I D E N T I A L SE T T I N G U P QU E R Y SE C U R I T Y 2 - 3

Defining Your Query Tree

Before you can insert nodes for access groups and record components, you must first define a number of important characteristics for your tree.

To define a query tree:

1. In Tree Manager, select File, New to open to the New Tree Definition Properties dialog box, where you specify general information about the tree.

New Tree Definition Properties dialog box – Structure tab

2. Enter a Structure ID for the query tree.

The Structure ID for a query tree must always be ACCESS_GROUP. You can either type ACCESS_GROUP in the text box or press F4 and select it from the prompt list.

When you move the cursor out of this field, Use of Levels defaults to Not Used because query trees don’t use levels.

3. Enter a name for the tree.

For the tree name, we recommend that you start the name with QRY_ so that you can easily identify the tree as a custom query tree. (The standard query trees we deliver with the system start with QUERY_.)

4. Enter an Effective Date for the tree.

The status defaults to Active. Query trees are available immediately if the effective date is active; you don’t need to run an SQR utility like you do for organizational security trees.

2 - 4 SE T T I N G U P QU E R Y SE C U R I T Y PE O P L ESO F T PR O P R I E T A R Y A N D CO N F I D E N T I A L

This description will appear along with the name and effective date in the list box whenever you select from a list of trees.

Note. You can change a tree description at any time by selecting File, Definition from within Tree Manager.

6. You can also specify a Category, if desired.

Note. Currently, Detail Values are not necessary for query trees.

7. Finish your new Tree definition by completing the Properties, Levels, and Access Performance Methods dialogs.

For more information about completing these dialogs and creating new Trees, see Introduction to Tree Manager.

8. Once you’ve completed your tree definition, click OK.

Tree Manager displays the name and effective date of the query tree you are creating. Together, these fields form a key that identifies each unique version of a tree.