In the Weblogic console, select Deployments and click Install to display the

25-20 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite ■ oracle.rules.adf.permission.DeleteRulePermission: Displays the Delete Rule button; if the permission is not granted, the Delete Rule button is not visible to the user. ■ oracle.rules.adf.permission.EditRulePermission: Displays the Edit Rule button for rules inside a ruleset; if the permission is not granted, then the rules are View-Only. ■ oracle.rules.adf.permission.AddDTPermission: Displays the Add Decision Table button; if the permission is not granted, the Add Decision Table button is not visible to the user. ■ oracle.rules.adf.permission.DeleteDTPermission: Displays the Delete Decision Table button; if the permission is not granted, the Delete Decision Table button is not visible to the user. ■ oracle.rules.adf.permission.EditDTPermission: Displays the Edit Decision Table button for decision tables within a ruleset; if the permission is not granted, the decision tables are View-Only. ■ oracle.rules.adf.permission.RulesEditorPermission: A global permission that sets all the preceding permissions to true. For example, to grant the delete rule permission to a role, specify the following code in the jazn-data.xml file of the application: grant grantee principals principal classoracle.security.jps.service.policystore.ApplicationRoleclass namerole2name principal principals grantee permissions permission classoracle.rules.adf.permission.DeleteRulePermissionclass nameDeleteRulePermissionname actionsaccessactions permission permissions grant If you do not want to use the individual permissions, such as AddRulePermission or DeleteRulePermission, you can just set the RulesEditorPermission in the jazn-data.xml file to set global permissions.

25.2.5 What You May Need to Know About the Supported Tags of the Rules Editor Component

This section lists the tags and attributes that are supported by the Rules Editor component. Table 25–1 lists the supported facets. Using Declarative Components and Task Flows 25-21 Table 25–2 lists the supported attributes. Table 25–1 Supported Facets of the Rules Editor Component Name Description patternDisplay Used to render specific user interfaces. This facet is used to display the rule condition and pattern in advanced mode, which is the IF portion of the rule. actionDisplay Used to render specific user interfaces. This facet is used to display the rule action, which is the THEN portion of the rule. Table 25–2 Supported Attributes of the Rules Editor Component Name Type Required Default Value Supports EL? Description dateStyle java.lang. String no Gets from the locale yes If specified, the date style is used in all inputDate components, for example, yyyy.MM.dd. decimalSeparator java.lang. Character no Based on Locale yes Specifies the decimal separators. This is used in Number Formatting. If specified, this attribute overrides the decimal separator based on locale. disableRuleSetName java.lang. Boolean no false yes If true, the editable ruleset name is disabled. This attribute is used only when displayRuleSetNa me is set to true. discloseRules java.lang. Boolean no false yes If true, all the rules in the ruleset are expanded. If false, all the rules are collapsed. displayRuleSetEffDate java.lang. Boolean no true yes If true, the Rules Editor component renders the user interface for displaying the effective dates for the RuleSet. displayRuleSetName java.lang. Boolean no true yes Displays the editable ruleset name by default. You can choose to hide this by setting it to false.