Understanding CampusNexus CRM Objects
Objects contain basic information that you require when working with CampusNexus CRM. This information can also relate to data pertaining to the business functions in the institution.
For example, the Contact object contains information about the name of the contact, the address, details about the previous education, their educational preferences, documents, interactions, and so on.
Objects are grouped as Global, Team, and Shared, depending on how the information is used in CampusNexus CRM. An object can be predefined, or user-defined.
Predefined objects are also referred to as System objects.
The following table lists the predefined objects:
| Object Type | Object |
|---|---|
| Global |
Account, Contact, and Event, are Global objects. User and Target are also Global objects, but inherit the attributes of the associated global object (account, contact, or event). |
| Team | Interaction, Campaign, and Message. |
| Shared | Canned Response, Mailer/SMS Template, Mailing List, Link, Print Template, and Script. |
Global Objects
The Global objects are Account, Contact, and Event. Special Global objects include User and Target. Global objects are not team-specific, and are available to all users regardless of their team associations. These objects are managed in Desktop Client from the relevant Workspaces.
Notes
• The Event object is available in CampusNexus CRM only if Event Management is installed.
• Though Contact is a global object, team-based security can be enabled for the Contact object. For more information about team-based security, contact Product Support.
User and Target are special global objects. Though the User object itself is not available to users, the User property, User Name, can be defined in other objects. In addition, a User property can be defined in relationships between the User object and other objects.
The Target object is an element of the Campaign object, which is a Team object. Hence, its behavior is similar to that of Team objects, rather than that of Global objects.
A Contact is a constituent. A contact may be required to interact with one or several teams in an institution. Therefore, the Contact object is classified as a Global object. Other predefined objects such as Interactions, Accounts, Campaigns, and Targets directly depend on the Contact object. A contact's transactions are not confined to a single team.
Note that a Team refers to a division or department in the institution.
A contact may also represent an institution. The Account object represents the institution to which that contact belongs. Account is a Global object. An Account representing a contact may be required to interact with several teams in the institution.
Contact and Account information are therefore available to all teams in CampusNexus CRM. However, contacts and accounts have properties that are available only for certain teams.
A User is a representative of an institution who interacts with contacts and visitors using Desktop Client.
A Target is a contact who has been selected to be part of a campaign.
In addition to these predefined Global objects, Global custom objects can be created in Business Administrator.
Team Objects
Team objects include Interactions, Campaigns, and Messages.
Team object items belong to only one team, and are available to users having access to that team. A Team object item can be assigned to users within the team in which it is created, or transferred to users outside the team. After the object item is transferred, it gets associated with the team to which it has been transferred.
Team objects are managed in Desktop Client from the relevant Workspaces. Interactions, Campaigns, Targets, and Messages are examples of predefined Team objects.
Example
A user with access to the Events team can create a Campaign in this team. Only users associated with the Events team can view or edit this campaign. These objects are also called local objects, because operations on them are confined to users associated with teams in which they are created.
In the program or event scenario, the institution builds business relationships with Accounts that are represented by contacts. Interactions result from the conversations an institution has with its contacts.
Campaigns are aimed at targets that are instances of contacts on whom the campaign is focused. At the end of a campaign, targets that express interest in an event or program are considered as leads. These leads are then serviced and followed up in an effort to convert them into enrollments.
In addition to these predefined team objects, Team custom objects can be created in Business Administrator.
Shared Objects
Shared objects include Canned Responses, Mailer/SMS Template, Mailing Lists, Links, Print Templates, and Scripts.
Shared objects can belong to multiple users across the teams with which they are shared. Changes made to a shared object by one user can be viewed by users of all teams with which the object is shared.
Canned Responses, Scripts, Mailers, Mailing Lists, Filters, Links, Print Templates, and Workspaces are examples of predefined shared objects. \
All shared objects, except Links, Print Templates, and Shared Custom Objects, are managed from the respective Manager consoles in Desktop Client.
The Link object can be managed from the Links tab in the Chat Workspace. Print Templates and shared custom objects can be managed from any Workspace.
In addition to these predefined Shared Objects, shared custom objects can be created in Business Administrator.
Higher Education Foundation Objects
If Higher Education Foundation is installed, the objects in the following table are also displayed in the Objects node in Business Administrator.
Based on their usage, these objects are categorized as Operational, Reference, and Integration objects.
| Object | Classification | Type |
|---|---|---|
| Activity | Operational | Team |
| Address Type | Reference | Global |
| Address | Operational | Global |
| Area of Interest | Reference | Global |
| Area of Study | Reference | Shared |
| Assignment Log | Integration | Global |
| Country | Reference | Global |
| Document Status | Operational | Global |
| Document Status Type | Reference | Shared |
| Education Level | Reference | Shared |
| Enrollment | Operational | Team |
| Ethnic Group | Reference | Global |
| FERPA Group | Reference | Global |
| Incoming Queue | Integration | Global |
| Lead Source | Reference | Shared |
| Lead Type | Reference | Global |
| Lead | Operational | Team |
| Nationality | Reference | Global |
| Outgoing Queue |
Integration | Global |
| Program Level | Reference | Shared |
| Program Version Start Date | Reference | Shared |
| Program Version | Reference | Shared |
| Program | Reference | Global |
| Pronoun | Reference | Global |
| Region | Reference | Global |
| Shift | Reference | Global |
| SIS | Integration | Global |
| SIS User | Reference | Shared |
| State | Reference | Global |
| Term | Reference | Shared |
| Test Score | Operational | Global |
| Test | Reference | Shared |
| IDNC | Operational | Global |
Collectively, items of these objects enable you to manage the functionality of the Lead object.
Objects in the Objects node are listed in the following order:
1. All System objects are listed alphabetically.
2. All Reference objects, except the Address Type reference object (specific to Higher Education Foundation) are classified as Custom (Reference) and are listed alphabetically.
3. The remaining custom objects, including the Operational and Integration Objects, are listed alphabetically.
Health Check Objects
Application Server, Campaign Dispatcher, Database, Services, Mail Service, Replication, Threader, and Web Server are examples of Health Check objects.
Health Check objects are used to monitor the state of your system. Health Check objects are only available to users with the System Administration or Database Administration permission.