What You May Need to Know About the Custom Permissions for the Rules Editor Component

Using Declarative Components and Task Flows 25-23 locale java.util. Locale no Locale.get Default yes Used for Localization ruleModel java.lang. String no oracle. bpel.rules dc.model. impl. RuleModel yes Used to customize the default RuleModel. You can extend the RuleModel class to override certain methods. rulesetModel oracle.bpel. rulesdc.model. interfaces. RuleSetInterface yes - Only EL Wrapper around the Rules SDK ruleset object.You can use the RuleSetModel object supplied as part of the Rules Editor Component jar file adflibRulesDC.jar. rulesPageSize java.lang. Integer no 5 yes Specifies the number of rules to be displayed in a page. It is used in IFTHEN rules pagination. | showDTButtons java.lang. Boolean no true yes Displays the Add and Delete Decision Table links by default. You can choose to hide this by setting this to false. showValidationPanel java.lang. Boolean no true yes Displays the validation panel by default. You can choose to hide this by setting this to false. simpleTestModel java.lang. String no oracle. bpel.rules dc.model. impl. SimpleTest Model yes Used to customize the default SimpleTestModel. You can extend the SimpleTestModel class to override certain methods. timeStyle java.lang. String no Gets from the locale yes If specified, the time style is used in all inputDate components, for example HH:mm:ss. timezone java.util. TimeZone no TimeZone. getDefault yes Used for Localization Table 25–2 Cont. Supported Attributes of the Rules Editor Component Name Type Required Default Value Supports EL? Description 25-24 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

25.3 Using the Oracle Business Rules Dictionary Editor Declarative Component

This section discusses the Oracle Business Rules Dictionary Editor declarative component. It also provides information on how to create and run an application using the Rules Dictionary Editor component, and then deploy the application. In addition, this section lists the supported tags and the localization process for the application.

25.3.1 Introduction to the Oracle Business Rules Dictionary Component

The Oracle Business Rules Dictionary Editor is a composite declarative component that can be embedded in any ADF-based Web application. It enables you to edit business rules metadata artifacts, such as Globals, Bucketsets, and Rulesets, by using the Rules SDK2 API. The Rules Dictionary Editor Task Flow uses the Rules Dictionary Editor Component to create applications. Typically, you should either use the Rules Dictionary Editor component or the Rules Dictionary Editor task flow, but not both. For more information on Rules Dictionary Editor Task Flow, see Section 25.4, Using the Oracle Business Rules Dictionary Task Flow. The Rules Dictionary Editor component performs the following: ■ Edits Globals or Variables that have the final attribute set to true by using the Globals Editor, as shown in Figure 25–29 . viewOnly java.lang. Boolean no true yes If true, in the viewOnly mode, you can view the existing rules in the ruleset. If false, which is the edit mode, you can add new rules and edit existing rules. Note: You should not confuse Rules Dictionary Editor with Rules Editor. Rules Editor is used to edit rules inside a specified ruleset. In fact, Rules Editor is embedded within Rules Dictionary Editor. For more information about Rules Editor, see Section 25.2, Using the Oracle Business Rules Editor Declarative Component. Table 25–2 Cont. Supported Attributes of the Rules Editor Component Name Type Required Default Value Supports EL? Description