Hi, Can you please post the code of the ChangeApproveForWorkFlowEventPx PX?
At least the returned Action Result.
The object ActionResult returned seems to not be configured properly.

Sorry I though the opposite.
If you call addChild, you are not pointing on the just added element but on the list itself. So the setObsolete is called on the list itself in your code (and therefore doesn’t work)
For that it is quite easy. When you call list.addChild(“Neptune”) the API returns the just added value (an IAgileList …). So you have to call setObsolete on this new one and not on the original list.

Example:
IAgileList neptune = (IAgileList) listchildren.addChild(“Neptune”)
neptune.setObsolete(true);

If any question you can check the sdk docs where this is explained quite well:
https://docs.oracle.com/cd/E17287_04/otn/pdf/integration/E17315_01.pdf

You can Interact with the agile list properties only wrapping it as AdminList:
IAdminList adminList = list.getAdminList();
adminList.enable(false);

the setObsolete is valid only if you try to inactivate a single list entry (the same interface) like “Pluto” and cannot be used to the entire list

For whom is interested on that topic, I received an answer from Oracle, saying that this cannot be done  in 9.3..4,5, and 6 version.
There is an enhancement request created on November but it is still under review:

https://support.oracle.com/epmos/faces/BugDisplay?_afrLoop=384097139108488&parent=SrDetailText&sourceId=3-16854990161&id=27117283&_afrWindowMode=0&_adf.ctrl-state=bheanacd5_21

So probably it is not possible to set HTML as Default Value for Large Text using official ways 🙂

The sort order can be modified by the Personalize view. In the first tab of the displayed dialog when you click Personalize, there is the sort criteria (till 3 fields configurable).
Once applied, you can save as the base view to something new but you cannot override the Base View.
Once saved this personalized view as global, all users can select it by default for all Items. It is not possible to assign automatically to all users but each of them has to select it as default.

Could you please send more details on that? Like the stack trace of the error displayed in the log and what is not loaded in the web client

Thanks

probably a stupid answer
Is the AutoVue windows service up and running before run the Filemgr?

As mentioned by Steve, the Invalid Parameter error could be related to the set of a Role.
Try to set the list with an array of IRole objects instead of Strings

INode nodeRoles = (INode)m_session.getAdminInstance().getNode(NodeConstants.NODE_ROLES);
IRole role1 = (IRole)nodeRoles.getChildNode(“PPM Task Owner”);

Hi,
Is there any custom JAva or Groovy PX that runs during the release of the ECO/MCO? I see in the stacktrace this kind of “Mass Update – Change Objects” that seems not to be an Agile one.
In case please share the code or have a look at it in order to check if there is any issue.

Hi,

This warning has been added since JAVA 8.
http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html

Area: HotSpot / gc 

Synopsis

The command line flags PermSize and MaxPermSize have been removed and are ignored. If used on the command line a warning will be emitted for each.

Java HotSpot(TM) Server VM warning: ignoring option PermSize=32m; support 
was removed in 8.0

Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=128m; support 
was removed in 8.0

Nature of Incompatibility

source

RFE

6965548

This because the Perm Generation doesn’t exist anymore in Java 8.

So the warning is not related to your -Xmx=512M (Heap Size) param  but to the param -MaxPermSize=512M, which is related to the PermSize