on 10-23-2014 10:07 AM
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:
What can be done to avoid giving enlarged authorizations to agency users?
Would greatly appreciate if you cold help with these answers.
Best Regards,
Shyamu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Waldemar,
Thanks. Its a good approach. I've experimented with gmail and I agree this will work if all the agencies use gmail as the provider. That, unfortunately, won't be the case. Most agencies will have their own domains and some would use their ISP's mailbox service.
I would welcome more thoughts to see where we can take this. As mentioned by a fellow member, SAP E-Recruiting is highly limited in functionality (practically zero!) when it comes to agencies.
Regards,
Shyamu
SAP E-recruitment is highly expandable as I am experiencing just now, so you can find the smart solution even for things that seems to be the fundamental change.
I like however to recommend you to ask at least two or three vendors because the proposed solutions may differ a lot all in terms of scale and of course of the cost.
User | Count |
---|---|
6 | |
6 | |
3 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.