As of June 2019, this page is no longer being maintained.
If you have questions on updates on the items listed in the "Requests/Defects/Known API issues" section, please send an email to eis-support@berkeley.edu and/or update the Service Now Incident number directly.
As of June 2019, this page is no longer being maintained. If you have questions, please send an email to eis-support@berkeley.edu and/or update the Service Now Incident number directly.
The API v3 is available in Production! We're now in "After Calnet", full capacity mode.
Here are key points:
This article will be updated after Employee API changes have been deployed to the UAT environment. The following key information is available via this article:
As we approach go-live, we want to give an update on how the UCPath transition will impact Recruitment. We have confirmed that TAM (our existing Talent Acquisition Management system) will remain up and active during the UCPath transition in March.
What this means for applicants:
The UCPath Project Team is working closely with other teams on campus involved in data reporting to provide more detailed information about reporting options for transactional users.
During the UCPath conversion scammers may try to send emails impersonating Payroll Services or Central HR. Be extra alert during this time of transition and do not open any attachments or click on any email links that look suspicious. If you think something looks suspect, report it to consult@berkeley.edu.
This message is to clarify a previous (now removed) post regarding credit union deductions that was misleading. We sincerely apologize for any inconvenience this may have caused.
The only payroll deduction data that will not get converted into the UCPath system are credit union "deductions" that are used for direct deposit purposes only. This only applies to credit union "deductions" that are in addition to a direct deposit to your primary institution.
The Employee API V3 has transitioned from a /test to /uat environment. The UAT API will facilitate access to UCPath data based on converted legacy HR production snapshot as of October 25 2018.
For those applications that are using the /v3/employees “changelog” endpoint you will start to see incremental and realtime changes. If your application had access to restricted data using the /test/ endpoints, please validate the restricted data continues to be visible in /uat.
During the Integration Testing (IT) Phase, developers have requested information about old and data value differences from the existing HCM system to the new UCPath system. While this list is not comprehensive, the UCPath Project and Technical teams have consolidated a few popular documents circulated for reference, in the course of application testing. Please send an email to ucpathtechinfo@lists.berkeley.edu for questions related to the API, and include
Federal law requires that every employer who recruits, refers for a fee, or hires an individual for employment in the United States must complete Form I-9, Employment Eligibility Verification to verify employees' identity and employment authorization.
An important inter-dependency of UC Berkeley’s integration with UCPath, is the implementation of Tracker I-9:
The UCPath Project training team is committed to providing UC Berkeley employees, managers/supervisors, and operational staff with the resources they need to successfully interact with the new UCPath system.
This article will be updated after Employee API changes have been deployed to the Test environment. The following key information is available via this article:
Information about Planned/Actual Deployment opportunities and Technical FAQs are accessible via the following hyperlinks.
There are important items to consider to ensure you're prepared for the transition to UCPath in March 2019.
Your personal information will be converted from the current HR systems into the new UCPath system. Be sure the right data is being converted!
Take the following steps to verify your personal information:
When UC Berkeley transitions to the UCPath system, many current processes for HR, payroll, personnel, and benefits transactions will change.
Here's a preliminary view at some, but not all, of the important changes when UCPath launches at UC Berkeley.
To navigate directly to the desired content, click on the anchor links below.
Currently, all employees who have set up an email address in At Your Service Online (AYSO) receive an email notification on payday stating the electronic statement is available.
After UCPath Go-Live, employees will no longer receive an email confirmation of deposit from UC Berkeley.
The Employee API is changing to support campus needs in conjunction with the UCPath project. The Enterprise Integration Services (EIS) team is working with the UC Path team, the developer community, and functional owners to refine requirements and test the next version of the API. The current version running in production, v (2), will be decommissioned in the near future.
The Employee v3 API is moving from a Development to a Test environment, in alignment with the UCPath Testing Timeline. This next Integration testing phase for the Employee V3 API is planned from mid-October to end of December. This phase is a precursor to the UCPath User Acceptance phase, slated to start January 2019.
As the API transitions from DEV to TEST, new URLs, as well as additional APIs are now available in TEST:
