Grouper Users - Open Discussion List

["Crawford, Jeffrey" <>]

Hey,

 

This appears to have worked now, does this rule run on a schedule? I was in the middle of testing and had to walk away, and when I came back the dependent group had the record removed. Perhaps I was confused since the veto one was right away.

 

Thanks

Jeffrey C.

 

From: <> on behalf of "Crawford, Jeffrey" <>
Reply-To: "Crawford, Jeffrey" <>
Date: Tuesday, April 16, 2019 at 8:22 AM
To: Grouper Users <>
Subject: Re: [grouper-users] Problem with Composite-org intersection

 

Bump 😊

 

From: <> on behalf of "Crawford, Jeffrey" <>
Reply-To: "Crawford, Jeffrey" <>
Date: Monday, April 15, 2019 at 8:35 AM
To: Grouper Users <>
Subject: Re: [grouper-users] Problem with Composite-org intersection

 

Just as a follow up. I can’t seem to get “RuleApi.groupIntersection” to work either, however the corresponding veto rules seems to work just fine!

 

Jeffrey C.

 

From: <> on behalf of "Crawford, Jeffrey" <>
Reply-To: "Crawford, Jeffrey" <>
Date: Friday, April 12, 2019 at 10:44 PM
To: Grouper Users <>
Subject: [grouper-users] Problem with Composite-org intersection

 

Hello,

 

I’m sure I’ve gotten this to work before, but now I seem to be having some issues Here is the result of my last test:

addStem("training:app:auto2:etc", "eligibility", "eligibility");

addGroup("training:app:auto2:etc:eligibility", "population", "population");

eligibility = StemFinder.findByName(grouperSession, "training:app:auto2:etc:eligibility");

subjectActAs = SubjectFinder.findByIdAndSource("GrouperSystem", "g:isa", true);

addGroup("training:app:auto2:org:level1:roles", "role1", "Role 1");

group = GroupFinder.findByName(grouperSession, "training:app:auto2:org:level1:roles:role1");

group.setDescription("First Role");

group.store();

RuleApi.groupIntersectionWithFolder(subjectActAs, group, eligibility, Stem.Scope.SUB);

 

Then I execute the following:

groovy:000> addMember("training:app:auto2:etc:eligibility:population", "urn:mace:ucla.edu:ppid:person:EC1C794C8A424A18A34A5E73F78A2DDF");

===> true

groovy:000> addMember("training:app:auto2:org:level1:roles:role1", "urn:mace:ucla.edu:ppid:person:EC1C794C8A424A18A34A5E73F78A2DDF");

===> true

groovy:000> delMember("training:app:auto2:etc:eligibility:population", "urn:mace:ucla.edu:ppid:person:EC1C794C8A424A18A34A5E73F78A2DDF");

===> true

groovy:000> hasMember("training:app:auto2:org:level1:roles:role1", "urn:mace:ucla.edu:ppid:person:EC1C794C8A424A18A34A5E73F78A2DDF");

===> true

 

That last one should be false right? The following is my install:

Grouper starting up: version: 2.4.0, build date: null, env: <no label configured>

grouperPatchStatus read from: /opt/grpr/grouper.apiBinary/grouperPatchStatus.properties

api patches installed:        0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26

pspng patches installed:      0, 1, 2

 

 

Is this a bug or did I do something wrong?

 

Thanks

Jeffrey C.