The recommended way to integrate with WISEflow is to use the WISEflow API
Please Note
Always refer to the documentation on SIS integrations to find exactly what data is synchronised with WISEflow
Updating User Information Using an Integration
When a user is created in WISEflow, the user must have at least one unique Id that can be used to uniquely identify the user. With an integration, this is something that has been set up during one of the mapping workshops.
When a user is synchronised, WISEflow checks for known, unique user data types on the user. WISEflow matches the unique Ids in the following order:
- Personal Organisation Id
- Personal Unique Id
- External Id
- Email (If enabled)
Meaning that a user will first be matched with an organisation Id, then the personal unique Id, then an external Id. If no existing user is found with any of these Ids, a new user will be created.
Updating a User on Login
When a user logs in, WISEflow will automatically match the user's unique Ids with all current users. If one or more of the unique Ids are matching a current user, WISEflow will update the current user with information from the new user (if enabled on your licence). When updating a user, WISEflow will iterate through all values and update singular values: Names, External User Id, User Alias and Language, and add values that can be multiple: Email, Phone, Student Number, Personal Organisation Id, Personal Unique Id and Roles.
If, after matching the unique Ids, the user does not have any updated user information, the user is logged in.
If a user logs in, but there are no matching unique Ids on current users, WISEflow will automatically create the user (if enabled on your licence). The user will then be created with the unique Id used for login. In the future, when the user is updated, WISEflow will iterate through the user information as described above.
The below chart describes how a user is updated when logging in to WISEflow:
Updating a User Via the Flow Synchronisation
When a user is added to a flow during a synchronisation, WISEflow will automatically match the user with current users and either create or update the user. This process is very identical to the above and will update the user information across all flows that a user is active on.
Overview of User Data Types
| Meta type | Singular/Multiple | Unique | Description |
| External User Id | Singular | Yes | A unique ID is used internally at the institution. The External User ID is usually an attribute coming from SIS or added through the API. |
| Personal Unique Id | Multiple | Yes | This could be a nationalId. This ID is unique per licence and thus can be used to identify a user in, e.g., governmental systems. |
| Personal Organisation Id | Multiple | Yes | eduPersonPrincipalName. This is the mandatory unique identifier used by various identity providers. |
| Student Number | Multiple | No | Typically, a student number, but could be any non-unique value used to identify the user. This meta type can also be used to store additional information, e.g., a department. |
| User Alias | Singular | No | Very similar to Student Number. The main difference is that User Alias is singular. |
Relevant Articles
What, how, and when data is synchronised during the flow phases