Axpoint: Difference between revisions
No edit summary |
|||
| Line 17: | Line 17: | ||
=== Security options === | === Security options === | ||
URL: The URL of the | Site Collection URL: The URL of the workarea | ||
User | Security token: Value optained from Axpoint | ||
Site type: Value optained from Axpoint | |||
User account: The user that has the right to access the site collection | |||
Waid: Value optained from Axpoint | |||
=== Disable/Enable === | === Disable/Enable === | ||
The key and values are different from 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 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 === | === 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 == | == Metadata == | ||
Creating users: Metadata used when creating or updating users | Creating users: Metadata used when creating or updating users[[File:Axpoint Metadata.jpg|none|thumb|668x668px]] | ||
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 | 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 | ||
Revision as of 14:40, 11 January 2018
Integration with Axpoint's Office 365 SharePoint-based document management system.
Prerequisites
Module requirements
Template Setting
This is where you connect a Axpoint Setting to a template. Users on this template will be synchronized with AxSelpoint.
Settings
Select the setting you want to change or add a new one
Setting
Security options
Site Collection URL: The URL of the workarea
Security token: Value optained from Axpoint
Site type: Value optained from Axpoint
User account: The user that has the right to access the site collection
Waid: Value optained from Axpoint
Disable/Enable
The key and values are different from 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