Difference between revisions of "TASS Sync Profiles"

From Studentnet Wiki
Jump to navigation Jump to search
Line 3: Line 3:
 
==Split Parents==
 
==Split Parents==
 
===Split Parent in Cloudwork===
 
===Split Parent in Cloudwork===
Split parents are handled in Cloudwork by assigning either '''user_code''' or '''sfa_num''' values as usernames
+
Split parents are handled in Cloudwork by determining whether both Parents have the same or different '''user_code'''
  
====Split Parent handled by user_code====
+
====Split Parents with different user_codes====
Split Parents created in Tass using user_code are displayed on Cloudwork as:
+
Split Parents created in Tass with user_codes are displayed on Cloudwork as:
  
[[File:tass_split_parent-1.png|1100px|center|frame|Splits Parents in User List using user_code]]
+
[[File:tass_split_parent-1.png|1100px|center|frame|Splits Parents in User List using different user_codes]]
  
 
[[File:tass_split_parent_2.png|500px|center|frame|Parent 1 using user_code for username]]
 
[[File:tass_split_parent_2.png|500px|center|frame|Parent 1 using user_code for username]]
  
[[File:tass_split_parent_3.png|500px|center|frame|Parent 2 user_code for username]]
+
[[File:tass_split_parent_3.png|500px|center|frame|Parent 2 using user_code for username]]
  
  
  
====Split Parent by sfa_num====
+
====Split Parents with same user_code===
  
Split Parents created in Tass using sfa_num are displayed on Cloudwork as:
+
Split Parents sharing one user_code, when creating separate accounts, in Cloudwork, the '''sfa_num''' will be added to Parents user_code to distinguish them.
  
[[File:tass_split_parent_4.png|1100px|center|frame|Splits Parents in User List using sfa_num]]
+
[[File:tass_split_parent_4.png|1100px|center|frame|Splits Parents in User List using usercode and sfa_num]]
  
[[File:tass_split_parent_5.png|250px|center|frame|Parent 1 sfa_num for username]]
+
[[File:tass_split_parent_5.png|250px|center|frame|Parent 1 usercode and sfa_numfor username]]
 
 
[[File:tass_split_parent_6.png|250px|center|frame|Parent 2 sfa_num for username]]
 
  
 +
[[File:tass_split_parent_6.png|250px|center|frame|Parent 2 usercode and sfa_num for username]]
  
 
==Cloudwork Syncing Instructions==
 
==Cloudwork Syncing Instructions==

Revision as of 06:27, 23 July 2021

Tass

Split Parents

Split Parent in Cloudwork

Split parents are handled in Cloudwork by determining whether both Parents have the same or different user_code

Split Parents with different user_codes

Split Parents created in Tass with user_codes are displayed on Cloudwork as:

Splits Parents in User List using different user_codes
Parent 1 using user_code for username
Parent 2 using user_code for username


=Split Parents with same user_code

Split Parents sharing one user_code, when creating separate accounts, in Cloudwork, the sfa_num will be added to Parents user_code to distinguish them.

Splits Parents in User List using usercode and sfa_num
Parent 1 usercode and sfa_numfor username
Parent 2 usercode and sfa_num for username

Cloudwork Syncing Instructions

Credentials needed

  • Token key
  • App Code
  • API Version
  • Company Code
  • Endpoint

Credentials located in Tass>System Admin>Utilities>API Gateway Maintenance

Login to Cloudwork Dashboard and click Sync Profile

tass Setup 2

Click New Sync Profile

tass Setup 2

Select Tass Sync Profile from sync profile types

tass Setup 3

Under Basic Settings, input a simple description for this profile, and credentials provided by Tass.

tass Setup 4

Select the attribute to be mapped to Cloudwork for Tass under Parents Usercode Mapping, Students Usercode Mapping, Staff Usercode Mapping , choices include SIS ID (highly recommended) and User Name.

tass Setup 5

Under User Settings, for each type of users, parents, students, and staff, there are choices sync users, organisational unit, maintain ou for existing users, and actions for users no longer meet the condition web_access = True

By ticking ‘Do not change orgunits for current users', existing users will not be moved to ou set by the previous three fields.

“Action for disabled users” works if users no longer meet the condition web_access = True. Actions include “Do nothing”, “Suspend User”, and “Delete User”.

tass Setup 6

Save the settings, there will be a green flash showing the creation is successful, and the information input creates a successful connection with TASS

tass Setup 7

Scroll down, there will be 3 tables showing custom attributes for parents, students, and staff.

tass Setup 8

Click Edit for three tables and add custom attributes for three types of users.

tass Setup 9

A green flash will show after the attributes are added.

tass Setup 10

Click Force Sync for pulling users from Tass. A green flash shows the pulling process is successful.

tass Setup 11

In the sync details table, the pulling result of three types of users will be shown here.

tass Setup 12

Heading to Users, select a pulled user, the extra attributes will be added.

tass Setup 13