Casepoint: Difference between revisions

From UmsWiki
Jump to navigation Jump to search
Created page with "Introduction text. == Prerequisites == === Supported administrative systems === === Module requirements === === Additional functionality === === Testing after setup ===..."
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Introduction text.
Integration with IT Leans SharePoint-based electronic sales and document management system. CasePoint ensures that users automatically have the proper permission. The automation saves the school resources and time at the IT department.


== Prerequisites ==
== Prerequisites ==


=== Supported administrative systems ===
=== Module requirements ===
[[UMS]]
 
== Installation ==
 
=== '''Security options''' ===
[[File:Casepoint.png|none|thumb]]
 
URL: The URL of the customer
 
User, Password And Domain: Active Directory information of the user used to connect to CasePoint


=== Module requirements ===
Delete Users: Whether or not to delete users when they leave


=== Additional functionality ===
Delete after: Keep users for a certain number of days after they have left


=== Testing after setup ===
=== '''Metadata''' ===
Creating users: Metadata used when creating or updating users


=== What to have ready ===
Disabling users: Metadata used when disabling users
[[File:CasepointMetadata.png|none|thumb]]


=== Is any physical item required ===
Casepoint key name: The key that casepoint uses


=== Should third party be contacted ===
Static text (Before/After): Can be any text


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


== Technical settings ==
Required in CasePoint: Check this to make sure the field will not be empty in CasePoint. If the field is blank in UMS it will not send the record to Casepoint


== FAQ ==
=== '''Template Setting''' ===
This is where you connect a CasePoint Setting to a template. Users on this template will be synchronized with CasePoint.
[[File:Casepointtemplateeditor.png|none|thumb]]

Latest revision as of 10:26, 17 March 2017

Integration with IT Leans SharePoint-based electronic sales and document management system. CasePoint ensures that users automatically have the proper permission. The automation saves the school resources and time at the IT department.

Prerequisites

Module requirements

UMS

Installation

Security options

URL: The URL of the customer

User, Password And Domain: Active Directory information of the user used to connect to CasePoint

Delete Users: Whether or not to delete users when they leave

Delete after: Keep users for a certain number of days after they have left

Metadata

Creating users: Metadata used when creating or updating users

Disabling users: Metadata used when disabling users

Casepoint key name: The key that casepoint uses

Static text (Before/After): Can be any text

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

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

Template Setting

This is where you connect a CasePoint Setting to a template. Users on this template will be synchronized with CasePoint.