Basic person information

A process that captures basic person information, validates it, and checks for the presence of duplicate information.

Multiple entity component can be used to capture information of multiple person entities as part of a single step in any case type.

Detailed person information

A process that captures detailed person information like ethnicity, race, communication preferences, and so on, validates it, and checks for the presence of duplicate information.

Business information

A process that captures business information like legal name, trade name, office location, communication details, and so on, validates it, and checks for the presence of duplicate information.

Facility information

A process that captures facility information like facility name, contact details, location, and so on, validates it, and checks for the presence of duplicate information.

Vehicle information

A process that captures vehicle information like model, make, registration number, garage location, owner details, and so on, validates it, and checks for the presence of duplicate information.

Household information

A process that captures household information like household name, type, description, location, members of the household, and so on.

Persist object component

A generic component that saves entity related information and data object information in the system of record.

Capture experience

A process that captures the experience details of a person.

Capture training

A process that captures the training details of a person.

Capture location

A process that captures the location details of an entity.

Consent agreement

Consent agreement is a feature that displays an actionable consent agreement screen. This screen contains customizable text for the agreement clauses of your organization, a check box to signify agreement, and a field to provide a signature. Pega Government Platform extends Pega App Studio to provide additional business configuration capabilities for the consent agreement.