You are here:

About Talisma Higher Education Foundation

Object Category	Object
Operational Objects	Lead, Activity, Address, Enrollment, Test Score, Document Status, IDNC, Academic Progress, Course History, and Goal.
Reference Objects	Term, Education Level, Ethnic Group, Lead Source, Lead Type, Program, Program Version, Program Version Start Date, Area of Interest, Area of Study, Program Level, State, Country, Address Type, Shift, Region, Nationality, Document Status Type, FERPA Group, Test, SIS User.

Operational Objects

Lead Management in Talisma involves working with the following Operational Objects:

• Lead

• Activity

• Address

• Enrollment

• Test Score

• Document Status

• IDNC

• Academic Progress

• Course History

• Goal

In the process of managing Leads, you will also be required to work with the Contact and Account Objects.

The Activity Object is a ‘container’ Object in which details of the Interaction are available. A new Activity is created in the Talisma system when you engage the Lead by exchanging e-mail messages with the Lead. The resultant Interaction that is created can be viewed when you open the parent Activity Object item in Talisma.

The Activity Object can be selected in the Object Selector in the Home Workspace. When you double-click an Activity, its child Object item, Interaction, will be displayed. This implies that while the Activity Object can be viewed in the Table View in Talisma Client, its child Object item will be displayed when you double-click the Activity.

Note

Activity details in Talisma and SIS are constantly updated as a result of bi-directional database synchronization. This occurs as a result of settings in Talisma Business Administrator.

Address details of a Lead are saved in Talisma as an Object item. This is required as the Lead may have multiple addresses. For example, during a vacation from school, a Lead can be contacted at a permanent address before the admissions process is complete. However, the Lead’s address while in school is different from the permanent address. Additionally, in a scenario where the Lead is temporarily employed, the Lead may have a different address during the vacation. The Address Object meets the requirement to cater to this scenario. Further, it also ensures that a framework is available to quickly and constantly be in touch with the Lead.

An Enrollment is created in the SIS when the implemented business logic determines that the Student has fulfilled specific criteria in the admission lifecycle. As a result of database synchronization with the Talisma system, details of the Enrollment Object created in the SIS are also available in the Talisma system.

The Test Score Object stores information about the scores of Test items of a Contact. For example, the scores of the Physics, Mathematics, and Computer Science Test items of the Contact are stored in the Test Score item. While you not be required to create Test Score items, you will be required to add instances of Test Score items into Lead, Contact, and Test Objects. Typically, Test score items are incorporated into Talisma from an SIS as a result of database synchronization from an SIS to Talisma.

Note

• Talisma Higher Education Foundation Setup must be installed to enable you to work with:

◦ Reference Objects, and the Address, Activity, Document Status, Test Score, Lead, and Enrollment Objects.

◦ Enhanced functionality of the Account and Contact Objects specific to Talisma Higher Education Foundation.

For more information about the Talisma Higher Education Foundation Setup, your administrator must see Installation Manager Help.

• To work with Talisma Higher Education feature, the Root Team must be configured as of type Campus in Talisma Business Administrator. For more information, see Business Administrator Help.

Reference Objects

Properties of a Lead in Talisma change as a result of the corresponding Student’s progress through the admission cycle in the SIS. To easily manage the numerous combinations of attributes applicable to a Lead such as the type of Lead, the programs in which the Lead may express an interest, and other elements of information required to effectively manage and engage the Lead, details of the Lead are available as Objects in the Talisma system. Creating them as Objects enables the Talisma-SIS integration to be loosely coupled, implying that later modifications to business logic can be achieved in a short time and with no impact on the integration, thus enabling higher education institutions to configure business logic that is completely customized to their needs. Further, new instances of Reference Objects can be easily incorporated into Talisma as the process simply entails that when the Object items are created in the SIS, the next cycle of the Talisma-SIS database synchronization achieves this seamlessly.

These Objects are referred to as Reference Objects in Talisma, indicating that while the Talisma User will not be required to create instances of these Objects, the User will be required to incorporate instances of these Objects into the Lead, Contact, and other Reference Objects. The Reference Object items would have been created automatically in the Talisma system when Talisma Main Database was first synchronized with the SIS.

Example

Instances of the Country Object are created in Talisma as a result of database synchronization with an SIS. When the Talisma User creates a Lead Object item, the User is required to select the Lead’s Country from a list of available instances of the Country Object.

While you will not typically create instances of Reference Objects in Talisma, a framework to create items of these Objects is available to those Talisma Users for whom the System Administration or Business Administration Permissions are enabled. The Object Selector in the Talisma Home Workspace will list the Reference Objects only for those Talisma Users for whom the System Administration or Business Administration Permissions are enabled.

If a Talisma Client User has a System Administration or Business Administration Permission, no other Permissions specific to the Reference Object need to be selected for the User to perform an operation on the Reference Object.

Note

• Regardless of whether the System Administration or Business Administration Permissions are enabled, the Lead, Activity, Address, and Enrollment Objects are listed in the Object Selector if your organization has implemented Higher Education Foundation.

Although Users with the System Administration or Business Administration Permissions can create and share a Reference Object-based Workspace with a Web Client user, it is recommended not to do so. Web Client Users are required to only work with items of Reference Objects. They are not required to create items of these Objects.

• When Shared Reference Object items are created through Talisma Higher Education Foundation iService and a Team is passed for the item, the Team and its child Teams are automatically shared with the item. If the value of a Team is not passed for the Shared Reference Object item through Talisma Higher Education Foundation iService, the item is automatically shared with the Home Team. However, the Reference Object item will not be shared with the child Teams of the Home Team.

The following Reference Objects are available in Talisma:

• Term

• Education Level

• Ethnic Group

• Lead Source

• Lead Type

• Program

• Program Version

• Program Version Start Date

• Area of Interest

• Area of Study

• Program Level