[Rt-commit] rt branch, 4.4/lazy-role-groups, repushed

[Jim Brandt]

The branch 4.4/lazy-role-groups was deleted and repushed:
       was 0f51e463be032b6001bd917a4d13ade80ebb8571
       now 54b0e2a99c5aca4a404871852472531564f011dd

1: b2aa7a96f2 ! 1: d2061ce0e2 Support to create ticket/asset role groups lazily
    @@ -1,6 +1,12 @@
     Author: sunnavy <sunnavy at bestpractical.com>
     
         Support to create ticket/asset role groups lazily
    +    
    +    For objects with a large number of custom roles, creating
    +    all necessary role groups at object create time can add a
    +    large number of additional create operations in the DB,
    +    impacting performance. Creating them later when needed
    +    reduces time to create the object.
         
         Since role groups may not exist, we need to use left join in searches.
     
    @@ -13,7 +19,10 @@
      
     +=item LazyRoleGroups
     +
    -+A boolean to control if to create role groups immediately or just when necessary
    ++Boolean value that controls how role groups are created:
    ++
    ++1: create when necessary (lazy, default value)
    ++0: create immediately
     +
      =back
      
    @@ -88,7 +97,7 @@
        Due -- an ISO date describing the ticket's due date and time in GMT
        MIMEObj -- a MIME::Entity object with the content of the initial ticket request.
        CustomField-<n> -- a scalar or array of values for the customfield with the id <n>
    -+  LazyRoleGroups -- a boolean to control if to create role groups immediately or just when necessary
    ++  LazyRoleGroups -- boolean, create role groups immediately (0) or just when necessary (1, default)
      
      Ticket links can be set up during create by passing the link type as a hask key and
      the ticket id to be linked to as a value (or a URI when linking to other objects).
2: 1c9c2d1bcc = 2: 35b0c0208f Default PrincipalId to 0 to avoid SQL error for not-existing role groups
3: 0f51e463be = 3: 54b0e2a99c Update tests for the lazy role groups change