How to set the ECR to resolved when few ECN are Resolved and others are Canceled

Forum|Forum|5 years ago
February 23, 2021
3 replies
4755 views

Hi All,

Can anyone let me know how to set the ECR to resolved programmatically even if one ECN is resolved and others are Cancelled?

I checked on the code within the Synch on Change Notice Implementation where it has a code like below

.WorkflowProcessHelper.isRelatedChildrenInStates(

primaryBusinessObject,
new String[]{"RESOLVED"})) {
result = "Resolved";
}

So what if there are multiple ECN where few are resolved and few are cancelled and how to make sure that ECR is resolved even if one ECN is Resolved. Can we modify the code? If yes can someone provide their leads here?

General Customization

Best answer by aacciano3

I believe everything can be found in here:

https://www.ptc.com/en/support/article/CS294111

http://support.ptc.com/help/windchill/wnc/r11.1_m020/whc_en/index.html#page/Windchill_Help_Center/WCCG_BusLogicCust_ChangeMgmt_Closure_Procedure.html

A

aachanta

Author

15-Moonstone

any leads on this case please?

R

RandyJones

20-Turquoise

One way is to use WorkflowProcessHelper to set the resolution date and to use LifeCycleHelper to set the state:

WTChangeRequest2 ecr = <TheECRInQuestion>;
WorkflowProcessHelper.setResolutionDate(ecr);
LifeCycleHelper.service.setLifeCycleState(ecr, State.toState("RESOLVED"));

A

aachanta

Author

15-Moonstone

Hi Jones

Thanks for letting me know.

I checked the workflow and see within the synch on change notice completion expression the below code is already there

if(com.ptc.windchill.pdmlink.change.server.impl.WorkflowProcessHelper.isRelatedChildrenInStates((wt.lifecycle.LifeCycleManaged)primaryBusinessObject, new String[]{"RESOLVED"})) {
result = "Resolved";
} else if(com.ptc.windchill.pdmlink.change.server.impl.WorkflowProcessHelper.isRelatedChildrenInStates((wt.lifecycle.LifeCycleManaged)primaryBusinessObject, new String[]{"CANCELLED"})) {
result = "Cancelled";
}

Post that there is also another expression robot in the workflow where it sets the change request to resolved and sets the resolution date

com.ptc.windchill.pdmlink.change.server.impl.WorkflowProcessHelper.setResolutionDate((wt.change2.VersionableChangeItem)primaryBusinessObject);

The same for Cancelled Routing as well. I attached a screenshot of the same. My request would be if we can change the synch on change notice completion expression itself so that regardless of how many ECN's that are present for the ECR, even if one ECN gets resolved it should be choosing the resolved routing option and not a Cancelled Routing and also it should not be stuck waiting for manual execution of that sync expression.

So can we modify the synch on the Change notice completion expression so that the workflow chooses a resolved routing and does not get stuck up when there are both resolved and canceled change notices.

Best Regards,

Aditya

A

aacciano3