This requirement is a classic calculated-field transformation for an outbound report-based integration. The first step is to use Substring Text to extract only the first three characters from the worker’s first name and the first three characters from the worker’s last name. After both substrings are produced, Concatenate Text joins those values into a single User ID string. Finally, Format Text is required to convert the combined result to lowercase so the output matches the Active Directory vendor standard. Evaluate Expression is not required because there is no conditional logic. Lookup Related Value is also inappropriate because the values are already available from worker name fields. Text Constant is not enough because the result must be dynamically built for each worker.

================

The requirement is to filter a custom report to show only workers terminated after a user-prompted date. In Workday, filters are defined in the Filter tab of the custom report definition, and conditions can be combined using AND/OR logic to refine the dataset. Let’s analyze the requirement and options:

Key Conditions:

Workers must be terminated, so the " Worker Status " field must equal " Terminated. "

The termination must occur after a user-specified date, so the " Termination Date " must be greater than the prompted value.

Both conditions must be true for a worker to appear in the report, requiring an AND combination.

Option Analysis:

A. Worker Status is equal to the value " Terminated " OR Termination Date is greater than a value retrieved from a prompt: Incorrect. Using OR means the report would include workers who are terminated (regardless of date) OR workers with a termination date after the prompt (even if not terminated), which doesn’t meet the strict requirement of terminated workers after a specific date.

B. Worker Status is equal to the value retrieved from a prompt AND Termination Date is less than a value retrieved from a prompt: Incorrect. Worker Status shouldn’t be a prompted value (it’s fixed as " Terminated " ), and " less than " would show terminations before the date, not after.

C. Worker Status is equal to the value retrieved from a prompt OR Termination Date is equal to a value retrieved from a prompt: Incorrect. Worker Status shouldn’t be prompted, and " equal to " limits the filter to exact matches, not " after " the date. OR logic also broadens the scope incorrectly.

D. Worker Status is equal to the value " Terminated " AND Termination Date is greater than a value retrieved from a prompt: Correct. This ensures workers are terminated (fixed value) AND their termination date is after the user-entered date, precisely meeting the requirement.

Implementation:

In the custom report’s Filter tab, add two conditions:

Field: Worker Status, Operator: equals, Value: " Terminated " .

Field: Termination Date, Operator: greater than, Value: Prompt for Date (configured as a report prompt).

Set the logical operator between conditions to AND.

Test with a sample date to verify only terminated workers after that date appear.

References from Workday Pro Integrations Study Guide:

Workday Report Writer Fundamentals: Section on " Creating and Managing Filters " details combining conditions with AND/OR logic and using prompts.

Integration System Fundamentals: Notes how filtered reports support integration data sources with dynamic user inputs.

Creating or associating a filename sequence generator is not enough by itself. The EIB must be configured so the File Name launch parameter determines its value at runtime from the sequence generator utility. The correct runtime field is Next Sequence for Integration File Utility. If the launch parameter is not set this way, Workday can still use a static or manually supplied filename, which means the configured sequence generator will not drive the final output filename. Typing the sequence generator name as a static value would not invoke the generator. The issue is also not simply a transformation problem or delivery endpoint problem. The key configuration gap is that the runtime filename value was not linked to the sequence generator output.

================