Determine the trigger mode for run wave

You can now use the Redwood Wave Inquiry screen to see the source screen and module responsible for creating a wave, making it easier to distinguish between waves initiated manually, from template-driven processes, by scheduled jobs, or through REST APIs. This additional context simplifies operational reviews and troubleshooting and provides a clearer audit trail without requiring you to investigate other system activity to determine how a wave originated.

View the source of a wave

Previously, waves created through different trigger methods could appear identical in Wave Inquiry. For example, a user could select a wave template from the Manual Wave screen, while the same template could also be triggered from the Wave Template screen or by a scheduled job. Wave Inquiry did not provide enough information to distinguish between these scenarios.

The Redwood version of Wave Inquiry now captures and displays two new fields that identify the source context of the wave:

• wave_trigger_module_name – Identifies the module from which the wave was triggered.
• wave_trigger_screen_name – Identifies the screen, scheduled job instance, or API associated with the wave trigger.

Both fields are available as display columns in the Wave Inquiry datagrid. They are also available as filter criteria, allowing you to find waves triggered from a particular source.

Note: The new wave_trigger_module_name and wave_trigger_screen_name fields are available only in the Redwood version of Wave Inquiry.

Supported wave trigger sources

The trigger information is captured for supported wave creation flows, including the following:

Wave Trigger Source	Information Captured
Manual Wave screen	Module and screen associated with the Manual Wave flow
Order Inquiry	Module and screen associated with the Order Inquiry flow
Wave Template screen	Module and screen associated with the Wave Template
Replenishment Template screen	Module and screen associated with the Replenishment Template
Wave Group screen	Module and screen associated with the Wave Group
Scheduled Job	Module identifies the scheduled job flow, and the screen identifies the corresponding scheduled job instance that triggered the wave
REST API	Module identifies the REST API framework, and the screen identifies the API that triggered the wave

For waves triggered by a Scheduled Job, wave_trigger_module_name can display ScheduledJobView, while wave_trigger_screen_name identifies the scheduled job instance. Supported jobs include Normal Picking Wave, Trigger Wave Group, Trigger Work Order Wave, and Replenishment Wave.

For waves triggered through a REST API, wave_trigger_module_name displays lgfapi.v10, while wave_trigger_screen_name identifies the API/entity used to trigger the wave. Supported operations include run_template and run_manual, with or without a specific wave template ID.

The supported wave-triggering REST API operations include:

• POST .../entity/wave_template/run_template/

• POST .../entity/wave_template/{id}/run_template/

• POST .../entity/wave_template/run_manual/

• POST .../entity/wave_template/{id}/run_manual/

Search and filter by wave trigger

Because wave_trigger_module_name and wave_trigger_screen_name are included in the Wave Inquiry entity, you can add them to the Redwood Wave Inquiry datagrid to review the origin of individual waves.

You can also use these fields as filter criteria. For example, you can filter Wave Inquiry to identify waves initiated by a scheduled job, from a particular application flow, or through an API.

Steps to enable and configure

No additional wave configuration is required to capture the trigger source for supported wave flows.

To view the new information:

1. Navigate to the Redwood Wave Inquiry screen.
2. Configure the datagrid columns to include wave_trigger_module_name and wave_trigger_screen_name.
3. Review these fields to determine the source that triggered each wave.
4. When needed, add wave_trigger_module_name and/or wave_trigger_screen_name as filter criteria to locate waves created through a specific trigger method.

The new trigger-source fields are exposed only in the Redwood version of Wave Inquiry.