The Prism use case is to classify workers based on their pay.

Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, classifying workers into pay ranges based on their pay requires creating a new field that evaluates the pay values and assigns them to defined ranges (e.g., "Low," "Medium," "High"). According to the official Workday Prism Analytics study path documents, the recommended approach is to create a derived dataset (DDS) and build a CASE calculated field to classify workers against their pay (option B). The CASE function in a calculated field allows users to define conditional logic (e.g., CASE WHEN pay < 50000 THEN "Low" WHEN pay < 100000 THEN "Medium" ELSE "High" END), which is ideal for creating pay range classifications. This calculated field is added within a deriveddataset, which can then be published as a Prism data source, making the new field available for reporting and analytics.

The other options are not optimal:

A. Add the additional field to your raw data before you ingest into Prism: Modifying raw data outside Prism is unnecessary and less flexible, as Prism’s transformation capabilities (like CASE) are designed for such tasks.

C. Build a CASE calculated field function on the TBL directly to ease later transformation: Calculated fields cannot be created directly on a table (TBL) in Prism Analytics; they must be defined in a derived dataset.

D. Build an Evaluate Expression calculated field on your final Prism business object to evaluate workers against their pay: Prism Analytics does not use "Prism business objects" for calculated fields, and "Evaluate Expression" is not a standard function; this option is not applicable.

Using a CASE calculated field in a derived dataset provides a flexible and maintainable way to classify workers by pay ranges, ensuring the field is included in the final Prism data source.