Understanding Talisma Objects

Object type	Object
Global Objects	Account, Event, and Participant which are purely Global Objects. User and Target, which are special Global Objects.
Team Objects	Interaction, Campaign, Opportunity, Order, Message, and Application.
Shared Objects	Canned Response, Mailer/SMS Template, Offer, Mailing List, Product, Link, Print Template, and Script.

Global Objects

• Purely Global Objects: Accounts, Event

• Special Global Objects: User, Target

Global Objects are not Team specific, and are available to all Users. Thus, the Account and Event Objects, which are purely Global Objects, are available to all Users, irrespective of the Teams to which the Users belong. They are managed in Talisma Client from the relevant Workspaces.

User and Target are special Global Objects. Although the User Object is not available to Users, the User Name Properties can be defined in other Objects. In addition, a User Object Property can be defined in Relationships between the User Object and other Objects.

Note

By default, the Contact Object is a Global Object. However, you can enable Team-based security for the Contact Object. For more information about enabling Team-based security for the Contact Object, Talisma Product Support.

Relationships

A Relationship is an association between two Objects. For example, Employees are assigned to Projects. In this context, Employee and Project are custom Objects created in Talisma, and a Relationship exists between them. This Relationship enables Managers to assign Employees to appropriate Projects.

Example 1

The Business Administrator User can define a User type Property called User Name for the custom Object, Policy. User Name values will be listed for the User Name Property in the Policy window in Talisma Client.

Example 2

The Business Administrator User can create a One to One Relationship between two Objects, User and Policy. In this Relationship, User Name can be defined as a Property in the Policy Object, and Policy ID can be defined as a Property in the User Object.

The Target Object, which is a Global 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 customer. A Contact may need to deal with one to several Teams in an organization while conducting business. Therefore, the Contact Object is classified as a Global Object. Other predefined Talisma Objects such as Interactions, Accounts, Campaigns, Targets, Opportunities, and Orders directly depend on the Contact Object. A Contact's transactions are not confined to a single Team. Please note that a Team refers to a division or department in the organization.

A Contact may represent an organization. The Account Object represents the organization to which that Contact belongs. Account is a Global Object. An Account representing a Contact may need to deal with several Teams in the organization.

Contact and Account information is therefore available to all Teams in Talisma. However, Contacts and Accounts may have Properties that are available only for certain Teams.

The Event Object enables your organization to manage Events. Events can be of various types. Your organization can conduct Events to launch products, or services. For example, you are the Marketing Manager at WorldWaves Inc, and your organization is promoting vocational courses for students offered by Neptune University. WorldWaves Inc is organizing an Event to present the courses to prospective students. The Event will gauge the preferences of the student community, and will assist Neptune University in planning, and presenting courses that are requested by the students.

A Participant is a Contact in Talisma who is associated with an Event. When a Contact is added to an Event, the Contact progresses to be created as a Participant Object item.

When the Event is conducted, Properties of the Participant, and Contact Object items that are associated with the Event Object item are updated.

A User is a representative of an organization who interacts with contacts and visitors using Talisma.

A Target is a record of a campaign base object that progresses through a campaign. Targets are not created manually like other objects; they are created automatically when the base object instance progresses through the campaign.

Example

If your organization has a business relationship with an Enterprise, that Enterprise is termed as an Account in Talisma. An Account is a Global Object, and is available to all Teams in Talisma.

However, you can create specific Properties for the Account Object that can be made available only to specific Teams such as Sales or Finance.

In addition to these predefined Global Objects, Global custom Objects can be created in Talisma Business Administrator.

Team Objects

• Purely Team Objects: Interactions, Campaigns, Opportunities, Orders, Messages, and Applications.

Team Objects belong to only one Team, and are available to Users who have access to that Team. A Team Object can be assigned to Users within the Team in which it is created, or transferred to Users outside the Team. After the Object is transferred, it belongs to the Team to which it has been transferred.

Team Objects are managed in Talisma Client from the relevant Workspaces. Interactions, Campaigns, Opportunities, Orders, Targets, and Messages are examples of predefined Team Objects.

Example

A User with access to the Marketing Team can create a Campaign in this Team. Only Users on the Marketing Team can view or edit this Campaign. These Objects are also called local Objects, because operations on them are confined to Users belonging to Teams in which they are created.

In the Service scenario, the organization builds business relationships with Accounts, who are represented by Contacts. Interactions result from the conversations an organization has with its Contacts.

Campaigns are aimed at Targets, who are instances of Contacts on whom the Campaign is focused. At the end of a Campaign, Targets who express interest in a product or service or any business proposition are converted into Opportunities, and then assigned to sales representatives. The Opportunities are then serviced and followed up in an effort to convert them into Orders.

In addition to these predefined Team Objects, Team custom Objects can be created in Talisma Business Administrator.

Shared Objects

Canned Responses, Mailer/SMS Templates, Offers, Mailing Lists, Products, Links, Print Templates, and Scripts are examples of predefined Shared Objects in Talisma.

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 in all Teams with which the Object is shared.

Canned Responses, Scripts, Mailer/SMS Templates, Mailing Lists, Offers, Products, Filters, Links, Print Templates, and Workspaces are examples of predefined Shared Objects in Talisma. All Shared Objects, except Links, Print Templates, and Shared Custom Objects, are managed from the relevant Managers in Talisma 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.

Example

You can create a Canned Response in a Team, and then share it with Users in different Teams. Similarly, you can share Categories, Properties, Mailer/SMS Templates, Offers, Mailing Lists, Products, Scripts, Reports, Rules, Print Templates, and Links.

In addition to these predefined Shared Objects, Shared custom Objects can be created in Talisma Business Administrator.

Talisma Higher Education Foundation Objects

If Talisma Higher Education Foundation is installed, the Objects in the following table are also displayed in the Objects node. These Objects are categorized as Operational, Reference, and Integration based on their usage Collectively, items of these Objects enable you to manage the functionality of the Lead Object in Talisma.

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
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

Health Check Objects

Application Server, Campaign Dispatcher, Database, Services, Mail Service, Replication, Threader, and Web Server are examples of Health Check Objects in Talisma. 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.