Setting Up Text for Advisor Tools

This chapter provides an overview of advisor tools and discusses how to:

• Define content for the Language Checker tool.

• Define content for the Development Tips and Results Writer tools.

• Link development tips to competencies and sub-competencies.

• Import third-party content.

• Build Verity search indexes.

Understanding Advisor Tools

This section lists common elements and discusses:

• Template setup for using results writer and development tips.

• Search collections for results writer and development tips.

Common Elements Used in this Chapter

Template Setup for Using Results Writer and Development Tips

You can define text for these tools at either the competency or sub-competency level. You then set up the document template to access this text. The template rules control the level of text, by competency or sub-competency, that the system searches to find text suggestions for a section or item.

You must set the template rules to correspond to the level at which the text is defined. For example, if you define text or bring in text from a third party at the sub-competency level, then you must set the Results Writer and Development Tips template switches to Sub-Competency for the tool to locate text.

The combination of the level at which text is defined, the level at which the tool is enabled on the document template, and the ratings that the user enters, determine the suggested results that appear when the user clicks the Writing Tools link on an evaluation.

This table shows the results for the possible combinations of link level, text level, and ratings entered.

See Also

Creating Document Templates

Search Collections for Results Writer and Development Tips

Any time you make an addition or deletion to Results Writer or Development Tips items, you need to rebuild the search index to reflect the new state of the collection of items. The Writing Tools use this search index to locate text when either the Results Writer or Development Tips tool is enabled for a section or item.

See Also

Working with Writing Tools

Defining Content for the Language Checker Tool

To define content for the Language Checker tool, use the Language Checker Suggestions (EP_CHK_SUG_TBL) and Language Checker Words (EP_CHK_WRD_TBL) components.

This section discusses how to:

• Define objectionable words and phrases.

• Define suggested wording.

See Also

Working with Writing Tools

Pages Used to Define Language Checker Content

Defining Objectionable Words and Phrases

Access the Language Checker Word page (Set Up HRMS, Product Related, ePerformance, Advisor Tools, Language Checker Words, Language Checker Word).

Words and Phrases	Enter the word or phrase that is deemed inappropriate in a performance document. Case is not important (the Language Checker tool is not case-sensitive). When invoked, the Language Checker tool follows these search rules: If you enter a single word here, the Language Checker tool searches for whole words that match. If you enter multiple words, the Language Checker tool looks for phrases with an exact match.
Content Supplier	Select the source of the content. The default value is Customer Defined.
Suggestion ID	Enter the ID for the suggested words or phrases that managers can use instead of the words and phrases entered on this page. You define language suggestions and IDs on the Language Checker Suggestion page.
Language Suggestions	Displays the language suggestions that are associated with the suggestion ID.

Defining Suggested Wording

Access the Language Checker Suggestion page (Set Up HRMS, Product Related, ePerformance, Advisor Tools, Language Checker Suggestions, Language Checker Suggestion).

Content Supplier	Select the source of the content: Customer Defined or the third-party supplier's name.
Language Suggestions	Enter language suggestions for words and phrases, or list the reasons why the manager should not use certain words and phrases.
Proper Usage	Enter examples of the proper usage of words or phrases.
Incorrect Usage	Enter examples of the incorrect usage of words or phrases.

Defining Content for the Development Tips and Results Writer Tools

To define content for the Development Tips and Results Writer Tools, use the Define Development Tips (EP_DEV_TIP_TBL_EP) and Results Writer (EP_COMP_WRT_TBL) components.

This section lists prerequisites and discusses how to:

• Define development tips.

• Define Results Writer text for competencies.

See Also

Working with Writing Tools

Setting Up the Content Catalog

Prerequisites

Text entries for the Results Writer and Development Tips tools are related to competencies and their proficiency level, and sub-competencies and their proficiency level. You must set up this information before defining text for these tools.

• Rating models.

• Competencies and sub-competencies.

• Competency and sub-competency proficiency levels.

If multiple business units and setIDs are implemented in PeopleSoft HR, the information that you use and create is determined by how the business unit and setID functionality is set up for the user ID.

See Setting Up Organization Foundation Tables.

See Setting Up the Content Catalog.

Pages Used to Define Content for the Development Tips and Results Writer Tools

Defining Development Tips

Access the Define Development Tip page (Set Up HRMS, Product Related, ePerformance, Advisor Tools, Define Development Tips, Define Development Tip).

Content Supplier

Select the content supplier for the development tip. Select a third-party supplier from the available options, or select Customer Defined to enter development tips.

Defining Results Writer Text for Competencies

Access the Results Writer - Competency page (Set Up HRMS, Product Related, ePerformance, Advisor Tools, Results Writer, Results Writer - Competency).

Review ratings describe an employee's level of proficiency for a competency. For each review rating that is associated with the competency, you can define the suggested text that managers can use when they invoke the Results Writer tool. You can create one or more text entries for each rating.

Note. When you access the Sub-Competencies page, the first sub-competency that is associated with the competency appears. You must page forward or use the View All link to access other sub-competencies.

Linking Development Tips to Competencies and Sub-Competencies

To link development tips to competencies and sub-competencies, use the Link Development Tips (EP_COMP_DEV_TBL) component.

This section discusses how to link development tips to competencies and sub-competencies.

Pages Used to Link Development Tips to Competencies and Sub-Competencies

Linking Development Tips to Competencies

Access the Link Development Tips - Competency page (Set Up HRMS, Product Related, ePerformance, Advisor Tools, Link Development Tips, Competency).

Review ratings describe an employee's level of proficiency for a competency. For each review rating that is associated with the competency, you can define the suggested text that managers can use when they invoke the Development Tips tool. You can create one or more text entries for each rating.

Importing Third-Party Content

This section provides an overview of importing third-party content for the Language Checker tool and lists the pages used to import data.

See Also

PeopleSoft 9.1 Components PeopleBook

PeopleTools 8.52: Integration Broker PeopleBook

Understanding Third-Party Data Import

PeopleSoft has established partnerships with several third-party providers that supply content for defining competencies and proficiency levels. Some content providers also provide content for the Development Tips and Language Checker tools that are delivered with ePerformance. You can import third-party data into the system, enter free-form content, or use a combination of both.

ePerformance uses PeopleTools Integration Broker to receive vendor-supplied data in the form of comma-delimited flat files. The flat files are imported into ePerformance using the Inbound File Publish Application Engine (EOP_PUBLISHF) process. You do not need to develop an interface to load third-party content into ePerformance.

Preparing to Import Data

To prepare to import data, activate inbound file rules for the file you are importing on the Inbound File page. You also use this page to associate messages with files and optionally change the default directory for incoming files from c:\temp to a directory that you choose.

This table lists the identifiers for the inbound file rules.

Importing Data

To import data:

1. Make sure that each channel is running (not paused).

   Channels are delivered paused.

   Follow the procedure for configuring a message channel.

   See PeopleTools 8.52: Integration Broker PeopleBook

2. Ensure that each message, its PeopleCode subscription, and its Integration Broker transaction are active.

3. Open PeopleSoft Process Scheduler.

   The application server must have publish and subscribe running.

   See PeopleTools 8.52: System and Server Administration PeopleBook

4. For each file identifier, initiate the publish process.

   The publish process converts the flat file to a message.

   1. Select Enterprise Components, Integration Definitions, Initiate Processes, Inbound File Publish.

   2. Create a run control and initiate the process.

      Follow the procedure for using the inbound file pages for processing files.

      See PeopleSoft 9.1 Components PeopleBook

5. Confirm that the process is complete through the Process Monitor page.

6. Confirm that the subscription occurred.

   1. Access the Monitor Message component by selecting PeopleTools, Integration Broker, Monitor, Monitor Message.

   2. Select the local node in the Publish Node field and Subscription Contract in the Queue Type field.

      Look for a subscription contract for the message just processed.

Pages Used to Import Data

Building Verity Search Indexes

This section provides an overview of search indexes and lists the pages used to build Verity search indexes.

Search Indexes

When you either add or remove Results Writer or Development Tips text items, you must rebuild the Verity search index to accurately reference these items in the database. If you do not rebuild the index, the system user will not see the added content when using the writing tools.

These are the search indexes to rebuild for each item that you change:

These Search Index definitions are predefined in the system. You must manually rebuild them any time you make a change to Results Writer or Development Tips content, including when you load content from a third-party provider. The search indexes are built using PeopleTools pages.

Note. If you don't use languages other than English, you do not need to build the indexes whose object name ends in _LANG

See Also

Working with Writing Tools

PeopleTools 8.52: System and Server Administration PeopleBook

Pages Used to Build Search Indexes