9Modifying Existing Application Pages
Overview of Existing Page Modification
This topic provides an overview of how you can modify an existing page delivered by Oracle in a Public Sector Compliance and Regulation offering.
You can use the Configure Page feature to modify specific attributes of an existing page delivered by Oracle in a Public Sector Compliance and Regulation offering. You can make these modifications:
Change field labels.
Hide fields.
Examples of page modifications include:
Suppose the existing page has a field label that doesn’t correspond to the terminology used in your agency. Suppose the delivered field label is Flood Zone, but your agency uses Flood Zone Code. You can use the Configure Page option to modify the label.
Suppose the existing page contains a field tracking information your agency does not track, such as the Patio field. You can use the Configure Page feature to hide that field.
Access Page Edit Mode
This topic describes how to access edit mode for existing application pages that you can modify.
Before accessing edit mode, make sure you are signed on with a user who is assigned one of the following job roles:
PSC Business Analyst
PSC System Administrator
Also, make sure the existing page supports configuration. Not all existing pages can be modified. Pages that can be modified display the Configure Page icon in the global header.
Click the Configure Page icon to launch page edit mode.
Use the Page Edit Mode Interface
This topic describes the features and controls you can use to modify an existing application page.
To access the page edit mode, click the Configure Page icon in the global header. For more information see Access Page Edit Mode.
When in page edit mode, the interface consists of these items:
Toolbar
Workspace
Attributes Panel
Using the Toolbar
The toolbar spans the top of the interface below the global header and displays the following information and controls.
Page Element |
Description |
---|---|
Page Name |
Displays the name of the page as it appears in the application, such as Parcel Details. |
Status |
Indicates the status of the current page.
Note: The status is displayed only if you are modifying the page or you have previously modified and published the page.
|
Save |
Saves the current changes to the page to store them, without publishing them. Clicking Save puts the page in draft mode. |
Publish |
Click to create a sandbox and publish the current changes in the sandbox so that the page reflects the changes for runtime access and use.
Note: The Publish button is available only after your have clicked
Save.
|
Cancel |
Click to exit the edit mode without saving or publishing any changes. |
Close |
Click to exit edit mode. The Close button appears when there is no change on the page to be saved or published, such as after you have just published page modifications. |
Manage Sandbox |
Click to access the Oracle Fusion Applications Sandboxes page where you can view the status of your sandbox and refresh your sandbox if needed. When modifying an existing page, the sandbox exists only during the publishing process request. While you modify a page and save any changes, the system tracks your changes in an internal metadata storage object. When you click Publish, the changes are added to the sandbox, and the sandbox is published.
Note: The Manage Sandbox button appears only if the sandbox associated with your form layout becomes out of sync during a publish request, requiring a refresh.
Identify the sandbox for your page modifications according to this naming scheme: PSCSC_<page name>__sb_<number of publish requests> For example: PSCSC_ParcelDetailsInformation__sb_2 For more information on sandboxes, see Working with Sandboxes. |
Using the Workspace
The workspace displays the content of the page that you can modify. Select a field on the page to display its attributes in the Attributes panel.
Using the Attributes Panel
The Attributes Panel contains the attributes you can modify for a selected page element, such as a field.
You can view and set these field attributes:
Page Element |
Description |
---|---|
Label |
Use to modify the existing label for the page.
Note: The length limit for modified field labels on existing pages is 100 characters.
Note: Do not change the meaning of a field label in an attempt to use it to reflect a value different from its intended purpose. For example, don’t change “Flood Zone” to “School Zone.” Each field may have logic behind it, dependencies in workflow, dependencies related to fees, and so on. The ability to change field labels is intended to support minor changes in terminology.
|
Hidden |
Use to hide a field on the existing page. When the switch is on, the associated field is hidden.
Note: Fields that are set to be required can’t be hidden.
|
Business Object |
The name of the database view object associated with the page. |
Field Name |
The name of the field as it appears in the REST payload, which you can view using a describe command for the associated REST resource. |
The Business Object and Field Name values are read-only values provided for informational purposes to help implementation teams assess any areas affected by a page modification, which affects:
Sub pages using the same view object field
Reporting
Auditing
Modify Existing Pages
This topic describes the steps in the procedure for modifying an existing page delivered in an Oracle Public Sector Compliance and Regulation offering.
Change Labels
To change a a label:
Navigate to the page you want to modify.
Click the Configure Page button in the global header.
In the workspace, select the field you want to modify.
In the Field Attributes panel, enter your modified label in the Label field.
Click Save.
Click Publish.
Hide Fields
To hide a field:
Navigate to the page you want to modify.
Click the Configure Page button in the global header.
In the workspace, select the field you want to hide.
In the Field Attributes panel, turn on the Hidden switch.
Click Save.
Click Publish.
After you have hidden a field, the layout in page edit mode displays the field within a box with a hidden icon next to the hidden field to indicate its hidden runtime status.
Managing Existing Page Modifications
This topic describes concepts necessary to keep in mind when migrating existing page modifications between environments, such as from the test environment to the production environment.
Similar to migrating transaction types from one environment to another, the data related to page modifications gets migrated in multiple parts using these features:
Functional Setup Manager’s export and import feature.
Configuration Set Migration feature, which you access using the Functional Setup Manager step “Manage Existing Page Modifications” in the System Administration functional area.