Page History

...

• COU: The Expiration Policy will only apply to the specified COU. If no COU is specified, the Expiration Policy applies to the entire CO.
• Affiliation: The Expiration Policy will only apply to CO Person Roles with the specified affiliation. If no affiliation is specified, the Expiration Policy applies to all CO Person Roles.
• Days Before Expiration: The Expiration Policy will apply the specified number of days before the Valid Through date of a CO Person Role. For example, if a CO Person Role has a valid through date of June 30, and Days Before Expiration is set to 3, then the Expiration Policy will be considered in effect beginning June 27. When used in conjunction with a Notification action and nightly automated processing, this will generate nightly expiration warnings for 3 nights prior to expiration. (To have an Expiration Policy apply only once when using this condition, set an Action that will change the Affiliation, COU, or Status so that the Expiration Policy no longer matches. Or use Max Execution Count.)
• Days After Expiration: The Expiration Policy will apply the specified number of days after the Valid Through date of a CO Person Role. For example, if a CO Person Role has a valid through date of July 1, and Days After Expiration is set to 7, then the Expiration Policy will be considered in effect beginning July 8. When used in conjunction with a Status action and nightly automated processing, this will implement a week long grace period (but see more, below).
• Max Execution Count: The Expiration Policy will apply no more than the specified number of times. The count will reset when expiration related CO Person Role attributes (eg: status, valid through, affiliation, COU, sponsor) are changed. Available since Registry v1.1.0.
• Status: The Expiration Policy will only apply to CO Person Roles with the specified status. If no status is specified, the Expiration Policy applies to all CO Person Roles.
• Invalid Sponsor: If set, the Expiration Policy will apply to CO Person Roles attached to a sponsor (CO Person) that is no longer in Active status.
  
  

...

1. The Registry cron job has been installed.
   1. As of Registry v4.0.0, expirations are processed via the Core Job Plugin Expire job.
2. Expiration is not disabled. To disable expiration, edit the CO Settings (Collaborations >> CO >> CO Settings) and check Disable Expiration.
3. Only Expiration Policies with status Active will be executed.

...