The base product provides a generic BO for Form Rule Group, C1-FormRuleGroup. Your implementation can add additional business rules to this BO as required.
The base product provides a parent BO for Form Rule, C1-FormRule. This BO defines the common elements for all form rules. It is not intended to be used stand-alone. Your implementation can include this BO in each rule BO and add the additional components as required.
The base product supplies a number of BOs that apply particular Form Rules. Refer to the business objects that reference the Form Rule maintenance object C1-FORMRULE for a complete list.
Your implementation can define additional form rule BOs as required. The following points highlight the important configuration for this business object:
Create a new business object and include the C1-FormRule business object.
Develop the appropriate rule processing algorithm to perform the rule logic.
For any configuration required by the rule processing algorithm, consider whether it should be defined when configuring the form rule by a business user. If so, include the appropriate elements in the form rule business object's schema.
For a rule that performs validation, consider whether the rule exception information, which includes the Exception Category should be defined when configuring the form rule by a business user. If so, include the appropriate elements in the form rule business object's schema. The base product provides the data area (C1-ExceptionInformation) that can simply be included in the business object schema.
For the user interface, the business object C1-FormRule and the data area C1-ExceptionInformation both support UI Hints. Many base form rule business objects also support UI hints. However, some still use full UI maps. When creating a new custom form rule, it is recommended to use UI Hints for the new business object. For an example of a base form rule business object that uses UI Hints and includes functionality for referencing a form section and line business name, refer to the Create Customer Contact business object (C1-CreateCustomerContact).
Consider what logical grouping this rule belongs to. Note that a group of rules is always executed in the context of a single rule event. Rules should be grouped according to common actions that make take place for a particular event or set of events.
The following UI map fragments are available for use in creating full UI maps for form rule display and maintenance. However, with the use of UI Hints, it is not expected that they are needed.
Map fragment to display the common elements for all form rules along with the actions: C1-FormRuleDisplay
Map fragment to display the common exception details (for validation rules only): C1-FormRuleExceptionDisplay
Common display service script to plug in on the rule BO to retrieve the form rule details: C1-FRGenDisp
Map fragment to maintain the common elements for all form rules: C1-FormRuleMaint
Map fragment to maintain the common exception details (for validation rules only): C1-FormRuleExceptionMaint
The topics in this section describe some of the base rules that may be used by your implementation. Click here for a complete list of the apply rule algorithms provided by the system. A corresponding business object exists for each one.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]