Hi Rahul,
If you're using the standard MFSM execution flow shown in your screenshots (Basis → Materials → Notes → Other), I would avoid directly modifying the core execution logic unless absolutely necessary.
The usual approach is to integrate Checklist and Material Consumption as activities tied to the Work Order lifecycle rather than injecting custom logic into every execution step.
For example:
Materials Tab
Checklist Tab
A flow that has worked well for similar field-service implementations is:
Start Work
↓
Generate Checklist
↓
Execute Checklist
↓
Record Material Usage
↓
Add Notes/Attachments
↓
Complete Work Order
Rather than embedding warehouse-selection logic directly in the execution page, I would create a separate material selection microflow/page that:
Looking at your screenshots, the cleanest implementation would be:
One additional recommendation: don't wait until Work Order completion to validate materials and checklist completion. Add validation on the Complete Work Order action so technicians receive a clear message such as:
"Required checklist items are incomplete."
or
"Required materials have not been issued."
This keeps the standard MFSM execution experience while adding Checklist and Materials management without heavily customizing the core flow.