Welcome to volume 2 of my 'being kicked by a recruitment api' . .Again this is more of a heads-up than anything but i'd welcome experience from elsewhere... . .Still here at a well-known establishment for maintaining the Nations Health using this custom recruitment interface that extracts vacancies and imports applicants to these vacancies. . .This one is a bit less windy that my previous post (honest). . .If an existing applicant applies for a second vacancy then we use the following api .hr_assignment_api.create_secondary_apl_asg . .However in certain circumstances we get back the following error: .HR_51281_ASG_INV_VAC_REC - essentially this means an invalid recruiter error. . .Closer examination reveals that the api compares the recruiter_id of the vacancy being applied for with the recruiter_id on the existing vacancy. If they are different then it raises this error. . .For a small company this may be true. You may only have a single person responsible for all your recruitment needs. For "the well known establishment responsible for maintaining the health of the nation" they have vast teams of people responsible for their recruitment activities. THey have 1000's of vacancies being managed by many different recruiters. . .So I duly raised a TAR (4223231.999). After much too-ing and fro-ing they tell me that I should supply the recruiter_id as part of the API call! . . :evil: EXCUSE ME BUT. :evil: .. if the recruiter_id is so damm important that the API call will fail if it's not supplied why is it not a FECKING mandatory parameter??? . .I of course responded in the TAR in a slightly more controller manner and tone...I've yet to recieve a reply but it has had a Bug raised against it now!

As a footnote to this. .The TAR has now been closed as the work-around solves the problem. .The Bug is now a P3 so may never make the light of day.