A use case represents a small atomic processing unit performed by one or more actors for a given work type within an application. A single use case implementation may correspond to an entire flow, a single flow action, a screen flow, an activity with the May Start? option enabled or the New harness of a flow.

Typically, use cases are entered in an Application Profile, created by the Enterprise Application Accelerator, and made available for update as instances of Rule-Application-UseCase rules as a project evolves.

They also are referenced in application, flow, activity and flow action rules.

See the Pega Developer Network article PRKB-25652 Working with Use Cases and others listed under the Implementation Methodology knowledge category for more information.

	actor, Direct Capture of Objectives, Application Profile, Enterprise Application Accelerator
	About Application Use Case rules About Application rules About Flow rules

Definitions — U