Restricting the Release of Obsolete Items using Criteria

When I move the status from Pending to Submit (if Item is obsolete), I should get the Error message. Obsolete item cant be released.

Can this be achieved through criteria?

Agile Expert Asked on March 3, 2015 in Agile PLM (v9),   Product Collaboration.
Add Comment
15 Answer(s)

Did you try criteria based on “affected item not equal to Obsolete LC”

Agile Expert Answered on March 3, 2015.
Add Comment

I have tried with that criteria. Also I gave Status Criteria Matching Type as ‘Same’ in workflow. But it didn’t work.

Agile Expert Answered on March 3, 2015.
Add Comment

I have an affected items criteria requirement (item number can not be null) on the submitted step. Did you use pending step or submitted step for your criteria

Agile Expert Answered on March 3, 2015.

I have used pending step for my criteria.

on March 3, 2015.
Add Comment

It would seem like Pending would be correct but for some reason my critera only worked when I used Submitted step. Try it.

Agile Expert Answered on March 3, 2015.
Add Comment

I included in both statuses. Still it is not working.

Agile Expert Answered on March 3, 2015.
Add Comment

I use the AddLifeCyclePhaseonBOMRule on the parts lifecycle tab. It will not allow an obsolete item onto a new BOM. This stops an obsolete item for being on a BOM.

Agile Expert Answered on March 3, 2015.
Add Comment

For Obsolete lifecycle phase, AddLifeCyclePhaseOnBomRule is set to disallow.

Agile Expert Answered on March 3, 2015.
Add Comment

Use criteria “Change Orders Affected Items.Lifecycle Phase Not In Items.Obsolete” .. Apply this criteria on your change order workflow…It should work..You will get an error message “The object violates the workflow criteria”

Agile Expert Answered on March 3, 2015.
Add Comment

May be other criteria is overriding for you.. check the exit and entry criteria in workflow status tab..

Agile Expert Answered on March 3, 2015.
Add Comment

There are multiple criteria. I have given Status Criteria Matching Type as Same. But it didn’t work.

Agile Expert Answered on March 3, 2015.
Add Comment

Your Answer

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