In Agency 2.0 the Company ID and Agency ID fields at login have been split up. Until now the Agency ID was constructed as "companyID:agencyID", now they need to be typed in separetely into two separate sections.
However, the token [[AGENCY_ID]] still prepopulated agency ID in the old format "companyID:agencyID" .
SuccessFactors BizX - Recruiting Management(RCM) - 1908
Reproducing the Issue
- Log in to the instance and Go to Set-up Agency Access.
- Create new Agency and add Agency User.
- The email notification gets triggered with the token [[AgencyID]] in the format as "companyID:agencyID" .
Currently this has been identified as an escape issue and our engineering team are working on correcting the same. As of now the fix for this is planned for 1911 Q4 version, we will be updating the latest fix date in the article, please follow for the same.
For now, Agency Users need to be informed that the Agency ID generated has to be broken down while trying to access in Agency 2.0 portal.
Tip to share the information with already Active Users (while token is enhanced): you can obtain the list of users who are added to agencies and who are therefore affected by this change by creating an Ad-Hoc report. Please see KBA 2837392 for more information.
Tip to share the information with new users: you can add a note in the email template linked to recruiting trigger "New Agency User Alert" (example below), so new users will understand that they are required to put the company ID in a separated field from the agency ID.
Note: until now the Agency ID was constructed as "companyID:agencyID", now they need to be typed into two separate sections.
2836512- Agency 2.0 Login Page now requires the Company ID - Recruiting Management
[[AgencyID]] , Agency 2.0, Agency token, agency portal , KBA , LOD-SF-RCM-POR , Career and Agency Portals , Problem