Ellucian Elevate Fixpack - Deployment to TEST - Jan 30, 2018
Scheduled Maintenance Report for Ellucian Cloud
The scheduled maintenance has been completed.
Posted about 1 year ago. Jan 30, 2018 - 08:00 EST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted about 1 year ago. Jan 30, 2018 - 03:00 EST
Ellucian SaaS Maintenance
Ellucian Elevate Fixpack
Deployment to TEST - Jan 30, 2018
This notice is to inform you about planned fixpack maintenance to the Ellucian Elevate TEST environments on Tuesday January 30th 2018.
The fixpack addresses several important new CR's, and contains the rollup CR's from the previous fixpacks released for 8.13. Detailed Information about the fixpack will be posted in the Ellucian Documentation Library shortly. A brief list of them is included here:

CR-000147541: If a user creates a new account using Enroll and Pay when redirected from
a shopping cart link, the system does not generate the email message for
the new account that contains the logon credentials.

CR-000152307: The Heartbeat monitoring mechanism continually failed (with a connection
error) in environments where an institution had integrated Elevate with
Banner 9.9 (or above).

CR-000152966: The system generated a database error if a user deregistered a student
from an employer enrollment that was using multiple enrollment codes and
which had no places remaining.

CR-000153386: Elevate did not charge fees for students on program instances where
the fee level was set to section, if users set the default values of the fee
parameters for the section fee level and the program instance fee level to
the same value in the Reference Data Manager.

Export of student charge and payment data:
When users exported student charge and payment data to a CSV file, using
the functionality introduced in Ellucian Elevate Software Update,
the system did not truncate the field containing the financial transaction
description if it exceeded 30 characters. If a record contained a value for
this field that was greater than 30 characters, Banner did not load this
record from the file.

If an institution had enabled Single Sign-On (SSO) in Elevate, was
using Active Directory as the Identity Provider (IdP), and was using the
embedded LDAP Server then Elevate did create a user account for a new
person, if an account for this person did not already exist in the system, as
expected. However, the LDAP ID generated in Elevate did not match the
corresponding value released by the IdP, so that the person could not log
on to the Elevate Student Gateway or Elevate using the credentials defined
for the new account.

SSO and person lookups in integrated environments:
When an institution enabled Single Sign-On (SSO) for Elevate in integrated environments, the system did not check if a person record existed in the integrated ERP before it created records for new users in Elevate.

The maintenance will begin at 3AM Eastern and is expected to conclude by 8AM Eastern on the day indicated.

NOTE: PROD deployment is planned for Thursday February 1st at 3AM Eastern.

The system will be unavailable during the window, a maintenance page will be posted to alert users to the system availability.
Please review the release documentation. If you have been impacted by one or more CR's that are included, please test to ensure the functionality is working as designed. Otherwise, there is no action required by Customers. If you experience any post-upgrade issues please contact the Action Line for support.
Thanks for your help and cooperation, feel free to reach out to your Customer Success Manager with any questions.
Your Ellucian Cloud Services and Customer Success Teams
Posted about 1 year ago. Jan 25, 2018 - 14:34 EST
This scheduled maintenance affected: Ellucian SaaS (Ellucian Elevate).