Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Anand Yalla (ANANDYALLA)
Rbc

Rbc
CA
ANANDYALLA Member since 2010 1 post
Rbc
Posted: Apr 8, 2019
Last activity: Jul 15, 2019
Posted: 8 Apr 2019 13:38 EDT
Last activity: 15 Jul 2019 15:56 EDT
Closed

Using queue method - severe guardrail warning

We have activity and have step which calling Queue method (not queue-for-agent) with another activity to run in asynchronously (please find the attached screenshots). One thing we are considering to convert this to queue-for-agent but need lot of testing.

Just started upgrading the application from V7.1.5 to V7.4 and started seeing following new severe warning. I would be grateful if anyone see similar issue and solution.

Guardrail wanring - Functionality: Severe

When using the Queue instruction, the queued activity will not be run on the primary or step page specified. Check the Help documentation for more information.

To see attachments, please log in.
Pega Platform
Updates

Posted: 5 years ago
Posted: 15 Jul 2019 15:56 EDT
Ron Cohen (coher) Client Support Engineer Senior Fellow
PEG
US

This warning is a very useful one, because it is quite unusual for there to be no step or primary page when the activity fires.  This can lead to a difficult to debug issue if your calling activity is relying on there being a step page or primary page.  As the warning says, THERE WILL BE NONE.

You can add a "justification" for the warning, and I believe the score will not be added to your total guardrail score.

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice