Dynamics Community Forum Thread Details

Clarification on Product Readiness Policy and Checklist in D365 F&O Engineering Change Management

I would like to clarify a few points regarding the Product Readiness Policy under the Engineering Change Management module D365 F&O.
Within the readiness policy we use the Readiness Control option, where we can add checks. Currently the "Add Check" option displays only fifteen available checkpoints. I noticed there is a "Refresh List" option—could you please confirm if using this will provide additional checklist items?
Additionally, I would like to implement some restrictions through the Engineering Change Order (ECO) process. For example:

The ECO should not be processed unless a BOM Unit is defined.
Certain fields should be marked as mandatory, preventing further steps unless they are completed.

Could you please confirm if these configurations are possible, and if so, guide me on how to implement them.

Or else, how we make customize questionaries in readiness policy.

Please find below SS

Categories:

Dynamics 365 Supply Chain Management

Hi RD-24060816-0,

can you provide more information on the requirement?

Basically, and on the description above, find the following answer:

Yes, in D365 FO, specifically within the Engineering Change Management module, the "Add Check" option under the Product Readiness Policy currently displays only fifteen available checkpoints by default. The "Refresh List" option is intended to update the list of available checks, and yes, using it can potentially reveal additional checklist items that were not initially loaded or visible. If you're not seeing more than fifteen even after refreshing, it could be e.g. due to:

- Limited configuration or setup of readiness checks
- Permissions or roles restricting visibility
- Customizations not being properly deployed

To implement the requirements, find the following guidance:

1) Prevent ECO Processing Without a BOM Unit
- You can enforce this by configuring Product Readiness Policies and checklists
- Navigate to Engineering Change Management > Setup > Product Readiness Policy
- Create or edit a policy and add a check that validates whether a BOM Unit is defined
- If the BOM Unit is missing, the system can block the ECO from progressing until it's completed

2) Make Certain Fields Mandatory
- To enforce mandatory fields before progressing an ECO
- Use Product Readiness Checks to define which fields must be filled
- Alternatively, configure data validation rules or custom workflow approvals that prevent submission or approval of ECOs unless required fields are completed
- You can also use form personalization or custom extensions to make fields mandatory at the UI level

3) Customize Questionnaires

- Navigate to
- Engineering Change Management > Setup > Product Readiness Policy
- Create or Edit a Policy
- Add a new check and select Checklist as the type
- Define the Checklist
- You can enter a series of questions
- Each question can have expected answers (e.g., Yes/No, dropdowns)
- The system will evaluate whether the answers meet the defined criteria
- Assign the Checklist
- Link it to specific products, variants, or engineering versions
- You can also assign it to roles or teams responsible for validation

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References: