The components of Pega Government Platform
Pega Government Platform™ comes with various components that you can reuse in any application that is built on the Pega Government Platform application.
The following components belong to the PegaPS-Work class:
Entity details capture
The components in this category are part of the process of collecting details about business entities (such as companies) and person entities (such as employees). The following components belong to this category:
| Rule name | Rule type | Description |
|---|---|---|
| BasicPersonInformation | Flow | This rule captures basic information about a person, such as name and address, and persists the data in the system when you submit the form. |
| PersonInformation | Flow | This rule captures detailed information about a person, such as eye color, and persists the data in the system when you submit the form. If an entity ID is part of the form, the rule fetches the details of that person and updates the details when you submit the form. If the form does not contain any ID, the rule creates a new person record instead. |
| BasicPersonInformation | Flow action | This rule captures basic information about a person, such as name and address. It uses the BasicPersonDetails section with the Person property as context. This rule includes the PostAddPerson activity in post processing to run duplicate checks. |
| PersonInformation | Flow action | This rule captures detailed information about a person, such as eye color. It uses the PersonDetails section with the Person property as context. This rule validates data by using the Person validate rule and it includes the PostAddPerson activity in post processing to run duplicate checks. |
| PersistPerson | Flow | This rule persists basic or full information about a person and it includes two parameters: EntityPage (of the PegaPS-Data-Entity-Person class) and SaveBasicDetails. If the SaveBasicDetails check box is selected, this rule persists only the basic information. Otherwise, it persists all details that the EntityPage parameter refers. You can use this rule at any stage of a case. |
| PersistBusiness | Flow | This rule persists information about a business and it includes BusinessPage (of the PegaPS-Data-Entity-Business class) as a parameter. You can use this rule at any stage of a case. |
| BusinessInformation | Flow | This rule captures information about a business, such as name and address, and persists the data in the system when you submit the form. If an entity ID is part of the form, the rule fetches the details of that business and updates the details when you submit the form. If the form does not contain any ID, the rule creates a new business record instead. |
| BusinessInformation | Flow action | This rule captures information about a business, such as name and address. It uses the CaptureBusiness section with the Business property as context. This rule validates data by using the Business validate rule and it includes the PostBusiness activity in post processing to run duplicate checks. |
Entity details management
The components in this category are part of the process of managing entity details. The following components belong to this category:
| Rule name | Rule type | Description |
|---|---|---|
| ManageEducation | Flow | This rule captures the education details of a person, such as degrees, and persists the information by using the entity ID as a parameter. The information must be included in the EducationList property |
| ManageExperience | Flow | This rule captures the experience details of a person, such as employer name, and persists the information by using the entity ID as a parameter. The information must be included in the ExperienceList property. |
| ManageRelations | Flow | This rule captures the relationship details of a person, such as family members, and persists the information by using the entity ID as a parameter. The information must be included in the RelationList property. |
| ManageTraining | Flow | This rule captures the professional training details of a person, such as training type, and persists the information by using the entity ID as a parameter. The information must be included in the TrainingList property. |
| ManageLocation | Flow | This rule captures the location details of a person, such as address, and persists the information by using the entity ID as a parameter. The information must be included in the .Entity.AddressList property. |
| UpdateEducation | Flow | This rule saves the education details of a person, such as degrees, by using the entity ID as a parameter. The information must be included in the EducationList property |
| UpdateTraining | Flow | This rule saves the professional training details of a person, such as training type, by using the entity ID as a parameter. The information must be included in the TrainingList property. |
| UpdateExperience | Flow | This rule saves the experience details of a person, such as employer name, by using the entity ID as a parameter. The information must be included in the ExperienceList property. |
| UpdateRelations | Flow | This rule saves the relationship details of a person, such as family members, by using the entity ID as a parameter. The information must be included in the RelationList property. |
| PersistLocation | Flow | This rule saves the location details of a person, such as address, by using the entity ID as a parameter. The information must be included in the .Entity.AddressList property. |
| ManageEducation | Flow action | This rule captures the education details of a person, such as degrees, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the EducationList property. This rule can be used at any stage of a case. |
| ManageExperience | Flow action | This rule captures the experience details of a person, such as employer name, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the ExperienceList property. This rule can be used at any stage of a case. |
| ManageRelations | Flow action | This rule captures the relationship details of a person, such as family members, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the RelationList property. This rule can be used at any stage of a case. |
| ManageTraining | Flow action | This rule captures the professional training details of a person, such as training type, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the TrainingList property. This rule can be used at any stage of a case. |
| ManageLocation | Flow action | This rule captures the location details of a person, such as address, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the .Entity.AddressList property. This rule can be used at any stage of a case. |
| ManageEducation | Section | This rule captures the education details of a person, such as degrees, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the EducationList property. This rule can be used at any stage of a case and included in any other section. |
| ManageExperience | Section | This rule captures the experience details of a person, such as employer name, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the ExperienceList property. This rule can be used at any stage of a case and included in any other section. |
| ManageRelations | Section | This rule captures the relationship details of a person, such as family members, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the RelationList property. This rule can be used at any stage of a case and included in any other section. |
| ManageTraining | Section | This rule captures the professional training details of a person, such as training type, but it does not fetch any existing information or save the details when you submit the form. The information is then included in the TrainingList property. This rule can be used at any stage of a case and included in any other section. |
Other processes
The components in this category are independent of entities. The following components belong to this category:
| Rule name | Rule type | Description |
|---|---|---|
| Evaluate | Flow | You can use this rule to evaluate an application against various criteria. The system recommends actions that are dependent on the total score. This flow contains a list of evaluation types and radio button for routing as parameters. Depending on the choice of routing options, the list of available options changes. |
| Review checklist | Flow | You can use this rule to review an application against various checklist items. This flow takes a list of checklist types and a radio button for routing as parameters. Depending on the choice of routing options, the list of available options changes. |
| Consent agreement | Flow | You can use this rule to display the consent agreement screen that contains the text of the agreement, a Boolean-type check box, and a signature field. This flow takes a list of consent agreement templates and a checkbox for an e-signature as parameters. |
Previous topic Ruleset changes in Pega Government Platform 8.1