This chapter provides overviews of market in PeopleSoft CRM and industry-specific translate values, and discusses how to:
Set up the label change utility.
Modify industry-specific translate values.
PeopleSoft CRM industry applications are built on the core applications. Market is an attribute of every PeopleTools component that is used to enable the system to make components available to only certain industries. When developers add custom features to the copy of a core component that is going to be used for a specific industry, the component is marked with an industry market setting so that the system knows that both the component and the added custom features are specific to an industry application.
PeopleSoft CRM enables you to implement simple industry-specific layout changes without customizing the system using PeopleTools. These two tools, label change utility and industry-specific translate pages, enable you to change field labels, translate values, and alter the visibility of fields and pages without updating the design of the application.
PeopleSoft CRM identifies a list of component pages that are used in both core and industry applications using the Industry Specific Page Setup page. Set by market, each page setup definition includes information, such as the base page, menu name, item name, page name, record, base record, bar name, component name, panel item name, and component interface name of the specified component page. The system uses this page setup data to facilitate the communication between applications.
Note. Do not modify the information on the Industry Specific Page Setup page unless the corresponding CRM pages are customized and it causes some of the values on this setup page to change.
This section discusses:
The label change utility.
Pages that support the label change utility.
Pages you see from the PeopleSoft online system are defined and maintained using PeopleSoft Application Designer. Depending on how a page is designed, it can contain a combination of fields, subpages, and records. In order for the same page developed for one market to be used in other markets (which is a common practice in PeopleSoft industry solutions, where core component pages are leveraged with industry-specific adjustments), both the page and its component must be cloned for each market where it is used. However, cloning is costly in terms of maintenance because if you change a core component page, you must make sure the same change is reflected in all of its cloned copies. The label change utility enables you to perform minor layout changes to core component pages for application-specific (core or industry alike) implementation without having to clone the associated components and pages. From the components that are modified to support the utility, you can change field labels, hide fields and pages, and switch the mode of pages to display-only. The diagram illustrates how you can use the label change utility to change a field label that appears on the PeopleSoft Internet Architecture page for a different application:
Changing a field label using the label change utility
We discuss this procedure in the documentation for creating page definitions.
See Enterprise PeopleTools 8.45 PeopleBook: PeopleSoft Application Designer
The following table lists the pages in PeopleSoft CRM that support the label change utility:
Note. The label change utility does not work on pages that are not enabled to support the feature.
Component |
Market |
Pages |
RBT_BILL_CMP |
Communications |
RBT_BILLDETAILS_PG, RBT_BILL_PG, and RBT_ITEMDETAILS_PG |
RB_TD_360 |
Global |
RB_TD_AGENT_VIEW |
RBT_ACCOUNT_CMP |
Communications |
RBE_ACCT_SITE_PG, RBT_ACCOUNT_PG, RBT_ACCTCASE_VW_PG, RBT_ACCTPROD_PG, RBT_ACCT_BAL_PG, and RBT_ACCT_USAGE_PG |
RBT_ACCOUNT_SS |
Communications |
RBT_ACCOUNT_SS, RBT_ACCT_BAL_SS, RBT_ACCT_USAGE_SS, RBT_ACCT_VIEW_SS, and RBT_CHNGPAY_PG_SS |
RBT_BILL_DISP_SS |
Communications |
RBT_BILL_DISP_SS |
RBT_BILL_SS |
Communications |
RBT_BILL_ITEM_SS, and RBT_BILL_PG_SS |
RBT_CONFIG_CMP |
Communications |
RBT_CFG_SAVEAS, and RBT_CONFIG_PG |
This section discusses:
Industry-specific translate values.
Delivered fields with industry-specific translate values.
Generally speaking, translate values are field values that appear in drop-down list boxes (note that not all values shown in drop-down list boxes are translate values). Translate values are a relatively small and static set of values (for example, male and female constitute the values available for the Gender field) and are stored in the Translate table, which is a prompt table in the database used to store values for fields that do not need individual prompt tables of their own.
Because translate values are not market-aware, it often causes development overhead whenever a change is made for specific industries. For example, if you want to modify the values in the Gender field from male and female to boy and girl for a specific industry, you must access PeopleSoft Application Designer and update the Translate table and the corresponding component and page.
Using industry-specific translate pages to quickly set up field values for industry use without performing any development tasks in PeopleSoft Application Designer. As you open a page after the setup, depending on the market to which this opened page belongs, the industry-specific translate values (for drop-down list boxes with declared industry-specific translate values) appear.
The following fields have system-delivered, industry-specific translate values:
Field |
Market for Which Specific Values are Created |
CHARGE_FREQ |
Government |
CHARGE_TYPE |
Government |
CRITERIA |
Government, Communications, and Global |
FSI_SERVICE_TYPE |
Communications and Financial Services |
NOTE_CONTACT_TYPE |
Communications, Government, Financial Services, and Global |
RC_NOTE_ORIGIN |
Global |
RF_ASSOC_TYPE |
Global |
Note. While this functionality also enables you to insert additional translate values for fields for information purposes or even for driving processes (that is, perform this action if the user selects option one and perform that action if user selects option two), its main purpose is to provide a quick and easy way to change the label display of translate values on pages for different industries. Therefore, we recommend that you confine the changes you make through this functionality only to the labels of fields that have translate values. Proficient knowledge of PeopleTools is required if you want to drive processes off of translate values based on user selection.
This section discusses how to:
Define templates.
Map templates to setIDs.
Configure field properties.
Configure page properties.
Page Name |
Object Name |
Navigation |
Usage |
Template |
RV_TEMPLATE |
Set Up CRM, Common Definitions, Component Configuration, Label Change Template, Template |
Define templates for industries or applications that use the utility. The system uses templates to identify setup data. |
Template Mapping |
RV_TMPL_APP_MAP |
Set Up CRM, Common Definitions, Component Configuration, Label Change Template Mapping, Template Mapping |
Map templates to setIDs. Each setID can be mapped to only one label change utility template. |
Page Fields |
RV_APP_COMP_PG_FLD |
Set Up CRM, Common Definitions, Component Configuration, Label Change Page Fields, Page Fields |
Configure field properties, such as define fields that need a label change or hide fields. |
Page Properties |
RV_APP_CMP_PG_PROP |
Set Up CRM, Common Definitions, Component Configuration, Label Change Page Fields, Page Properties |
Configure page properties, such as hide pages of the selected component or change page information to display-only. |
Access the Template page.
Template Name |
Displays the name entered when you added the template. For easy identification, use the name of the industry or applications for which the template is created as the template name, such as ENERGY or GOVERNMENT. |
Access the Template Mapping page.
SetID and Template |
Select a setID and match it with a template name. The Template Name drop-down list contains all templates created in the system using the Template page. Note. You can map a setID to only one template; however, you can map multiple setIDs to the same template. |
Access the Page Fields page.
Page Name and Record |
Select the page name and record of the page on which you want to hide fields or change field labels. Values in the Page Name field dictate the values available in the Record field and are specific to the component listed at the header level. |
Page Fields
In this section, configure the system to hide fields or change field labels that are associated with the selected page or page record.
Field Name and Label Text |
Select the name of the field you want to modify; the current label of the selected field appears in the adjacent field. |
New Label ID |
Select a new label for the selected field. The system lists existing labels that are associated with this field; you cannot create new field labels. After selecting a new label ID, the system displays the long and short name of the label. The Hide check box becomes unavailable for entry. |
Long / Short Name |
Select whether to use the long or short name of the new label. |
Hide |
Select to hide the associated field from the page. Do not select a new label for fields that you want hide because when you do, the Hide check box becomes unavailable for entry. To enter a new label for the field, clear the check box. In order for the system to adjust page layout accordingly after fields are hidden from the page, you must enable the adjust layout property in PeopleSoft Application Designer. With the page opened in PeopleSoft Application Designer, right-click on it and select Page Properties from the menu. On the Use page, select the Adjust Layout for Hidden Fields check box and save the change. The page layout updates and fields adjust horizontally after you hide fields from the page. Note. The label change utility cannot be used to hide required fields, unless a default value has been defined for these fields in their record definitions. |
To change labels for fields found inside grids, however, you must first change the page (where the grid resides) using PeopleSoft Application Designer. To do so:
Open the page in PeopleSoft Application Designer.
Right-click on the field (which appears as a grid column heading) whose label you want to change.
Select Page Field Properties from the menu.
On the General page, enter the field name in the Page Field Name field (available on the Record page).
Save the change.
You can now change field labels, regardless of whether they are inside or outside of a grid.
Grid Properties
Use this section to change the grid label available on the selected page.
Field Name and Message Text |
Select the name of the field that is associated with the grid; the current grid label appears in the adjacent field. If the selected page does not have a grid, the system returns no search results. |
Message Set |
Select the message set (message catalog) from which the new grid name is selected. The system displays the message set number in the field. |
Message Nbr (message number) |
Select the number of the text to be used as the new grid name. The text associated with the selected message number appears to the right of this field. |
We discuss this procedure in the documentation for creating page definitions.
See Enterprise PeopleTools 8.45 PeopleBook: PeopleSoft Application Designer
Access the Page Properties page.
Page |
Select the page that you want to hide. |
Hide |
Select to make the associated page invisible. For example, you can hide a page in a component that is used in a PeopleSoft CRM vertical application because this page is irrelevant to the application. |
Display Only |
Select to change the mode of the associated page to display-only, which means you cannot edit information on the page. |
This section discusses how to modify industry-specific translate values.
Page Name |
Object Name |
Navigation |
Usage |
RB_MKT_XLAT |
Set Up CRM, Product Related, Industry, Industry Specific Translates, Industry Specific Translates |
Modify industry-specific translate values. |
Access the Industry Specific Translates page.
Enter the translate value for the field. The number of characters entered in this field cannot exceed the number specified in the Length field. |
|
Enter the date on which you want this value to take effect. The default is today's date. If you want the effective date to predate all rows on your database, enter 01011900 (January 1, 1900). |
|
Select Active. When a value for a field becomes obsolete, select Inactive rather than deleting it. Deactivating a value enables fields in the database that still contain the value to use the correct long and short names. If you delete an obsolete code from the Translate table and you still have records in the database that contain that value, you must change all of those values to active values. |
|
Long Name |
Enter up to 30 characters. Field values are sorted by their long names and appear in the system in ascending order. For example, if the long names entered for the three field values are Activated, Suspended, and Disconnected, they appear in the corresponding drop-down list box in this order: Activated, Disconnected, and Suspended. |
Enter up to 10 characters. |