2780
Points
Questions
7
Answers
147
-
- 3376 views
- 11 answers
- 0 votes
-
Yes I agree that it should be a PRE operation but it seems that in your code you are not updating the change so it should not be a problem.
I mean, when you have the exception, you should see the line of your code where the exception “CO has been modified. Please cancel this action, refresh the page and try again.” is triggered. Do you have that information in your logs? in this way we can check together the single operation that you are doing on a change if can be reverted.
I suppose that the eco.logAction(“SOMETHING“); is the problem because it could modify something of the change (History for example) and this generates the error. Could you please try removing or commenting the remaining eco.logAction ? (there are 2 left)
This answer accepted by Divakar. on November 22, 2024 Earned 15 points.
- 3376 views
- 11 answers
- 0 votes
-
- 3376 views
- 11 answers
- 0 votes
-
- 3376 views
- 11 answers
- 0 votes
-
Hi Divakar,
THis happens when you try to update something on a change while the Change Status is not completed at all (Agile is updating the change too).
It means that the Event Subscriber is set as PRE event (so while the change status is in process).
If you set it at POST event, Agile completed its update on the change and your PX can proceed setting other info on it.- 3376 views
- 11 answers
- 0 votes
-
- 3376 views
- 11 answers
- 0 votes
-
- 3362 views
- 7 answers
- 0 votes
-
Hi,
As explained here the Some matching criteria should be correct in your case.
Also your expectation should vbe correct looking the criteria. Could you please add an example of Change Number that you are using that should match the “start with” condition?
I had bad issues with Start With in a Criteria because sometimes this condition was always false even though it was satisfied. There are a couple of bugs in OTN about that.
Try to use another Criteria for testing (for example: equal to ‘exactnumber’) to check that you are not affected by this issue.- 1500 views
- 5 answers
- 0 votes
-
Hi
The error message is typical of a Class Not Found Exception.
This happens when the jar used as third party dependency is not in your classpath or lib folder (to don’t confuse with Process Extensions folder).From https://blogs.oracle.com/jiechen/entry/into_agile_sdk_class_loader
<<The class is the type of dynamic class loading during JVM runtime, not at JVM initialization with specified classpath, so it will not be referenced by px.ClassManager automatically because px.ClassManager uses a customized URLClassLoader to load specified class ( just META-INF/ICustomAction or IEventAction files) and references.
That is to say, the newly loaded class1.class only be referenced during runtime on demand, not by URLClassLoader. In this case, there is no such class1.class mapping in jvm class stack. So you will see ClassNotFoundException.>>To overcome this, the to be loaded class “HTTPEntity” should be added to App Server’s shared library.
Please refer to that guide to deploy a third party library section 3.9 to deploy a class using Weblogic (or OAS if it is an old version)
http://docs.oracle.com/cd/E50306_27/otn/pdf/integration/html_agaaq/output/chapter_3.htm- 1698 views
- 1 answers
- 0 votes
-
Hi Anand,
Another solution could be set the Template field to Proposed when the task has to be put on Hold.
This makes the task scheduling modifiable but avoid to modify its workflow status.
Once you activate the tasklist (from proposed to Active) you can capture that in an Event PX and set the dates as you wish.
It should works but I have never tried it before. (PPM Module is magic sometime 🙂 )- 2289 views
- 2 answers
- 0 votes