cornerstone + banner core inbound integration - 2020 update · 2020. 7. 7. · 3 introduction •...

19

Upload: others

Post on 01-Feb-2021

0 views

Category:

Documents


0 download

TRANSCRIPT

  • Cornerstone + Banner Core Inbound Integration - 2020 UpdateJON BROCKWAY, Sr. Technical Program Manager, Cornerstone OnDemandNICOLE RIVERA, Solutions Consultant, Cornerstone OnDemand

  • 3

    Introduction

    • Goal: Present the Core Data Sync Integration between Banner and Cornerstone for Cornerstone clients

    • Cornerstone clients will understand:

    • What is included in the integration

    • How to install the integration from the Cornerstone Edge Marketplace

    • The Organization Unit and User field mapping and exceptions

  • 4

    Agenda

    1 Integration Overview and Architecture

    2 Use Cases

    3 Self-Service Capability & Edge Integration

    4 Integration Field Mappings

    5 Integration Exceptions

  • Integration Overview

  • 6

    Integration Overview

    Before:• File based integration for managing user and OU records• Requires Banner to send records to an FTP• An automated feed in Cornerstone picks up the file and loads using the

    Data load wizard based on a scheduler• Requires mapping exercise in the DLW

    After: • Allows management of employee and Organizational Unit (OU) data in

    Cornerstone when there are changes to corresponding records in Banner• Integration hosted on the Edge product• Enablement will be simple and client facing• Integration is API based and will no longer require flat files.

  • Integration Architecture

    Core Data Inbound

    • Employees• Institution-Positions• Employment-

    Organizations• Etc.

    • Users• Division OU• Location OU• Position OU• Cost Center OU

    ETHOS Data Models

    1. API based integration2. Self-service capability3. Centralizes User management

  • Use Cases1. Admin adds new

    user record in Banner

    2. Admin updates existing record in Banner

    3. Admin adds new OU record in Banner

    4. Admin updates existing OU record in Banner

  • Integration Enablement

  • Self-Service CapabilityNavigate to your CSOD portal. Go to Admin > Tools > Edge > Marketplace

    STEP 1: Select Integration

    STEP 2: Install Integration

  • Edge Configuration

    STEP 3: Configure Integration and Save

  • Integration Field Mappings

  • Organizational Unit MappingEllucian Data Type Ellucian API Endpoint RecommendationInstitution Positions api/institution-positions Recommended to Map to

    PositionSites api/sites Recommended to Map to

    LocationEmployment Departments api/employment-departments

    Employment Organizations api/employment-organizations

    Employers api/institution-employersPosition Classifications api/position-classificationsPay Classes api/pay-classesPay Cycles api/pay-cycles

  • Organizational Unit MappingBelow are the fields mapped for Organizational Units

    CSOD Field Ethos Field

    OU ID Code

    OU Title Title

    Status Status

  • User Mapping Cornerstone Field Name Ellucian Banner Field Name Ethos Data Model Mapping

    User ID Banner Source ID Persons > Credentials > Value = BannerSourceID

    Username Banner ID Persons > Credentials > Value = BannerIDActive Employee Status Employees > StatusAbsent Employee Status Employees > StatusPrefix Title Persons > Names > TitleFirst Name First Name Persons > Names > First Name (type = preferred)

    Middle Name Middle Name Persons > Names > Middle Name (type = preferred)

    Last Name Last Name Persons > Names > Last Name (type = preferred)

    Suffix Pedigree Persons > Names > Pedigree (type = preferred)

    Email Business Email Persons > Emails > Address (Type = business)Personal Email Personal Email Persons > Emails > Address (Type = personal)

    Work Phone Business Phone Number Persons > Phones > Number (Type = business)

  • User Mapping Cornerstone Field Name Ellucian Banner Field Name Ethos Data Model Mapping

    Home Phone Home Phone Number Persons > Phones > Number (Type = home)

    Mobile Phone Mobile Phone Number Persons > Phones > Number (Type = mobile)

    Fax Fax Phone Number Persons > Phones > Number (Type = fax)

    Country Country Code Addresses > Place > Country > Code

    Address Line 1 Business Address Addresses > Address Lines (Type = business)

    City Locality Addresses > Place > Locality (Type = business)State Region Title Addresses > Place > Region > Code

    Zip Code Postal Code Addresses > Place > Postal Code

    Required Approvals Defaulted to "1"Last Hire Date Start On Date Employees > Start OnManager ID Supervisor ID Institution Jobs > Supervisor > ID (Job Preference = primary)

    Gender Gender Persons > GenderEthnicity Ethnicity Persons > EthnicityLanguage Language Preference Persons > Language (preference = primary)

    Location ID

    **Based on OU ConfigurationPosition IDGrade IDDivision IDCost Center ID

  • Integration Exceptions

  • 18

    Integration Exceptions

    • This integration allows for mapping to standard Organizational Unit types only.

    • Organizational Unit Custom Fields are not supported.

    • User mapping is preset and not configurable at this phase.

    • User Custom Fields are not supported.

    • Organizational Unit types in the Edge Configuration Screen are labeled with original Cornerstone Titles and do not reflect and OU Type that has been renamed by the client.

  • Thank You!