June Project Updates | Constituent Relationship Management (CRM) | Kent State University

Recruiting Update

PROJECT HIGHLIGHTS

  • Participated in TargetX on-site training for primary team members of all admitting units; creating reports, email templates, events, etc
  • Loaded all recruitment data to MIT (Migration/Integrations Test) and UAT (User Acceptance Test) sandboxes
  • Completed working sessions with TargetX and core functional project team members to create email templates, create events, learn Conga, and configure travel for recruiting.
  • Configured and tested duplicate rules for duplicate record management, contact record, and related objects (recruiting lifecycle records)
  • Completed mapping of SAT test score and vendor (5 files) data loads

UPCOMING PROJECT ACTIVITIES

  • Continue to build the test score and vendor data load mappings
  • Build reports, events, and communications needed for go live
  • Conduct user acceptance testing; begin to deploy approved items to production
  • Test SAT test score and vendor data loads

Admissions Update

PROJECT HIGHLIGHTS

  • Tested the Target X Spring Release
  • Moved TargetX Spring Release to Production

UPCOMING PROJECT ACTIVITIES

  • Complete code review of CAD

One Stop Update

PROJECT HIGHLIGHTS

  • Completed Service Cloud Accelerator
  • Closed discovery project

UPCOMING PROJECT ACTIVITIES

  • Begin technology project planning in Q4 2017

Enterprise Marketing Cloud Update

PROJECT HIGHLIGHTS

  • Conducted Custom Subscription Center (CSC) code review with IS team
  • Reviewed User Interface with IS User Designer
  • Previewed CSC with Marketing Cloud Enterprise Team
  • Conducted initial QA testing of CSC in development sandbox

UPCOMING PROJECT ACTIVITIES

  • Review and finalize new design mock-ups
  • Deploy CSC to UAT and connect Marketing Cloud to Salesforce
  • Test CSC and Marketing Cloud connection
  • Deploy to Production

University Calendar Update 

PROJECT HIGHLIGHTS

  • Processed/tested parallel calendar events for pilot areas 
  • Tweaked event messaging, requests, and creation based on parallel testing feedback
  • Finalized event categories, types, and use of tags
  • Worked on ability to integrate events created in Salesforce to be pulled into Drupal and onto department web pages
  • Continued coding of event display/search within Flashline/University website
  • Prepared communication for go-live event processing scheduled for early June

UPCOMING PROJECT ACTIVITIES

  • Go live on University calendaring software for pilot areas (CSI, UCM, College of Arts, Stark, IS)
  • Enter pilot areas events from early June forward
  • Monitor pilot and compose game plan for rolling out software to remainder of university
  • Document new processes flows / guidelines
  • Complete coding of event display/search within Flashline/University website

Flashperks Update 

PROJECT HIGHLIGHTS

  • Processed/tested parallel Flashperks event for pilot areas
  • Tweaked messaging and queue processing based on parallel testing feedback
  • Tested load of one year Flashperks event history and attendance data from existing vendor to Salesforce
  • Implemented Flashperks tile displaying student points within Flashline
  • Continued coding of event display/search within Flashline/University website
  • Coded reports and dashboards for data analysis
  • Prepared communication for Flashperks go-live scheduled for early June

UPCOMING PROJECT ACTIVITIES

  • Go live early June
  • Load final event history data of all available Flashperks from existing vendor to Salesforce
  • Load prize inventory, claimed and unclaimed prize information, student point data
  • Document of new process flows / guidelines
  • Utilize ability to pull Flashperks events into CSI web-site
  • Add ability to see events attended for a given contact

Data Migration - General Person Update 

PROJECT HIGHLIGHTS

  • Identified General Person data rules and conditions 
  • Loaded general person (Active Student) data to MIT (Migration/Integrations Test) and UAT (User Acceptance Testing) sandboxes
  • Validated data in MIT and identified changes to data rules and conditions

UPCOMING PROJECT ACTIVITIES

  • Tweak coding of rules and conditions per validation feedback
  • Reload corrected General Person (Active Student) data to MIT
  • Sign off General Person (Active Student) data load in MIT
  • Identify General Person (Active Student) sync rules to keep data up-to-date
  • Plan for deployment in UAT and Production