Question
BMO
US
Last activity: 1 Dec 2025 10:45 EST
Where can I view documentation for pega's java functions?
Hello,
In step 9 of the pega activity named 'OpenAndLockWork' (CL: Assign- RS: Pega-ProcessEngine:08-08-01), I found the following java line: pega_procom_pegaprocomutilities.populateFlowActions(assignPage, myStepPage, tools).
I want to know if there is a website/documentation page where I can view which methods are called inside of populateFlowActions.
Some further context:
I understand that in a pega application, when a flow is entering an assignment, the newAssignPage page is created and added to the clipboard to temporarily hold the assignment properties. It looks like most of the properties on newAssignPage are populated from a query to the pegadata.pc_assign_worklist database table. Further into the execution of opening an assignment, there are additional properties that are populated on the newAssignPage. I pasted the properties below:
.pyDefaultActionIndex
.pyDefaultTaskStatus
.pyDefaultTaskHTML
.pyDefaultTaskValue
.pyDefaultTaskInstructions
.pyDefaultTaskInstructionsCaption
.pyDefaultTaskNextAssignment
I'm trying to find exactly when/where are these properties added onto newAssignPage. I traced a session where the user simply clicks on an assignment, and I found that these properties are added to newAssignPage on step 9 of OpenAndLockWork activity. I suspect that populateFlowActions method eventually calls the following pega function:
ID: FlowUtilities * pxSetDefaultFlowAction
Hello,
In step 9 of the pega activity named 'OpenAndLockWork' (CL: Assign- RS: Pega-ProcessEngine:08-08-01), I found the following java line: pega_procom_pegaprocomutilities.populateFlowActions(assignPage, myStepPage, tools).
I want to know if there is a website/documentation page where I can view which methods are called inside of populateFlowActions.
Some further context:
I understand that in a pega application, when a flow is entering an assignment, the newAssignPage page is created and added to the clipboard to temporarily hold the assignment properties. It looks like most of the properties on newAssignPage are populated from a query to the pegadata.pc_assign_worklist database table. Further into the execution of opening an assignment, there are additional properties that are populated on the newAssignPage. I pasted the properties below:
.pyDefaultActionIndex
.pyDefaultTaskStatus
.pyDefaultTaskHTML
.pyDefaultTaskValue
.pyDefaultTaskInstructions
.pyDefaultTaskInstructionsCaption
.pyDefaultTaskNextAssignment
I'm trying to find exactly when/where are these properties added onto newAssignPage. I traced a session where the user simply clicks on an assignment, and I found that these properties are added to newAssignPage on step 9 of OpenAndLockWork activity. I suspect that populateFlowActions method eventually calls the following pega function:
ID: FlowUtilities * pxSetDefaultFlowAction
RS: Pega-ProcessEngine:08-01-01
pxSetDefaultFlowAction is the only code I found that sets the properties I'm looking for onto newAssignPage. I need to see the documentation or class/method structure for populateFlowActions to confirm this.
I'm looking for something similar to this:
PublicAPI (PegaRULES Java Engine v7.4.0 - PUBLIC)
Accepted Solution
Updated: 1 Dec 2025 10:45 EST
HCA Healthcare
US
There is no public Javadoc or website that shows the internal implementation of pega_procom_pegaprocomutilities.populateFlowActions or similar engine utility classes. Pega only publishes the PublicAPI Javadocs (like the link you shared) and those cover the supported engine interfaces, not the internal helper classes used inside shipped activities. The populateFlowActions method is part of that internal layer, so you cannot see the exact list of methods it calls or the Java source from product documentation. To understand when properties like .pyDefaultTaskHTML or .pyDefaultTaskInstructions are set, the right approach is what you already did: trace OpenAndLockWork with Tracer, turn on Java and DB events, and watch the clipboard on newAssignPage. From there you can confirm that pxSetDefaultFlowAction is populating those fields, but not “open up” populateFlowActions itself. If you need more detail for a production issue, the usual advice is to raise a support ticket with Pega so GCS can confirm the internal behavior or propose a supported extension point. In general, Pega recommends relying only on the documented rules (activities, RUFs like pxSetDefaultFlowAction, data transforms, etc.) and PublicAPI, and not on undocumented Java methods, because those internals can change between releases.