Glossary:Pega Express test plan

Pega Express Testplan, pega express testplan, Pega Express Test Plan

A path through the application that guides the test team towards testing use case by use case, in the order in which journeys, microjourneys, and solution capabilities are developed.

A path through the application that guides the test team towards testing use case by use case, in the order in which journeys, microjourneys, and solution capabilities are developed.

A path through the application that guides the test team towards testing use case by use case, in the order in which journeys, microjourneys, and solution capabilities are developed.

A path through the application that guides the test team towards testing use case by use case, in the order in which journeys, microjourneys, and solution capabilities are developed.

1) In user portals, a "team" is equivalent to a "work group". 2) One or more associates who work semi-autonomously on recurring tasks or towards a common goal. In a Pega Workforce Intelligence hierarchy, departments are comprised of teams. (Defined by the WFI team)

Actual work that is performed by application users and automations that consists of a sequence of tasks and leads to an intended business goal. An example of a case is a process of hiring a particular job candidate, where an HR worker collects necessary documents, a hiring manager conducts a job interview, and an application sends an automated email with onboarding information after the candidate is approved. To create a case, you first build a template of your business process that is a case type, and then apply the template in multiple cases, for example, to review applications from many candidates.

Within Pega Robot Studio, solutions and projects are containers for all the items required to build and run a project. Solutions can include multiple projects. Once you deploy a solution to the Pega Robotic Automation Deployment Portal, it is known as a package.