BOM Release Rule - Offending Collected Object

[pwilliams-3]

Currently (10.1 M040), when the BOM release rule fails, the resulting item is displayed in the conflicts table but the offending object is not given.  This results in a wild goose chase to find the offending object.  In some cases such as an EPMDocument that References another EPMDocument this can be quite time consuming.  To reduce the time, an administrator can set the com.ptc.core.businessRules.validation.BOMReleaseRuleValidator logger to DEBUG and ask the user to Resolve Conflicts to run the rule again.  This will produce the below messages in the error logs.  An admin can then search for the offending object using the object id.

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Collection component insatnce is:com.ptc.core.htmlcomp.collection.engine.CollectionComponentInstance@48dbecd5

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - The config checkPredecessorRevisions is not set, defaulting to false

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - The config checkPredecessorRevisions is set to false

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - life cycle states are:RELEASED

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Lifecycle state is:RELEASED

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Life cycle managed states are:[RELEASED]

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - config: targetState, states: [RELEASED]

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - life cycle states are:RELEASED

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Lifecycle state is:RELEASED

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Life cycle managed states are:[RELEASED]

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - config: validDependentState, states: [RELEASED]

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Life cycle managed states are:[]

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - config: invalidDependentState, states: []

2015-10-14 14:55:01,007 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Transition is:PRODUCTION_RELEASE

2015-10-14 14:55:01,008 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - changeables are:[wt.epm.EPMDocument:2138118520, wt.epm.EPMDocument:2138111271, wt.part.WTPart:2138119466]

2015-10-14 14:55:01,011 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - lifecyle map is {wt.epm.EPMDocument:2138118520=RELEASED, wt.epm.EPMDocument:2138111271=RELEASED, wt.part.WTPart:2138119466=RELEASED}

...

2015-10-14 14:55:02,064 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - Life cycle state is:CREATE

2015-10-14 14:55:02,064 DEBUG [WfPropagationQueue.PollingThread] com.ptc.core.businessRules.validation.BOMReleaseRuleValidator wcadmin - The dependent object wt.epm.EPMDocument:1578421365 is not in a valid state: CREATE

Please add the offending object in the conflicts table when the BOM Release Rule fails!!!

[ChrisPLM]

It makes sense.

Modelcheck gives the offending object when error are returned

CHeck In will also give the offending objects.

So why not the BOM release rule ?

[arajanala]

How do we vote for this idea ?

I don't see any options to do it

Thanks,

Athmanand

[ChrisPLM]

Hi arajanala

you can't anymore as the status as changed to FOR FUTURE CONSIDERATION.

PTC has already acknowledge this week point and should soon provide improvement in new releases.

Best regards

[JeffZemsky]

Sorry about that - meant to make it UNDER CONSIDERATION which still allows Voting.

[ChrisPLM]

Thanks Jeff

so it is even better statuses then  

Best regards

[arajanala]

Thanks Chris and Jeff

Regards,

Athmanand

[OliverDroop]

The offending objects should be displayed together with some actions to fix the reasons.

We have customized this an offer an info icon as well as mass update to fix attributes.

Objects which got missed to fullfil the maturity rule and should be on the ECN should be easily additable

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.