IMS Role Configuration

The roles will be configured for IMS using this module. This module provides various parameters. The Windows service will execute the script for the roles per the parameters defined.

The roles can be set up with three options:

· Data Refresh – If selected, the customer role assignment table is repopulated when the role is executed. The existing data for role assignment is truncated and the table is refreshed with the selected records by the script defined for the role.

· Inclusion – The inclusion script should be set up to add new customers that match the role criteria. If selected, the script selects the records that match the criteria and that are newly added from the last execution to the Personify database. The records will be appended to the existing table.

· Exclusion – The exclusion script should be set up to revoke the role assignments for the existing customers. If setup, the customer records that match the criteria are deleted.

The Control File is:
DesktopModules/IMSModules/TMAR.IMSInterfaceWebParts/RoleConfiguration.ascx

Once a customer has created their account, it may take a few minutes for the new account to be activated.

Base IMS Roles

The following IMS Roles are delivered with Base Personify in 7.4.1:

Role	Logic
Committee Member	This role applies to individuals only. A customer is a current committee member if a record exists in Com_Committee_Member where MEMBER_MAST_CUST = MASTER_CUSTOMER_ID of the customer and MEMBER_SUB_CUST = SUB_CUSTOMER_ID of the customer and Com_Committee_Member.PARTICIPATION_STATUS_CODE = ‘ACTIVE’ and Com_Committee_Member.BEGIN_DATE <= current date and (Com_Committee_Member.END_DATE is null or Com_Committee_Member.END_DATE >= current date). Committees and committee memberships are owned by the Org Unit. Full data refresh will be set in base to run every week; you can change this schedule, if desired, to meet your business needs. This data refresh looks for a constituent's involvement in ANY committee and gives the icon if they have any active positions. Inclusion data refresh will be set in base to run every minute; you can change this schedule, if desired. As committee members are added, within a minute, they will have the committee icon. Exclusion data refresh is not included for committees. The full data refresh will pick up these edits. If you have some committees that need to refresh more often, or have their own icon, you can create a separate IMS rule to track these, and establish a more aggressive schedule for those.
Member	The logic for Membership will be based on what is in the Latest Interactions section in CRM360 and will reference data saved statically for that section.
Expired Member	This applies to a member whose fulfill status for the primary membership is Expired and no renewal exists. The logic for Expired Member is based on what is in the Latest Interactions section in CRM360 which will reference data saved statically for that section. Order_Detail.FULFILL_STATUS_CODE is ‘E’ and Order_Detail.RENEWAL_DATE_NEXT_ORDER is null.
Grace Member	This applies to a member whose primary membership is in Grace.
Volunteer	The system currently displays a Volunteer icon if the constituent is an active volunteer. TMAR continues to use this icon as the volunteer badge, but will discontinue showing it automatically on the screen. Rather, if you choose to implement a volunteer badge as part of constituent roles and attributes, it will be displayed. The logic for identifying a constituent as an active volunteer is where Cus_Volunteer.VOLUNTEER_STATUS_CODE = ‘ACTIVE’. Note that volunteers belong to an org unit.
Staff	The staff role displays a Staff icon if the individual is an active staff member.

Be conscious of the volume of data that you have and how often it changes. The IMS process will take time and resources, so you should be conservative when setting up new roles and/or scheduling these jobs. For instance if Membership only changes once per year in general, then perhaps that icon does not need to be refreshed as often as the other data. The number of jobs and the volume of data analyzed will factor into performance.

IMS Icon Setup

As of 7.4.1, the basic components of this feature are:

· Display of Role icons and/or text within each constituent's header in CRM360

· Access to the IMS Role Definition screen within Personify

· New UI to manage the Personify-specific Role setups: icons, text, and/or related command

· Inclusion of Role data in Data Analyzer Universes for reporting (for more information, please see Identity Management Roles Universe.

Personify will be delivered with all icons deactivated. It is your responsibility to validate the logic to fit your business needs and activate the desired icons.

IMS icons can be assigned by Org and Org Unit. Each may track different attributes of the same constituent, and may not wish to be confused by IMS icons extraneous to them, and in some cases may not wish to share sensitive IMS icons with other Org Units. The constituent IMS icons feature is only available for Individual and Company records (not Committees or Subgroups). If you have more than one Org/Org Unit and wish to have different icons for each (e.g. a different committee icon for a foundation), you can create a new IMS setup for each, and in the 'where' clause, identify which applies to each Org Unit.

If you are setting up logic for an IMS icon code, start with a master table, typically CUSTOMER. Within the body of the Criteria text box, you can define joins to other tables. A good starting point may be to look at the badges and ribbons you provide to Annual Meeting and Expo attendees. This logic can be re-created in IMS if these are important distinctions for your organization. Additionally, if you wish for some CRC (Constituent Role Code) values to be displayed in the header, e.g. VIP or Troop Leader, then they can create IMS Roles for each.

As of 7.4.1, IMS uses Windows services to pick up all active icons by running the logic defined in the DNN interface against the customer database and populate an IMS database outside of Personify. Users have control over the logic and scheduling of these updates. Some of the advantages to using the new IMS system are:

· Users already using this solution can present critical Icon details in Personify

· Users can leverage the same code for online and back-office purposes (less need to synchronize logic such as who qualifies for 'VIP')

· Users that become familiar with IMS roles can start to leverage them to tailer to their constituents' online experience (which pages and modules they can access)

· Users with basic SQL knowledge can define a client's list of IMS icons and how to populate them

· IMS system includes options to populate data en masse, just add where changes are detected, and remove records that no longer apply-and to check logic in advance

· IMS is in a distinct database so processing will not conflict with Personify operations