Question

1
Replies
24
Views
Close popover
Wilhelm Mauch (WilhelmM)
unymira USU GmbH
Senior Consultant
unymira USU GmbH
DE
WilhelmM Member since 2016 9 posts
unymira USU GmbH
Posted: January 25, 2019
Last activity: January 26, 2019
Closed

Wrong compare operator by numeric based SecurityClearance in the accademy course example

In the accademy course CUSTOMIZING SECURITY REQUIREMENTS IN PEGA APPLICATIONS there is the following explanation in how to verify a numeric based security clearance.

----

The attributes are represented as a numerical data type. The attribute values must be mapped to a top-level numeric property on both the object (case) and the subject (operator). For example, using the Top Secret, Secret, and Unclassifiedattributes, you can create the following mapping and condition:

Top Secret=1

Secret=2

Unclassified=3

Use a single condition with a numerical comparison to determine the access level:

Operator.SecurityClearance >= .SecurityClearance

----

The grather operator used here is wrong, as it wouldn't make any sense. Please adjust it in the course content to the follwing.

Right: Operator.SecurityClearance <= .SecurityClearance

Pega Academy
Moderation Team has archived post,
Close popover 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.