Introduction
This 20-minute tutorial introduces you to the Design Time Formatting (DTF) options in web forms. You will use the style selector and review the differences in runtime on applying the available style options. You will see that Groovy Rule takes precedence over all other Rules. The sections build on each other and should be completed sequentially.
Background
Design Time Formatting (DTF) enables you to combine form design Validation Rules on the web to provide robust formatting capabilities in data forms. You can also combine these with end user formatting capabilities for forms rendered in Oracle Smart View. Both data and metadata can be formatted.
Applies to: Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Tax Reporting
With Design Time Format Rules, forms will now:
- Support most of the formatting capabilities from Smart View client such as borders, colors, font sizes, fonts, numeric formats, and so on
- Allow Rules to be created for pure formatting purposes in addition to today’s Data Validation Rules
- Allow Format Rules to be applied to header and metadata cells in addition to data cells
Prerequisites
Cloud EPM Hands-on Tutorials may require you to import a snapshot into your Cloud EPM Enterprise Service instance. Before you can import a tutorial snapshot, you must request another Cloud EPM Enterprise Service instance or remove your current application and business process. The tutorial snapshot will not import over your existing application or business process, nor will it automatically replace or restore the application or business process you are currently working with.
Before starting this tutorial, you must:
- Have Service Administrator access to a Cloud EPM Enterprise Service instance.
- Import this snapshot into your instance. The examples provided in this tutorial use the snapshot.
Note:
If you run into migration errors importing the snapshot, re-run the migration excluding the HSS-Shared Services component, as well as the Security and User Preferences artifacts in the Core component. For more information on uploading and importing snapshots, refer to the Administering Migration for Oracle Enterprise Performance Management Cloud documentation.Assigning values to User Variables
User Variables were added when the business process was created. User variables act as filters in forms, enabling planners to focus only on certain members. In this section, you set values for user variables.
- On the home page, click
(Navigator), and under Tools, click User Preferences.
- Under Preferences, click User Variables.
- Click
(Member Selector) to select each variable's value.
Tip:
You can also type and enter the values under Member for each Dimension. - Verify your selections and click Save.
- At the information message, click OK.
Applying styles to forms using the Style Selector
After you define Format Rules for forms at design time, you can apply the Format Rules to forms at runtime using styles. Styles control how Format Rules are displayed for grids, row headings, column headings, and cells. The three style options are:
-
Cell Style: Applies Web form styles (such as read-only cells, locked cells, supporting detail), Smart View cell styles defined in Smart View 24.200, Data Validation Rules, and Groovy Rules to the form. No custom (Format only) styles are applied.
-
Custom Style: Applies Format only Rules that were defined in the Rule Builder at design-time, and any Excel custom formatting that was added by administrators and users in Smart View. No cell styles are applied.
-
Custom and Cell Style: Applies all cell styles and custom styles to the form. This is the default style option.
-
On the home page, click Data.
- In Data Entry, under Library, expand Workshop.
In this example, the forms displayed are part of the application provided in the Prerequisites section of this tutorial. When you create your business process, the cubes do not contain data.
- Click WS1-Dept Income Statement - Plan.
The form with duly formatted Data Grid is displayed.
Note:
The style selector has switched automatically to the default style - Custom and Cell Style. - From the quick toolbar that is displayed above the form, click the style icon.
- From the menu, click Cell Style.
In this style option, no custom (format-only) styles are applied on the form. In the following sections, we will be enabling the Rules for Cell Style and reviewing them in the forms.
Enabling format styles using Groovy Rules
- On the right, click Actions, then click Edit.
A Dynamic Tab (with the prefix Edit) opens with Forms Designer for the selected Data Grid.
- On the top, click Business Rules.
- In Business Rules Properties, for Plan1 – Rule – ValidateOtherCompensation, select Run After Load.
- Click Save.
- In Information, click OK.
- In the bottom tabs, click WS1-Dept Income Statement - Plan.
In the runtime form, the values for Account 6160: Other Compensation are shown with the background Pink (this is as per the Groovy Business Rule: Plan1 - Rule – ValidateOtherCompensation)
Note:
The style selector has switched automatically to the default style - Custom and Cell Style.
Enabling format styles using Data Validation Rules
- In the bottom tabs, click Edit WS1-Dept Income Statement - Plan.
- On the top, click Business Rules.
- In Business Rules Properties, for Plan1 – Rule – ValidateOtherCompensation, uncheck Run After Load.
- Click Save.
- In Information, click OK.
- On the top, click Layout.
- In the right panel, click Format/Validation Rules.
- In Format/Validation Rules, for Rules for location select All Rules.
- In Format/Validation Rules, select ValidateMaxAllowedOtherCompensation and then click
(Edit Validation Rule).
The Format/Validation Rule Builder displays.
- In Format/Validation Rule Builder, for Enable format/validation rule select the check box.
- Click OK.
- Click Save.
- In Information, click OK.
- In the bottom tabs, click WS1-Dept Income Statement - Plan.
In the runtime form, the values greater than 4000 for Account 6160: Other Compensation are shown with the background Yellow (this is as per the Data Validation Rule: ValidateMaxAllowedOtherCompensation).
Note:
The style selector has switched automatically to the default style - Custom and Cell Style.
Validating precedence of Groovy Rules over Data Validation and Format Rules
Multiple Rules can be specified for the same cells on a form which could impact how formatting is displayed. A form could include a Groovy Rule, a Data Validation Rule, Web form styles, and a Format Rule all at the same cells. In such cases, the order of precedence controls the displaying Rules in the forms. The order of precedence (highest to lowest) is as follows:
- (P1) Groovy Rule
- (P2) Data Validation Rule in the Format/Data Validation Rule Builder
- (P3) Oracle Smart View for Office cell styles
- (P4) Format Rule in the Format/Data Validation Rule Builder
- (P5) Smart View Custom formatting (not applicable on Web forms)
Note:
For a cell that inherits Data Validation Rules that are defined in multiple places (grid, row, column, or cell level), the Rule that is closest to the location of the Rule definition wins priority. So if there is a Rule applied at the cell level, that Rule wins. Next is column level, then row level, and then grid level.- In the bottom tabs, click Edit WS1-Dept Income Statement - Plan.
- On the top, click Business Rules.
- In Business Rules Properties, for Plan1 – Rule – ValidateOtherCompensation, select Run After Load.
- Click Save.
- In Information, click OK.
- In the bottom tabs, click WS1-Dept Income Statement - Plan.
In the runtime form, now both the Rules (the Data Validation Rule as well as Groovy Rule) are enabled. Groovy Business Rule takes precedence over all other Rules. Only the Cell Values, which are not impacted by Groovy Business Rule, are shown with the Yellow Background, which is the format as per Data Validation Rule.
Related Links
Data Forms in Web - Format Display in Runtime
G24130-01
January 2025