CUS602 - Committee Segmentation

As of 7.5.1, this new batch process is used to handle committee segmentation. In the past, committees, corporate relationships, etc. were combined into a single batch process, CUS600, and there was no way to run the process for just one of those groups. By splitting the groups into separate batch process, you can choose a different time to run the batch process for each group. In addition, the purpose of these batch jobs are to maintain who is in each group.

For example, a staff member at APA has just entered a new committee record, along with 20 new committee member records. Ideally, he/she should have created the committee and then created the committee as a web segment, before creating the individual committee records, but since he/she did not, the CUS602 batch process will need to be ran in order to create the individuals as members of the committee’s web segment.  

When determining when to schedule this batch process, some items you should take into consideration include the following:

·            Creating:
After you first create a segment for an EXISTING committee, company, or subgroup, you want to run this process to establish who is already part of the group.

·            Adding:
Personify has triggers in place that pick up most new committee members and employees; however, segment members are NOT automatically added to a group. First, the MBR700 process needs to be run to find all the new orders for the particular membership (e.g., a chapter), then the CUS603 process needs to be run to put those chapter members into a group that can be managed online.

·            Removing:
Usually, a constituent's involvement in a group is time-based and there is no trigger that the system can use to remove someone from the group (i.e., a record is added, updated, or deleted). When a particular date is reached, such as the end date for a committee member’s position, an employment relationship, or a chapter membership, there is no change in the database that tells the system to react. Therefore, a batch process is provided that searches for group member(s) to remove. To figure out a schedule on when to run the batch process, consider your organization's turnover for individuals belonging to a committee. Ask yourself the following questions and based on your answers, is how often you should schedule the batch process:

o           Do positions end at the same time, or is it common for each person’s involvement to end at different points during the year? The more consistent the service period is, the less frequent the CUS602 batch process needs to be run. For instance, if your organization has annual elections and it is rare for someone to step down mid-year, then this batch process may be run only once a year after elections.

o           If turnover is frequent, then the batch process should be run as frequently as the group manager will need to access the committee members. For example, if outreach to the committee members occurs quarterly, then CUS602 should be run at least once a quarter. If a committee meets monthly, then CUS602 should be run at least once a month, so the group manager is always working with a current roster.

Parameters