Behavior of the SIS owner and Admissions representative Properties

Concept Link IconSee Also

When a Lead is created and the values for the SIS owner and Admissions representative fields are not specified, after saving the Lead, the value in the Admissions representative field is automatically set to the value that is set in the SIS owner field. The value set in the SIS owner field is based on the value specified in the Owner field of the Lead and some conditions.

Following topics describe the scenarios based on which the value in the SIS owner field is set for a Lead, if a Talisma Client User does not specify a value in the SIS owner field before saving the Lead, and when a Lead is assigned or transferred to another Team or User.

Scenario 1 - When the value in the Owner field of a Lead is set to a Talisma User that is mapped to an SIS User

In this scenario, the value of the SIS owner field is set to the SIS User that is mapped to the Talisma User specified in the Owner field, if the following conditions are satisfied:

•   The Active Property of the SIS User is Yes

•   The Administrations representative Property of the SIS User is Yes

If the above two conditions are not satisfied, the SIS owner field will be blank.

Example 

Mark is an SIS User created in Talisma and is mapped to a Talisma User John. The following graphic displays configurations of the SIS User, Mark:

Configurations for the SIS User Mark

When John creates a Lead and does not specify a value in the SIS owner field, Mark-10 is automatically set as the value in the SIS owner and Admissions representative fields.

Scenario 2 - When the value in the Owner field of a Lead is not mapped as a Talisma User for an SIS User

In this scenario, if a Default SIS User exists for the Campus to which the Lead belongs and the following conditions are satisfied, the SIS owner field is set to the Default SIS User:

•   The Active Property of the SIS User is Yes

•   The Administrations representative Property of the SIS User is Yes

If the above two conditions are not satisfied, the SIS owner field will be blank.

Example 

In Talisma Business Administrator the following configurations are performed:

•   For the Campus Virginia, Alex which is an SIS User in Talisma, is configured as the Default SIS User.

•   A User, Samantha, is created and is assigned to the Virginia Campus. Further, Samantha is not mapped to any SIS User.

In Talisma Client, the following configuration is available for the SIS User, Alex:

Configurations for the SIS User Alex

In this scenario, when Samantha logs on to Talisma Client, and creates and saves a Lead without specifying values in the SIS owner and Administrations representative fields, Alex-20 is automatically set as the value in the SIS owner and Admissions representative fields for the Lead.

 

Note 

•   When you create a Lead and specify a value for the SIS owner field and save the Lead, the Admissions representative field will automatically be set to the value specified in the SIS owner field.

However, when you create a Lead and specify a value for the Admissions representative field, the SIS owner field will be set based on the scenarios explained in the above topic. As a result, the SIS owner and Admissions representative fields may have different values.

•   When the value of the SIS owner and Admissions representative fields are set by a User in Talisma Client or through a Talisma Higher Education iService request, these values will be retained in the SIS owner and Admissions representative fields and will not change based on the scenarios explained in the above topic.

•   For an existing Lead, if the value in the SIS owner field is changed later from Talisma Client or through a Talisma Higher Education iService request, the value in the Admissions representative field will not change automatically.

 

Send feedback on this topic (documentation@campusmgmt.com)