Question
Bluerose Technology
IN
Last activity: 2 Jun 2023 7:37 EDT
pxAddMessageToProperty Does not work to set error message on current page in a Loop
If you want to display an error message on Property when you are in a loop, pxAddMessageToProeprty doesn't work as it takes the Primary page by default inside of the function.
PublicAPI tools = null; PRThread thisThread = (PRThread)ThreadContainer.get();
if (thisThread != null) { tools = thisThread.getPublicAPI(); } if (tools == null) { throw new com.pega.pegarules.pub.PRRuntimeError("Can't get a PublicAPI reference."); }
ClipboardPage primaryPage = tools.getPrimaryPage(); return primaryPage.addMessage(aMsgDescr, aReference);
We can use pxAddMessageToProperty activity which will execute under the current page context.
String pRef = tools.getParameterPage().getString("PropertyReference"); String msg = tools.getParameterPage().getString("MessageName");
ClipboardProperty targetProp = myStepPage.getProperty(pRef); if (targetProp != null) { targetProp.addMessage(msg); }
Ex:
Updated: 9 Jan 2023 11:31 EST
JPMC
IN
@SureshP16655111 Can you try calling this ootb activity pxAddMessageToProperty and see if this helps.
Bluerose Technology
IN
@BhanuPrakash_G , Using activity has resolved my issue
Updated: 9 Jan 2023 11:49 EST
Pegasystems Inc.
GB
@SureshP16655111 I am unable to follow the issue that you are reporting in this post.
Are you sharing a solution for an issue you encountered? If so could you detail the scenario with details of errors and documented steps that are already availlable?
Which documentation are you following?
Are you Testing an activity in context? Setting the context of a data page?
Did you check existing forum questions such as Set message to clipboard property using data transform and In a series of validation rules on same context, how to know whether a certain validation has set messages?
Please can you clarify: do you believe you have found a reproducible product issue?
If so, could I ask that you log a Support incident for this, and provide the INC reference here so that we can help track it?
Bluerose Technology
IN
@MarijeSchillern , I'm not reporting the issue. I would like to call out the difference between using the function and the activity to set error message on property.
Updated: 12 Jan 2023 5:56 EST
Pegasystems Inc.
GB
@SureshP16655111 thanks for clarifying.
As forum moderators we try to make sure that our PSC content is clear and self-explanatory.
I'd like to therefore ask that you update the content to clearly define the purpose and audience for this Developer Knowledge Share.
Characteristics of an effective Developer Knowledge Share are:
• Targeted. Each entry should be about one topic and should have a clear and descriptive title.
• User-focused. Write about what your specific audiences ask for and may need help with.
• Well-written. adopt a friendly, conversational style to make it easier for customers to digest information.
• Structured. Your article should have a clear beginning, middle, and end.
• Illustrative. Whenever you can add your real-life example, graphics.
• Comprehensive. Include all critical information as well as nice-to-knows that will make things easier for our users.
• Discoverable. Use the right keywords and tags so users can easily discover your discussion.
• Interactive. Give users the opportunity to provide feedback, for example by asking them at the end of the discussion.
@SureshP16655111 thanks for clarifying.
As forum moderators we try to make sure that our PSC content is clear and self-explanatory.
I'd like to therefore ask that you update the content to clearly define the purpose and audience for this Developer Knowledge Share.
Characteristics of an effective Developer Knowledge Share are:
• Targeted. Each entry should be about one topic and should have a clear and descriptive title.
• User-focused. Write about what your specific audiences ask for and may need help with.
• Well-written. adopt a friendly, conversational style to make it easier for customers to digest information.
• Structured. Your article should have a clear beginning, middle, and end.
• Illustrative. Whenever you can add your real-life example, graphics.
• Comprehensive. Include all critical information as well as nice-to-knows that will make things easier for our users.
• Discoverable. Use the right keywords and tags so users can easily discover your discussion.
• Interactive. Give users the opportunity to provide feedback, for example by asking them at the end of the discussion.
As an example please see discussion Set message to clipboard property using datatransform.
Many thanks for providing your input and your examples on the forum - it is very much appreciated!