Wednesday 3 May 2023

Steps to change the field label on the Fusion Applications page.

 1.Navigate to the desired page where you wish to see the new label.


For example, if you wish to change the field label from "Person Number" to "Employee Number" in the Hire an Employee Page. Navigate to Hire an Employee Page as shown above.

2. Click on the desired field to select the same in composer. For example Person Number as shown in the screen under step 1.


3. Ensure that the "panelLabelAndMessage" of the desired field is selected in the Composer and click on the Edit icon in the Toolbar.


4. Click on down arrow icon next to Label field.


5. Choose Select Text Resource...


6. Click on Create.


7. Enter the following values and click on OK button.

Key: <any Code for unique identity of the label>
Display Value: <desired label text>
Description: <brief description>


8. Again follow the above step 7 and 8 to open the text resource window.

9. Enter the Display Value created in the previous step in the Search field and click on search icon.


10. Click on Use link .


11. ACTIVE message appears. Click on OK button.


12. Enter the new label in the Changed Desc field and Click on Apply and OK buttons.



Following string under the Label field in the above screen refers to newly created entry in the resource bundle.

#{adfBundle['oracle.adf.view.page.editor.resource.ComposerOverrideBundle']['RT_S_89']}

 

Note: Prefix for the key is RT_<Layer>_  and in this example it is RT_S_ since it is site layer.


16. Click on Save and Close icons of Oracle Composer on the top right.


17. New label now appears on the page .

Notes :

1. The new string you create will be added to the Override Bundle.

2. You cannot update a seeded resource strings that are bundled with the Fusion Applications.

3. User can update only strings that are created in the same layer.

4. You may Review <Note 1493661.1> For how to translate the custom text added to the Override Bundle.



Steps to change the field label on the Fusion Applications page. (Doc ID 1382016.1)

No comments: