Glossary:Change request (CR)

Change Request, change request

Anything that impacts the objectives, cost, timeline, or resources on a project. Even changes that have no cost impact should be logged. A change may be instigated by the project team or the customer. Change requests should be recorded on the weekly Project Status Report and in a change log.

Anything that impacts the objectives, cost, timeline, or resources on a project. Even changes that have no cost impact should be logged. A change may be instigated by the project team or the customer. Change requests should be recorded on the weekly Project Status Report and in a change log.

Anything that impacts the objectives, cost, timeline, or resources on a project. Even changes that have no cost impact should be logged. A change may be instigated by the project team or the customer. Change requests should be recorded on the weekly Project Status Report and in a change log.

An entity that bundles functionality when you develop solutions with Pega Robot Studio. You can integrate applications, monitor events, and automate tasks. Adapters, automations, and global containers are stored as .os and .xml files in the solution and project folders.

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)

A work party that typically initiates a case. In many applications, only one customer can be associated with a case.