No matching entry criteria.Submitted

Hi ,

I have created a criteria as below and added it to the “Submitted” status of “ECO Workflow”,Also, I have added a “Cpacitor” item to ECO with “Product Lines” set to “Aries” and “Category ” to “Electrical”, now when I move the ECO from Pending to Submit, I am receiving the error “No matching entry criteria.Submitted”, my question is even though the “Capacitor” Item is satisfying the criteria, this error persists.

This is the issue continuing for all the values(All,Same,Some) of “Status Criteria Matching Type” of  “ECO Workflow”

Criteria : ECO Affected Items.Item Product Lines Equal To [Parts]Aries And
Affected Items.Item Category In [Parts]Electrical


Agile Talent Asked on February 3, 2019 in Agile PLM (v9),   Product Collaboration.
Add Comment
4 Answer(s)

When criteria includes affected items then the status matching criteria (All, Same, Some) comes into play. Usually you want “Some” of the affected items match the same criteria. Unless you are trying to keep the change order from being submitted unless certain criteria is met, use a generic “catch-all” criteria that will allow the change to be submitted. Then add specific criteria for notifications and required fields.

Agile Angel Answered on February 3, 2019.
Add Comment

Hi Steve,

If  I add the generic criteria, it will pass ok, but I am trying to understand the (All,Same,Some) functionality clearly, so only I removed the generic criteria, if you have some example to understand the difference clearly,please let me know.


Agile Talent Answered on February 4, 2019.
Add Comment

Hi Surya – 
The Status Criteria Matching Type (SCMT) confused me for a long time as well. 

As Steve mentioned – this setting only matters at all if any of your status criteria (the criteria that you add to a specific workflow status) refers to something at the affected item level.  In other words if you only use generic status criteria, Like “All ECOs” or other status criteria that doesn’t drill down to the affected items level – it doesn’t matter what you set the SCMT to.

If /When any of your status criteria DOES refer to something at the Affected Items’ level (as your example criteria does) – then the SCMT setting does matter, but only for changes that contain multiple affected items.  If a change has only one affected item – the SCMT setting is more or less ignored.

SO – When a change contains more than one affected item AND the workflow it uses contains affected item based status criteria – the SCMT setting tells the workflow how to behave in relation to each affected item and the affected item based status criteria:

When set to ALL – it means that all of the affected items have to match at least one of a the affected item based status criteria. 

When set to SAME – it means that all of the affected items have to match the same affected item based status criteria.  

When set to SOME – it means that only one (or more) of the affected items has to match at least one of the affected item based status criteria.

Note – this is evaluated separately for each status that contains affected item based criteria upon attempted entry.

Agile Angel Answered on February 4, 2019.
Add Comment

In response to your original problem as to why you are getting the error when the affected item meets the status criteria – 

To troubleshoot – I would recommend enabling the two ‘read through’ fields on the ECO object itself to make sure that it is actually passing the values that your criteria expects.

Java Client > Admin > Data Settings > Classes > *Open ECO Subclass

*Select ‘User Interface Tabs’ Tab > *Open Affected Items > *Select ‘Attributes:Affected Items’ tab.
*Scroll down list to find and enable ‘Item Category’ and ‘Item Product Lines’ (set visible to ‘yes’)

Now go back the the ECO object that is getting the error and check these fields on the Affected Items tab of the ECO (rather than opening the item objects) to check the ‘Item Product Lines’ and ‘Item Category’ values.

It might even be the case that you need to have these fields visible on the change object for the criteria to work.  This shouldn’t be necessary, but I seem to remember encountering something similar several versions/years back and enabling the affected item read-through fields fixed my issue.  Might not be the same thing, but it won’t hurt anything to make sure…

Agile Angel Answered on February 4, 2019.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.