...
Tester | Use |
|---|---|
IntegerEQTester | Converts attribute and test value to ints. Attribute must be EQ to the test value. In the event of a NumberFormatException, the test fails (true for all Integer testers.) |
IntegerGETester | Attribute must be GE test value. |
IntegerGTTester | Attribute must be GT test value. |
IntegerLETester | Attribute must be LE test value. |
IntegerLTTester | Attribute must be LT test value. |
RegexTester | Attribute must match a regular expression. Do not include the delimiter. |
StringEqualsIgnoreCaseTester | String comparison ignoring case. |
StringEqualsTester | String comparison. |
ValueExistsTester | True if the attribute has any non-blank value. |
ValueMissingTester | True if the attribute is null or none of its values equals the specified value. |
| AdHocGroupTester (uPortal 4.3+) | Attribute should be either 'group-member' or 'not-group-member'. Value should be the group name as expected by GroupService.searchForGroups. |
...
Recursive Testing. If one PAGS group (the child group) belongs to another PAGS group (the parent group), then an IPerson member of the child group must also pass the test(s) required for membership in the parent group. This is a more restrictive contract than the group system in general requires, where membership in a group only means that some relationship exists between a group and its members. Here, when an entity group member belongs to a group, it means that the underlying entity has some specific attribute value(s). The PAGS enforces this by testing the entity for membership in all its parent groups, which means you can nest the testing of entity members. For example, assume a group named named "employees" requires status equal to "employed" and a group named "seniors" requires age GE 65. If "seniors" is a member of "employees", then any IPerson member of "seniors" is required to have both age GE 65 and status equal to "employed".
uPortal 4.3 Custom Groups
With uPortal 4.3 there is a new feature Custom Groups where you can define a group using the Admin UI which is a list of all groups a user must be a member of and any group the member must not be a member of. The UI creates a group using the AdHocGroupTester and stores it in the database. For example:
| Info | ||
|---|---|---|
| ||
Additional References
|
...