Axpoint: Difference between revisions

From UmsWiki
Jump to navigation Jump to search
Kia (talk | contribs)
No edit summary
Line 7: Line 7:


== Template Setting ==
== Template Setting ==
[[File:Axpoint Template.jpg|none|thumb|555x555px]]
This is where you connect an Axpoint Setting to a template. Users that are on this template will be synchronized with Axpoint.[[File:Axpoint Template.jpg|none|thumb|694x694px|This is where you connect an Axpoint Setting to a template.]]
This is where you connect an Axpoint Setting to a template. Users on this template will be synchronized with Axpoint.
 
== Settings ==
== Settings ==
[[File:Axpoint Settings.jpg|none|thumb|462x462px]]Select the setting you want to change or add a new one  
Start by selecting the setting you want to change or add a new one. [[File:Axpoint Settings.jpg|none|thumb|556x556px|Start by selecting the setting you want to change or add a new one.]]After choosing to either create a new or edit an existing setting, you will see the picture below.[[File:Axpoint Setting.jpg|none|thumb|707x707px|This is where you set up your Axpoint settings.]]
 
== Setting ==
[[File:Axpoint Setting.jpg|none|thumb|707x707px]]


=== Security options ===
=== Security options ===
Site Collection URL: The URL of the workarea
Site Collection URL: The URL for the work area


Security token: Value optained from Axpoint
Security token: Value obtained from Axpoint


Site type: Value optained from Axpoint
Site type: Value obtained from Axpoint


User account: The user that has the right to access the site collection
User account: The user who are allowed to access the site collection


Waid: Value optained from Axpoint
Waid: Value obtained from Axpoint


=== Disable/Enable ===
=== Disable/Enable ===
The key and values are different from each customer
The key and values are different for each customer.


Key: It is the key Axpoint looks at to see if a user is disabled or not (do not include in metadata)
Key: It is the key Axpoint looks at to see if a user is disabled or not (do not include in metadata)

Revision as of 15:07, 11 January 2018

Integration with Axpoint's Office 365 SharePoint-based document management system.

Prerequisites

Module requirements

UMS

Template Setting

This is where you connect an Axpoint Setting to a template. Users that are on this template will be synchronized with Axpoint.

This is where you connect an Axpoint Setting to a template.

Settings

Start by selecting the setting you want to change or add a new one.

Start by selecting the setting you want to change or add a new one.

After choosing to either create a new or edit an existing setting, you will see the picture below.

This is where you set up your Axpoint settings.

Security options

Site Collection URL: The URL for the work area

Security token: Value obtained from Axpoint

Site type: Value obtained from Axpoint

User account: The user who are allowed to access the site collection

Waid: Value obtained from Axpoint

Disable/Enable

The key and values are different for each customer.

Key: It is the key Axpoint looks at to see if a user is disabled or not (do not include in metadata)

User enabled value: A value that defines the user as active

User disabled value: A value that defines the user as disabled

Disable options

Disable Users: Whether or not to disable users when they leave

Disable after: Keep users active for a certain number of days after they have left and before disabling them

Metadata configuration

Select the Metadata setting used

SQL Sentence

This is used to define more uniquely what records to include from the students table. This is only the Where part of a SQL sentence

Could be something like

(Studienr = 'UMS)

Or (Fullname like 'inLogic%')

Metadata

Creating users: Metadata used when creating or updating users

Axpoint key name: The key that Axpoint uses

Static text beforedatabase field: Can be any text

UMS database field: Choose a field from the students table.

Static text after database field: Can be any text

Required in Axpoint: Check this to make sure the field will not be empty in Axpoint. If the field is blank in UMS it will not send the record to Axpoint