A component RuleSet contains rules that are designed to define reusable applications or functionality that executes embedded within an object. When a component RuleSet is installed in multiple systems, the class of the object may vary from system to system.
Because the rules in a component RuleSet are constructed without knowledge of the class of the object that will execute them, these must follow strict restrictions: PROJ-1318 5.4
pyWorkPage
, for read or update, and cannot use the
Primary
keyword or Top
keyword in property
references. All communication with the calling application is through
flow parameters, activity parameters, a shared clipboard page or
pages, and a shared property.For example, work objects your application may include multiple United States mailing addresses, some with incorrect or missing postal Zip codes. A component RuleSet can include rules that connect using SOAP to a Web service provided to validate or correct Zip codes in these addresses. Your calling application can pass a page (of class Data-Address) containing a street address to the component RuleSet to evaluate. Such pages may appear within a large variety of objects belonging to many distinct, unrelated top-level classes.
After it looks up the correct Zip code, the component can return status information and the answer to your application through callback property values, or through properties on a clipboard page that both the calling application and the component application share.
You define a RuleSet as a component type on the Category tab in the RuleSet form. Identify the RuleSet in the Component and Shared RuleSets array on the General tab of an application rule referenced by your access group.
In Java terms, a Component RuleSet provides encapsulation.
RuleSet list, rule resolution | |
About
RuleSets
About Application rules How the system assembles and uses your RuleSet list |