Page History

...

• Load groups as members
• Add incremental job
• Unit tests
• Better validation
• More methods to call (other than hasMember)
• Add subject attributes e.g. from global attribute resolver
• Failsafes
• Add delegated admin based on READ of groups
• Visualization
• Add more counts of total memberships etc
• See if comments can be included in scripts
• See if we can replace composite type with immediate in membership table if replacing a composite with jexl script
• Have a confirm screen that tells the user information about what will happen (tie into visualization)? (have a progress page)
• Add UI to configure scripts?
• Test button while writing to see if valid (maybe that does counts too)
• Add dependency graph for precedence or recalcs in full sync
• Do not allow circular references
• Identify full syncs to be hourly or daily

Entity attribute resolver groups

This is for a future release

The high level strategy is you need two database tables, a table of people and a table of one-to-many records about those people.  This will be configured in your global entity attribute resolver.  abac jexl scripted groups would be able to use those similar to this

my_people_table
employee_id (same as subject id or identifier)  email
123                                             a@b.c
234                                             b@c.d
my_people_affiliation
employee_id    affiliation_name   dept
123            staff              english
123            student            history
234            guest              chemistry
entity.attributeRecordFilter('myPeople', 'affiliation', "(affiliation_name == 'staff' || affiliation_name == 'student') && dept == 'english'")

The first argument "myPeople" identifies the entity resolver
The second argument "affiliation" identifies a one-to-many relationship on the main entity resolver table which is another table
The third argument is a filter on that one-to-many table for those people
This means find people where the affiliation has a name of staff or student and that affiliation is in dept english.   The format of the filter would not be a well defined subset of jexl...  thoughts?  Image AddedNote: this is a little weird since there is a JEXL script embedded in the JEXL script...  but we can document it and see how it goes? 

Entity resolver change log or last updated col could be used on incremental

Parse expression with JEXL (for Grouper developers)

...