Usually if you are trying access something in ADMIN Nodes which no longer exist we get this error. You can run aVerify and fix any errors reported. That will take care of this issue.

Hope you have added the Event class name along with the package as part of the META-INF/services/com.agile.px.IEventAction file.

we cannot search on history attribute.

There is no straight forward way to achieve a parallel status. However, by using the “Manual Valid Next Status” option you can achieve this.

For example,
1. Lets us say that the first status is A.
2. It has 2 statuses as the Manual Valid Next Status – B and C.
3. Logically the User can move the object to either B or C though in the view it will look like A -> B -> C.
4. Manual Valid Next Status for B and C is D. So, when the object is in status B or C it can only go to D.

In this way you can setup parallel flows. Note that you can have a series of status instead of either B or C creating two flows from A to D.

On ECO’s Page Three enable any one of the unused List attributes and point it to a dynamic list that points to Discussions objects.

You have to create a Process Extension for the Actions Menu (Extend Actions Menu – Event Type). That way a new Menu Item will be displayed for the User.

Please check if the path /temp exists. If it is a Unix machine usually you will have /tmp and not /temp

You will need 2 User Groups instead of User Group Cust 1 each with the respective users (A in the first and B, C in the second). Then you can have 2 different roles with the required privileges. Assign the User Group to the corresponding Roles.

Can you please try the following. I removed the braces for ‘Default Change Orders.CCB Review’

query.setCriteria(“([Cover Page.Status] in ‘Default Change Orders.CCB Review’ and [Workflow.Duration] > ‘2160’)”);

Please use “(” instead of “[” and try out.