This page outlines details of transitioning SPs to leverage UCPath EMPLID as part of the UCPath go live process.
| SP Name | EMPLID Required? | Attribute Replaced by EMPLID | Transition to EMPLID (without impacting users) | Notes | Locations |
|---|---|---|---|---|---|
| Connexxus (travel) | Only for locations relying on UCPath-provided data feeds. | ePPN | UC Travel staff will reach out to IAM teams to coordinate transition in advance each location's UCPath go live. Location provides an ePPN=>EMPLID cross walk file immediately after UCPath final conversion. Travel office, travel vendor and location coordinate update of user profiles and SSO changes shortly after go live. | Not every location leverages the UCPath-provided Connexxus travel feeds. Because the vendor starts receiving data feeds from UCPath immediately post location go-live, this conversion and SSO change needs to be made very shortly after UCPath go live. Locations not leveraging the UCPath feed may still require updates to SSO or data feed configurations post-UCPath go-live. | ALL(ish) |
| UC Decision Support (UCDSS) aka UC Report Center | EMPLID is required for access to prod UCPath data/reports. | N/A ePPN is primary user identifier. EMPLID is a secondary ID used to map user to UCPath-defined permissions. | To ensure user access to UCPath reports, EMPLID should be released as soon as possible after UCPath conversion/go live. Because ePPN is the user's primary ID, you can release EMPLID at any time without impacting existing users. | EMPLID is captured and added to the user's profile as part of any user login event. Therefore, it can be added to the SSO release at any time after production EMPLIDs are available and updates should be seamless. Some locations/users already use UCDSS for non-UCPath reporting purposes (without EMPLID being released or required). | ALL |
| UC Decision Support QA (UCDSSQA) aka UC Report Center QA | Pre-UCPath go live, access is required, without EMPLID. Post go-live, EMPLID is required. | N/A ePPN is primary user identifier. EMPLID is a secondary ID used to map user to UCPath-defined permissions. | Post-go live, EMPLID should be added to the list of SSO released attributes, as location testers will still need access for testing of UCPath reports after the location is live on UCPath. | For pre-UCPath go-live testing, UCDSSQA application owners manually add report permissions to the user's profile. | ALL |
| Effort Reporting System (ERS) | Eventually, but not immediately | PPS ID | ERS will only transition to EMPLID at the end of an effort reporting period, at which time they will reach out to locations. At UCPath go live, users will continue to be identified with the existing PPS ID until the end of that reporting period. | It's understood that some (new) users may get hired post UCPath go live, and end up needing access during a reporting period (but not having a PPS ID). ERS will work around this internally. ERS will reach out to locations at the end of ERS reporting periods to coordinate the SSO changeover. (ERS reporting periods may vary between locations) | ALL |
| UCPath Production | Yes | N/A (access requires EMPLID) | This transition is part of the go-live activities coordinated with UCPath. | ALL | |
| UCPath "P-stack" | Yes | N/A (access requires EMPLID) | ALL | ||
| i9 Complete/Tracker | Yes | PPS ID or a Local account | EMPLID supercedes PPS ID as userID. SSO change needs to be coordinated with UCOP Systemwide HR Compliance team (so HR can update the user Tracker profiles with EMPLIDs) concurrent with SSO change. | ALL | |
| Job Builder | Yes | UCNetID | Should be seamless, no coordination required with the application owner to add EMPLID to the release. | Job Builder matches SAML attributes to source data from UCPath/PPS, so adding EMPLID to the assertions will not break user access. | ANR UCB UCM UCOP UCSB UCSC UCSF |
| UC Outside Activity Tracker | Yes, but not immediately at UCPath go live | PPS ID | ??? | ||
| UCPath D1 Cognos Training | No | N/A | N/A | UCPath D1 Cognos Training has been replaced by UCDSSQA for now. If the Cognos Training environment is re-deployed, we will follow up with locations at that time. | None |
| Family Member Eligibility Verification (UnifyHR) | Yes | PPS ID or a Local account | EMPLID supercedes PPS ID as userID. SSO change needs to be coordinated with UCOP Systemwide HR Compliance team (so HR can update the user Unify profiles with EMPLIDs) concurrent with SSO change. | Not all locations are using SSO, app has the ability to manage local accounts for pre-UCPath locations. | ALL (except ANR) |
| Redwood Roots | Yes | UCNetID | EMPLID supercedes UCNetID as userID. SSO change needs to be coordinated with application team (so app team can update the user profiles with EMPLID) concurrent with SSO change. |