Qualifying the "Call contains an optional key part AppliesTo..." warnings
The warning "Call contains an optional key part AppliesTo..." is helpful for prevening bad coding. It just needs to be qualified in more use cases. (Maybe this has been addressed since v6.2?)
One circumstance I had pointed out in 2010 -- when you need to make a "static" call. This should not even pass the current step page; that might even help avoid coding errors.
Another situation is where you need to make a call to a super-class activity -- in that case, the warning.
Maybe there should be ("StaticCall", "SuperCall") which would bypass the warnings.
Of course, it's possible to simply justify these warnings as a response. But the best approach is to avoid the warnings by recognizing the situations where they are unnecessary.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Keep up to date on this post and subscribe to comments
- Can we increase the size of the parameters input field on a step with a "call activity"
- Getting "Call failed to complete. Do you wish to hang up?" pop up
- Getting "com.pega.pegarules.pub.PRException: Exception occurred while mapping incoming response to.response_POST.parts " while calling REST service
- "Send DTMF" call option can not be disabled/Removed
- How do you create a qualifier that will add a "%" symbol after the input, like pyCurrency does?