Oracle CRM On Demand -sovelluksen hallinta > Sovelluksen mukautus > Tietuetyyppien Sovelluksen räätälöinti -sivu > Customizing Static Page Layouts
Customizing Static Page Layouts
The right look and feel of an application is important for user adoption, and one way to achieve the right look and feel is by customizing page layouts. As part of the customizing process, you can:
There are two methods of customizing page layouts. You can define static page layouts defining specific fields by role, or dynamic page layouts that change based on the type of record being created. Dynamic page layouts can also be assigned by role. The number of characters that you can use in page layout names is limited. For more information, see About Custom Layout Limits.
You can create new layouts for each record type and then assign a page layout for each record type to a user role. When a user with that role signs in, the user then sees any customized layout specific to each record type. For example, you can create two page layouts for opportunities: one simplified layout for service representatives showing only the most important fields and another layout for field sales representatives showing many more fields, and assign the different layouts to the different roles. Users who are not assigned the service representative or field sales representative roles continue to see the default layout for the Opportunity page. As another example, you can create two page layouts for contacts, such that the Account field is required when service representatives add new contacts, but not required when service managers add new contacts.
If you do not assign a custom page layout for a record type for a given role, the default page is used for that record type.
When customizing a page layout, you can determine:
- Which fields appear on the page
For custom fields to appear, you must add them to the page layouts. After that, users with roles to which the custom page layout is assigned will see the fields on the Edit page, Detail page, and Create form (in the Action bar).
- Where fields appear on the page
- Which fields are required
- Which fields are read-only
- Which fields must always appear on the layout, even if users personalize their field layout
- How many page sections appear and with which headings.
- Which linked record types are displayed in the related information sections on the Detail page.
For example, you might want linked contacts to appear on the Accounts Detail page.
- Which layout is used for each related information section.
- Which layout is used in the new record page when users create records from a list of related records of a given record type, provided that the related record type supports custom layouts for new record pages.
There are some exceptions for this feature. For example:
- Although you can select a layout for the new record pages for the Open Appointments and Open Tasks related information sections, these layouts will not be used when users create new appointments or new tasks from an Open Activities related information section.
- You cannot select a layout for the new record page for the Log a Call button on a list of completed activities.
- Users cannot create new records from some related information sections, such as the Audit Trail section. Therefore, you cannot select a layout for creating new records from those related information sections.
NOTE: You can also assign a layout for the new record page for each record type in the Role Management Wizard. For information about how Oracle CRM On Demand determines which layout is used in the new record page when users create records from a list of related records, and for details of how to create such layouts, see Customizing Page Layouts for Creating New Records.
You can copy standard layouts, but you cannot edit or delete them. You can delete custom layouts, unless it is already assigned to a role or a dynamic layout.
About Personalizing Page Layouts
Käyttäjät voivat mukauttaa liittyvien tietojen osien asettelua tietuetyypin tietosivulla, jos käyttäjäroolille on otettu käyttöön Mukauta tietosivu - Liittyvät tiedot -oikeus.
Käyttäjät voivat mukauttaa kenttäasettelua tietuetyypin tietosivulla, kun käyttäjärooli on määritetty seuraavasti:
- Roolille on otettu käyttöön Mukauta tietosivu - Kentät -oikeus.
- Rooliin on liitetty mukautettu sivuasettelu tietuetyyppiä varten.
For more information about personalized page layouts, see the following topics:
Considerations for Fields in Page Layouts
When you design your page layouts, consider the following:
- Some record fields are important to report and forecast calculations. To enforce the consistent use of these fields, they are flagged as required. You cannot change the required flag on these fields when customizing a page layout. You also cannot remove them from a page layout.
- Removing fields from a page layout can have important implications for how the records are used. For example, if you remove the Status and Publish fields on solutions records, employees with that page layout cannot approve solutions or make them available to others.
- Addresses are grouped together so that the field and their labels reflect the naming convention for each country. Therefore, for some record types, you cannot separate out individual address lines. Instead, you must select the field that includes the group of address lines (a single address option). This option replaces the individual fields that you could select in releases earlier than Release 20, such as Street, City, Zip Code. For example, for leads, the field Billing appears on the Field Setup and Field Layout steps of the Page Layout assistant. The Billing field includes all the Billing Address fields.
- You can move standard and custom note fields in the Long Text Field(s) list on your page layout to other areas in your page layout.
- You can move the following fields to and from the Long Text field(s) list, and to and from other areas, in your page layout:
Record
|
Field Name
|
Account Address
|
Description
|
Address
|
Description
|
Address
|
Comments
|
Sales Assessment Template
|
Description
|
Activity
|
Next Call
|
Application
|
Existing Partnerships
|
Application
|
Expected Partnership Benefits
|
Application
|
Indexed Long Text
|
Asset
|
Description
|
Book
|
Description
|
Dealer Address
|
Description
|
Event
|
Description
|
Event
|
Session Details
|
Event
|
Test Objective
|
Fund
|
Description
|
Fund Request
|
Description
|
Household
|
Description
|
Invitee
|
Comments
|
Invitee
|
Session Detail
|
Messaging Plan Item
|
Synopsis
|
Messaging Plan Item
|
Speaker Notes
|
Messaging Plan Item
|
Audience
|
Messaging Plan
|
Audience
|
Messaging Plan
|
Comment
|
Messaging Plan
|
Description
|
Messaging Plan Item Relations
|
Audience
|
Messaging Plan Item Relations
|
Synopsis
|
Objective
|
Description
|
Objective
|
Target Audience
|
Account Call
|
Next Call
|
Account Call
|
Description
|
Appointment
|
Next Call
|
Appointment
|
Description
|
Attendee Call
|
Next Call
|
Attendee Call
|
Description
|
Contact Address
|
Acceptable Schedules
|
Contact Address
|
Description
|
Contact Call
|
Description
|
Contact Call
|
Next Call
|
Smart Call
|
Description
|
Smart Call
|
Next Call
|
Task
|
Description
|
Task
|
Next Call
|
Partner
|
Description
|
Partner Address
|
Description
|
Partner Program
|
Description
|
Product
|
Description
|
Product Indication
|
Description
|
Revenue
|
Description
|
Account Revenue
|
Description
|
Contact Revenue
|
Description
|
Opportunity Product Revenue
|
Description
|
Sample Disclaimer
|
Disclaimer Text
|
Sample Lot
|
Description
|
Sample Transaction
|
Comments
|
Service Request
|
Subject
|
Transaction Item
|
Description
|
Vehicle
|
Description
|
Vehicle Service History
|
Description
|
Page Layouts and Lists
Sivun asettelujen ja roolien käyttöoikeuksien avulla voit rajoittaa kenttiä, joita käyttäjät voivat hakea, tuoda näkyviin luetteloihin ja viedä. Kun käyttäjä luo ja muokkaa tietueluetteloita tai käyttää tarkennettua hakua tietueiden etsimiseen, käyttäjän roolille määritetyt käyttöoikeudet ja sivun asettelut määrittävät, mitä kenttiä käyttäjä voi hakea ja tuoda näkyviin.
Jos käyttäjäroolille on myönnetty Kaikki hakujen ja luetteloiden kentät -käyttöoikeus, käyttäjä voi hakea kaikkia hakukenttiä, jotka näkyvät kyseisen tietuetyypin käyttäjäroolille määritetyssä haun asettelussa. Lisäksi kun luetteloa luodaan tai muutetaan, käyttäjä voi valita minkä tahansa kentän näkymään hakutuloksissa tietueluettelon sarakkeena.
HUOMAUTUS: Suosittelemme, että yrityksen järjestelmänvalvoja ei ota suurimmalle osalle käyttäjärooleja käyttöön Kaikki kentät -vaihtoehtoa haku- ja luettelo-oikeuksissa. Kun oikeudet eivät ole käytössä, kentät, jotka eivät ole käytössä yrityksessä, eivät näy haku- ja luettelosivuilla. Tämä vähentää sekaannuksia ja käyttäjät löytävät helpommin heitä kiinnostavat kentät.
Jos käyttäjäroolin haku- ja luettelo-oikeuksissa on valittuna Kaikki kentät -vaihtoehto, käyttäjä voi hakea kenttää vain, jos se täyttää molemmat seuraavista ehdoista:
- Kenttä on käytettävissä oleva hakukenttä tietuetyypin käyttäjäroolille määritetyssä hakuasettelussa.
- Kenttä näkyy tietuetyypin käyttäjäroolille määritetyn tietosivun asettelussa. Jos roolille on määritetty dynaamisia sivun asetteluja, kentän on oltava näkyvissä ainakin yhdessä dynaamisista sivun asetteluista.
Lisäksi, kun luetteloa luodaan tai muutetaan, käyttäjä voi valita hakutuloksissa tietueluettelon sarakkeena näytettävän kentän vain, jos kenttä näkyy ainakin yhdessä tietosivun asetteluista, mukaan luettuna tietuetyypin käyttäjäroolille määritetyt dynaamiset sivun asettelut. Tämä rajoitus vaikuttaa myös siihen, mitä käyttäjä voi viedä luettelomuodossa. Jos käyttäjäroolille on myönnetty Luettelo - näkyvien kenttien vienti -käyttöoikeus mutta ei Luettelo - kaikkien kenttien vienti -käyttöoikeutta, käyttäjä voi viedä vain luettelossa näkyvät kentät. Käyttäjä ei voi viedä kaikkia tietueiden kenttiä luettelossa.
HUOMAUTUS: Jos käyttäjä tekee tarkennetun haun päätason tietueen liittyvien tietueiden luettelossa olevan Lisäasetukset-linkin avulla, hakukenttiin ja hakutuloksissa liittyviin kenttiin saattaa liittyä lisärajoituksia. Lisätietoja on kohdassa Tietoja liittyviin tietueisiin kohdistuvasta tarkennetusta hausta.
Before you begin. To perform this procedure, your role must include the Customize Application privilege.
To create a page layout
- In the upper right corner of any page, click the Admin global link.
- In the Application Customization section, click the Application Customization link.
- In the Record Type Setup section, click the link for the required record type.
- In the Page Layout section, click the required Page Layout link.
- In the Page Layout list, do one of the following:
- In Step 1 Layout Name, enter a name for the layout and a description (optional).
- In Step 2 Field Setup, select the field characteristics, as follows:
- Select the Required check box for any fields that you want to make required.
HUOMAUTUS: Käyttäjien ei ole pakko valita Valintaruutu-tyyppistä kenttää, joka on merkitty pakolliseksi. Jos haluat, että valintaruudun kentän arvo on Tosi (toisin sanoen haluat, että valintaruutu valitaan), käytä valintaruudun kentässä tarkistussääntöjä. Lisätietoja on kohdassa Tietoja kenttien hallinnasta.
- Select the Read Only check box for any fields that you want to make read only.
- Select the Always On Layout check box for any fields that you do not want users to be able to remove from their layout.
NOTE: When you create a new page layout, the Always On Layout check box is selected by default and is read-only for any field that is configured as a required field, unless a default value is configured for the field. If a default value is configured for a required field, then the Always On Layout check box is selected, but you can deselect it. It is also recommended that you select the Always On Layout check box for any fields that are configured as conditionally required. And, if you use or plan to use a dynamic page layout for the record type, then it is recommended that you select the Always On Layout check box for the picklist field that drives the dynamic layout.
For information about the Conditionally Required check box, see About Conditionally Required Fields.
- In Step 3 Field Layout, you can:
- Move fields from the record type Available Fields list to various sections of the record type Arrange Page Layout area.
Make sure you move the custom fields and the industry-specific fields you want to add to the forms. Also, if any of the fields for which you selected the Always On Layout check box in Step 2 are not already on the layout, then add them to the layout.
CAUTION: Unless a default value is configured for a required field, the required field must be on the page layout. Otherwise, anyone with that layout will be unable to create or edit a record of that type. Jos pakolliselle kentälle on määritetty oletusarvo, pakollinen kenttä voi näkyä sivuasettelussa. Vastaavasti on määritettävä, että ehdollisesti pakolliset kentät ovat asiaankuuluvissa sivuasetteluissa. Muussa tapauksessa käyttäjät eivät voi syöttää arvoa näihin kenttiin, kun ne muuttuvat pakollisiksi.
- Remove the Description field from your page layout or move the Description field to another area on your page layout.
- Rearrange the information.
NOTE: These changes affect all the forms for that record type when a user with an appropriate role views the pages. However, if you update the field layout after a user personalizes the field layout for the record type, then the changes do not apply to the personalized layout. Some fields include a group of fields or multi-line fields. Avoid moving those fields around because the information itself might overlap other fields in the final layout. For this reason, the application does not allow you to move multi-line text fields, such as Description. The application uses an address template that provides the fields specific to each country. For more information, see About Countries and Address Mapping.
- In Step 4 Related Information, you can:
- Add sections or remove sections that appear on the Detail pages. The sections are the areas where users can link records to the current record.
For example, if you do not want employees to be able to link products to opportunities, make sure the Products section does not appear in the Displayed or Available Information box.
NOTE: Users can change these default settings through the Edit Layout link on the Detail page for their application. After users have edited their personal layouts, they do not see new changes to the related information made by the company administrator until they edit their layout another time.
- Change the order of the sections on the Detail pages.
NOTE: These changes affect the Detail pages for that record type when a user with an appropriate custom role views the pages.
- (Optional) In Step 5 Related Information Layout, you can:
- In the Related Information Layout field, select the appropriate related information layout for each of the related information sections on the page.
NOTE: The default layout for each related information section is the standard one. If you have created custom related information layouts already, you can select them from the list. For more information about creating related information layouts, see Customizing Related Item Layouts.
- In the New Record Layout Name field, select a layout to be used in the new record page when users create records from a list of related records, for each of the related record types that support custom layouts for new record pages.
Administrators can create custom layouts for new record pages. If any custom layouts for new record pages have been created for the related record type, then you can select a custom layout from the list.
- Click Finish.
- Assign the page layout for this record type to user roles as required, see Adding Roles.
|