on ‎2013 May 28 9:06 AM
Hej gurus
We have encountered a strange error in our E-recruitment system, where rejection letters are not always sent, when a recruiter performs the rejection activity.
We have already performed many tests without finding a definite pattern.
We have also checked the workflows and there are never errors.
In one case the rejection letter is not generated, when the recruiter is logged in to the portal in one specific language.
In another case a recruiter performed several rejections for the same job within in the span of about half an hour, but in SOST we can see that only some of the candidates did not get a rejection letter. And there are no missing e-mail addresses on the candidates.
We have run out of ideas for where to look for the error. The only connection I can see is that it seems to have started right after a bunch of security notes were applied. I checked a couple of them which looked interesting (1738828 and 1597598), but it still makes no sense.
Does anyone have any idea where I could look for the problem?
Kind regards
Aage
Request clarification before answering.
UPDATE:
I have discovered that the status reason given in the rejection activity seems to determine if a rejection letter is sent or not.
Every time the reason recorded is "Hired using other requisition", then no letter is sent.
For other reasons such as "Underqualified" letters are sent.
Now my question is where can maintain these reasons, their translations and define which ones should generate a letter?
I cannot find it in IMG, so I am guessing it is part for workflows WS91800002 and WS51900005, but I am not proficient with workflows.
It also appears that "Hired through other requisition" gets defaulted with browser language "Danish", because the first letter in the translation is "A" and the dropdown list is sorted alphabetically.
Is it possible to change the default reason?
Kind regards
Aage
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aage,
Status reasons are defined in table T77RCF_RSN_CODE and assigned to the object types and statuses in VV77RCF_RCD2STAT.
Since EhP4 workflow WS51900005 is not used anymore but WS51900011. Nevertheless, here we just check for the acitivties created but not a special status reason behind it.
Regards,
Nicole
Thanks, Nicole
I am still waiting for an analysis from our external consultant, but all tests so far points to that the reason selected for the rejection activity determines if a letter is sent or not. What I mean is that we can find no other pattern.
We are in the process of upgrading from 604 to 606 and looking in SWI1 I can see that we are still using WS51900005. I am not sure what the consequences of this are though.
/Aage
| User | Count |
|---|---|
| 8 | |
| 3 | |
| 2 | |
| 2 | |
| 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.