Aggie Service Fix Notifications Archive

Three blue silhouette heads precede the words "Aggie Service" in blue and gold.

FIX UPDATES

February 28th, 2024

The AggieService Development Team, in partnership with the SSO Service Desk, are committed to continuous improvements for both UC Davis campus and Health system users. In our commitment to provide you with the best customer service, we will be keeping you updated on improvements and fixes each month our team has delivered on. The most recent improvements and fixes are

Summary

In January and February, we saw continuous improvements, with 2 bug reports, no user stories and 13 tasks closed. Improvements covered form changes, chart of account (CoA) string updates, and case flow changes. 

We are continuously monitoring our forms for performance improvements. Bug fixes addressed form data not mapping to cases for service providers and routing issues. Form enhancements implemented, include Benefits having their own form to allow users different topic selections. All Academic Postdoctoral Appointment forms were updated to reflect current processes. Users now have the ability to enter two job details for all Onboarding Only, and Additional Employment forms.

In alignment with the Aggie Enterprise project to establish consistency in UC system - wide accounting, ours has been a work-in-progress, spanning multiple sprints. Implemented bug fixes now allow forms to validate UCPath PPM string format. The Funding Account Information section help text was updated to allow links to open in a new browser window. 

Important improvements and fixes from this release:

  • Created a new dedicated Benefits form in FormAssembly.
  • Implemented additional Question Type and Topic categories for ELR cases. 
  • Made updates to ELR case visibility and security.
  • Implemented Associated Records in cases to capture multiple job details entered.

Upcoming projects  

  • Health LOA team to transition into using AggieService for their work flows. 
  • Further enhancements of Student and Graduate Recruitment form to accommodate multiple positions.

 

January 29, 2024

The AggieService Development Team in partnership with the Service Desk, are committed to continuous improvements for both UC Davis campus and Health users. In our commitment to provide you with the best customer service, we will be keeping you updated on improvements and fixes each month that our team has delivered on. Most recent improvements and fixes are as follows:

Summary

In December, we saw small continuous improvements, with 2 bug reports, no user stories and 2 tasks closed. Improvements covered contact page updates, chart of account string field updates, and case flow changes. 

We are continuously monitoring our Contact data for accuracy. Bug fixes have addressed integration issues on some contact pages, ensuring information is up to date. 

In alignment with the Aggie Enterprise project to establish consistency in UC system - wide accounting, ours has been a work-in-progress, spanning multiple sprints. Last month, all forms requiring CoA validation endpoint urls were updated. 

Important improvements and fixes from this release:

  • Salesforce security updates required by Jan 1 2024 have been completed. 
  • The flow called ‘Close Cases Update Operations’ was updated to run, even if the case submitter / contact / email address field was left blank or empty.
  • We changed integrations to ensure the Contact information was updating correctly. 
  • We updated the endpoint url on forms requiring CoA validation.

Upcoming projects for the year!  

  • Health LOA team to transition into using AggieService for their work flows. 
  • Health Worker’s Compensation team to transition into using AggieService for their work flows. 
  • Enhancements of Benefits team form to allow for different topic selections. 
  • Enhancements of Student and Graduate Recruitment form to accommodate multiple positions.

December 21, 2023

The AggieService Development Team in partnership with the Service Desk, are committed to continuous improvements for both UC Davis campus and Health users. In our commitment to provide you with the best customer service, we will be keeping you updated on improvements and fixes each month that our team has delivered on. Most recent improvements and fixes are as follows:

Summary

This past month we saw small continuous improvements with 1 bug report, 1 user story and 4 tasks closed. Improvements covered contact pages updates, chart of account strings and case assignment rule changes. 

In accordance with the UC policy and process for use of preferred or lived name for staff and employees, contact pages were updated to show preferred names. Bug fixes addressed integration issues on some contact pages ensuring data is up to date. 

In alignment with the Aggie Enterprise project to establish consistency in UC system wide accounting, this has been a work-in-progress, spanning across multiple sprints. This month, client case forms with funding charts now allow dual entry of both old KFS and new chart of account (CoA) account strings. Starting 12/22/23 only new account strings for new cases will be accepted. Case forms were also updated to allow Service Providers to enter new CoA strings. 

Important improvements and fixes from this release:

  • Updates and fixes UCPath Contact Data into AggieService. 
    • Revised UCPath Contacts Jobs data filters order based on Effective Date and Employee Record. 
    • Revised UCPath Contacts Legal Name and Job data not integrating in some employee AggieService contact pages.
  • Updated client forms to accept both old KFS & new Chart of Accounts (CoA) Regex Expressions.
  • Added new CoA Regex validation into case forms backend.
  • Added HTTP Connector to the new CoA endpoint.
  • AUSS-C Case Assignment Rule Changes

November 29, 2023

Most recent improvements and fixes are as follows:

  • Fix was put into Production to map IAM Email Field MetaData to correctly populate AggieService Contact’s Campus Emails that were appearing as blank.
  • ELR Change Request Form underwent critical updates and went into Production. 
  • Retire (decommission) What is your question? field from cases created by email. The body of email now maps to the Description field. 
  • Service Level Agreement (SLA) Stage logic to stop setting an SLA as primary that is dependent on other SLAs (deactivate).
  • Service Level Agreement (SLA) Stage logic to stop removing an SLA set as primary that has no dependent SLAs (activate).
  • Flow rule fix: Point of Contact Campus Email will not be blank when the Point-of-Contact (POC) name has a look up value.
  • Retire (decommission) Date Signed field. 
  • Developed standard operating procedures for Disaster Recovery Process, in which long term or permanent critical systems failure or data loss is preventing the Aggieservice application from performing its core functions.
  • Qualtrics Flow - 3 Qualtrics Workflows rules merged into one Flow.
    • Upon closing a non ELR case, the Submitter and if there is a Point-of-Contact (POC) they will receive an SSO Satisfaction Survey email to their inbox. 
    • Upon closing ELR case record types ELR Discipline - Skelly, ELR Personnel Action, ELR General Inquiry, and ELR Notice, the Submitter will receive an ELR Satisfaction Survey email to their inbox. 
  • Migrate Workflow Rules to Flows.
    • Case Email / Comment sent in case updates three fields - (i)Last Comment Posted, (ii)Last Comment Channel, (iii)Last Modified by. 
    • If New Hire Email is NOT Blank and either Send New Employee Onboarding Email or Send Current Employee Onboarding Email is checked an email is sent to New Hire. 
    • Retire (decommission) Workflow rule "Basecamp cases to UCPath Basecamp queue" due to being a duplication of existing rule where cases created by basecamp@ucdavis.edu  emails are already configured to assign to UCPath Basecamp queue. 
    • Cases created by email benefits@ucdavis.edu to be assigned Case Record Type: Ask a Question, Request Type: Benefits, and Case Origin: Email - Benefits.