The "Create a Component" and the "Embed a Component" wizards where both deprecated with the release of PRPC 6.1. However, PRPC 6.1, 6.2, 6.3, and Pega 7.1 all still support Components and their use. Creating and Embedding a Component is now a manual development pattern that can be implemented by creating and using a Component RuleSet.
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:
Contains one or more class rules for embedded pages, typically an abstract class derived from the Work- class.
All rules other than class rules have an Applies To key part that is one of the classes in the RuleSet.
Rules cannot explicitly reference top-level pages such as 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.
A component RuleSet cannot create work items or include harnesses.