Hello Members,
I have a scenario where I need your advice. I'm implementing E-Recruiting (EhP5) using the distributed scenario - front-end on one box and backend on the ERP box. I need to have agencies created applications on behalf of their proposed candidates.
What I want to do:
1. Allow agencies to create applications
2. Force all correspondence to go to agencies instead of candidates
Where I'm stumbling:
The distributed scenario still means that data is stored in the backend. In this case, how does the following happen:
- Agency user creation. Since E-Recruiting administrator will create agency users in the Portal (backend), how does this get replicated to the front-end to agency users to logon? I'm aware this is similar to external candidate users but I would like to know exactly how the system manages this.
- When creating an application as an agency, the system is asking for authorization to create user and assign them to user groups. This authorization cannot be given to anyone except for a group of administrators in the company.
What can be done to avoid giving enlarged authorizations to agency users?
- Unable to fathom the data exchange/ replication between front-end and backend. Since all data is stored in the backend, how does duplication check work?
- When I try to assign a support group to the agency, the system throws an error. The customer is using a Plan Version different from 01. It seems 01 is hard-coded in the system as the table T77RCF_AGENCY stored the support group as <plan version>NG<support group ID>. Example: PDNG56999577.
Would greatly appreciate if you cold help with these answers.
Best Regards,
Shyamu