Understanding Industry-Specific Setup
Industry-specific setup consists of three setup steps:
Core functionality required for the industry.
Requirements common to all industry-specific installations.
This topic discusses the setup requirements for industry-specific functionality. The setup requirements for core functionality are discussed in the appropriate topics.
This sections discusses:
Markets.
Industry-specific page setup.
Industry-specific translate values.
Display templates.
Markets
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.
Industry-Specific Page Setup
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, page item name, and component interface name of the specified component page. The system uses this page setup data to facilitate the communication between applications.
Industry-Specific Translate Values
Using industry-specific translate pages, you can 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.
Display Templates
The introduction of display templates eliminates the need for component cloning. The idea is to make the look and feel of components entirely configurable using templates, so that they can potentially be used in any scenario. In the display template framework, only one version of a component exists. This component is a consolidation of all its variants and it consists of all the parts and pieces that can be manipulated. Each implementation that wants to present the component in its specific way creates a display template for the component. Through the display template, you can control the visibility of component pages and fields, alter section and field labels, apply field-level security and setup options that are available to the component.