Symptom
Customers will need to migrate from DPCS 1.0 to DPCS 2.0 before this feature sunset in the Recruiting Module.
Resolution
Customers who are still using DPCS 1.0 will need to migrate before this feature is depreciated. Please feel free to contact your Partner to complete this migration.
For customers who does not have a Partner at the moment, please create an incident for the Support Team and make sure to provide the following:
- The case will need to be created under the following component: LOD-SF-RCM-ADM
- Provide the Customer approval form (fill in and sign). See Attachment section.
- The case will be created as low priority (P4)
Please note that Support will only perform the switch from DPCS 1.0 to DPCS 2.0 on the back end, here are the remaining steps that the customer will need to perform:
- See Procedure section on the following link :see here
- Make sure that the correct permissions has been granted, Click Here
- Select the following filters: Recruiting as Component and type consent under permission name, see screenshot below:
IMPORTANT NOTE : Make sure that the configuration is adjusted once DPCS 2.0 is enabled to avoid any error in the system.
See Also
Keywords
DPCS 1, DPCS 2, DPCS 1.0, DPCS 2.0 , KBA , LOD-SF-RCM-ADM , Admin Center, RBP, Permissions and Settings , Product Enhancement
Product
Attachments
Migration_customer_approval_form.docx |