Question
Atos Syntel
IN
Last activity: 5 Sep 2025 3:02 EDT
How to utilize message field value from Activity-Set-Status Method
In Activity-Set-Status there is a field called Message, where is this Message value getting written/saved ?
I have a requirement: there are two Activities A and B, Activity A calls Activity B, Inside Activity B i am using Activity-Set-Status method and setting a Message, is it possible for Activity A to obtain this Message ?
Accepted Solution
Updated: 5 Sep 2025 3:02 EDT
HCA Healthcare
US
ai4process ltd
GB
Use a Parameter to set the value of the Message for Activity-Set-Status and when calling Activity B from A, check the checkbox- Pass current Parameter page.
this should pass the parameters and achieve your goal of returning the message from Activity B to Activity A
Capgemini
NO
@DilipanV105 Use @pxGetPageMessages() to fetch messages from your primary page. If you want to fetch messages from a different page, use @pxGetPageMessages(PAGENAME) instead.
Accepted Solution
Updated: 5 Sep 2025 3:02 EDT
HCA Healthcare
US
The message value you set in the Activity-Set-Status method is not stored on a clipboard page or database table by default. It is only added to the pxMethodStatus property on the primary page context of the activity that executes the method. This is why you don’t see it directly available elsewhere. If Activity A calls Activity B, then once Activity B finishes, Activity A can check the status using tools.getStatusMessages() or by looking into pxMethodStatus to retrieve the message. Another option is to explicitly copy the message into a parameter or property inside Activity B before ending it, so that Activity A can easily read it after the call. This approach is cleaner because relying on pxMethodStatus is less predictable when multiple methods are executed. So, the best practice is to map the message from Activity B into a property or parameter and then pass it back to Activity A for use
@DilipanV105
The message value you set in the Activity-Set-Status method is not stored on a clipboard page or database table by default. It is only added to the pxMethodStatus property on the primary page context of the activity that executes the method. This is why you don’t see it directly available elsewhere. If Activity A calls Activity B, then once Activity B finishes, Activity A can check the status using tools.getStatusMessages() or by looking into pxMethodStatus to retrieve the message. Another option is to explicitly copy the message into a parameter or property inside Activity B before ending it, so that Activity A can easily read it after the call. This approach is cleaner because relying on pxMethodStatus is less predictable when multiple methods are executed. So, the best practice is to map the message from Activity B into a property or parameter and then pass it back to Activity A for use