FIX UPDATES - Archive
August 15, 2024
Summary
In July, we saw continuous improvements with 7 Jira tickets closed. Completing the Campus Student Recruitment Project remains a priority and is moving towards completion as milestone and task timelines are refined. With that, we were still able resolve additional client issues as they arose:
Submitters were unable to see Summer Compensation field in AggieService Community portal. Fixed.
We created a new Email-To-Case: JBTemplates@ucdavis.edu for Health submitters to Job Builder.
Postdoctoral Appointments Form ID 230 - Qualifying Degree Date failing validation. Fixed.
Documentation : Updated CSV File Mapping Document with latest updates.
Request Access cases were being created with no submitter name. Fixed.
Aggie Service: Benefits Case Creation Response Email - Wording Update
----------------------
We are currently looking into an issue with submitter email addresses not populating in new and reply emails
In CAB we will be discussing further case changes to optimize the CoA process
We’re working to fix an approval reminder link directing users into Salesforce Classic
DocuSign is now available within Aggie Service cases and is currently being tested by a pilot group.
Important improvements pending release:
- Implementing logic to handle multiple child cases from one parent case
- Updating Additional Employment and Onboarding case forms – repeatable supervisor field logic
Continuing projects
- Health LOA team to transition into using AggieService for their workflows.
- Further enhancements of Student and Graduate Recruitment forms to accommodate multiple positions.
July 10, 2024
Summary
In June, we saw continuous improvements, with 8 tasks closed. The Campus Student Recruitment project remains a primary focus; however, we were able make additional client contributions along the way.
We adjusted Leaves case email functionality.
A new HR Coordinator queue with case assignment rules was created.
In late-June we experienced a system-wide issue due to student recruitment form changes, which affected visibility of fields in the Case Owner Console. The impact precipitated a redesign of case details across all forms: case details are now grouped in sections. Due to the immediacy of the issue, we had no window of opportunity for change management protocols, and greatly apologize for any impacts.
Bug fixes: First-Name, Last_Name, Timesheet_Identifier, HRC_Comments, and Location didn’t have strict typing; Cases timing out upon submission; “isValidUCDEmail” was not recognizing special characters.
We made modifications to the Email Template to look better and updated the CSV file per the HRC team.
The Service Desk and Development teams continued to promptly address any Funding Chart of Account issues that arose within Aggie Service, and recently updated the Aggie Enterprise validator logic.
The Student Recruitment initiative continues to span multiple sprints: we are currently focusing on the onboarding timeline with milestones, tasks, multiple hire functionality, and auto-notifications.
DocuSign is now available within Aggie Service cases and is currently being tested by a pilot group.
Important improvements pending release:
- Implementing logic to handle multiple child cases from one parent case
- Updating Additional Employment and Onboarding case forms – repeatable supervisor field logic
Continuing projects
- Health LOA team to transition into using AggieService for their workflows.
- Further enhancements of Student and Graduate Recruitment forms to accommodate multiple positions.
June 14, 2024
Summary
In May, we saw continuous improvements, with 1 bug report, 2 user stories and 10 tasks closed. Improvements covered student recruitment enhancements, chart of account (CoA) field form updates and upgrade of community user licenses.
We are continuously monitoring our forms for performance improvements. Bug fixes addressed case field visibility issues tied to the upgrade of community user licenses. We ensured there was no difference between the previous version of the community license and upgrade.
Enhancements to the Student Recruitment Process is a work-in-progress, and spanning multiple sprints. Case Detail section fields that have migrated to Associated Record have now been made read-only in preparation to be removed in the next phase with exceptions. DocuSign is now available and is currently being tested by a pilot group.
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. Recruitment forms were updated to have only one required instance of Chart of Accounts and the second as conditional. The IT Development team met with the Aggie Enterprise team to continue to look at ways to improve user experience in AggieService.
Important improvements and fixes from this release:
- Implemented updates to the Leaves form and case record type to continue Health LOA transition into AggieService.
- Updated Health LOA case visibility among team members.
- Case assignment rule changes were completed for SSO HR and AUSSC team.
Continuing 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.
May 21, 2024
Summary
In April, we saw continuous improvements, with 2 bug reports, 0 user stories and 3 tasks closed. Improvements covered mapping bugs, chart of account (CoA) field form updates and system integration updates.
We are continuously monitoring our forms for performance improvements. Bug fixes addressed student recruitment form case request type not mapping to cases for service providers and case creation automated emails not sending. Issues with new department accounts not integrating in AggieService and not appearing in the form’s dynamic lookup was resolved.
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. Reclassification and Position Update forms were updated to have the Chart of Accounts field as conditional.
Important improvements and fixes from this release:
- Implemented updates to the Subtype categories for Campus ELR cases.
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.
April 12, 2024
Summary
In March, we saw continuous improvements, with 3 bug reports, 1 user stories and 3 tasks closed. Improvements covered mapping bugs, chart of account (CoA) string validation updates, and system coding updates.
We are continuously monitoring our forms for performance improvements. Bug fixes addressed form attachments not mapping to cases for service providers and home department routing issues. Enhancements to the Student Recruitment Process is a work-in-progress, and spanning multiple sprints. This sprint, technical tasks were outlined based on Student Recruitment Process requirements gathering and user stories.
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. In addition to current CoAs format validation, AggieService implemented CoA validation against active CoAs in Aggie Enterprise.
Important improvements and fixes from this release:
- Workers Compensation transition concluded. All outstanding action items have been completed.
- Implemented additional Subtype categories for Campus ELR cases.
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.
- Health Compensation to transition into using AggieService for one of their work flows related to JDX rollout.
February 28th, 2024
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
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
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.