Question

6
Replies
290
Views
Samuel Fox (SamuelF7)
Auto-Owners Insurance

Auto-Owners Insurance
US
SamuelF7 Member since 2013 4 posts
Auto-Owners Insurance
Posted: July 8, 2015
Last activity: July 21, 2017
Posted: 8 Jul 2015 8:26 EDT
Last activity: 21 Jul 2017 10:05 EDT
Closed
Solved

Can you fully qualify Function Aliases?

I created a series of activities to validate various rules on "Save" for functions containing a RuleSet and Library (e.g. @PageExistsWithClass(1,2) should now be @(Pega-RULES:Page).PageExistsWithClass(1,2)). This has, however, caused me to encounter a some issues that are impeding progress going forward.

Function aliases such as @if and @and cannot be fully qualified.
1a. Can we fully qualify function aliases?
1b. If function aliases cannot be fully qualified, how could we dynamically exclude all of these so that they will never appear in the warning message upon validation (without having to hard code each of these individually)?

***Updated by moderator: Lochan to close 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.

Low-Code App Development Case Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.