If vacancies don't appear in Access Recruit after you create them in SelectHR, to ensure your vacancy record processes correctly, check each of the following.
Enable requisitions in Access Recruit
To enable a requisition to appear, follow the steps below in Access Recruit.
Click Positions then click Openings.
Click My Openings then click New.
Select position opening template [with requisition].
Select the relevant requisition.
Once you've done this, move on to the next section.
Check the Service Administrator
Your Service Administrator may have stopped running, which prevents the records from sending to Access Recruit.
If you're hosted with Access, raise a new case online and reference the title of this article.
If you aren't hosted with Access, please request that your IT department check the Service Administrator is operational.
Once you've done this, move on to the next section.
Check for errors in the batch job
If you're confident the vacancy is created and approved in SelectHR, follow the steps below.
Log into the SelectHR Admin Tool.
Click Batch Jobs then click the batch job relevant to your version:
Versions 3.3 and below: aCloud Recruitment - Vacancy
Version 4.0: Access Recruit - Vacancy
Click View the log for the selected batch job.
Click View Workflow Log then double-click the record at the top.
No error messages present
If there are no error messages in the batch job, this suggests there may be data missing from the record. Required values are:
Position Reason Number must be populated.
Requisition Template Number must be populated.
Requisition Reference must be populated.
Date Opened must be populated.
Number of vacancies must be greater than zero.
Workflow must be greater than zero and the vacancy must be approved.
Date Closed must be on or after today, or not populated.
To ensure the vacancy record meets the minimum requirements, follow the steps below.
Log into the SelectHR Admin Tool.
Click Import/Export Data then click Create an export definition.
Click Select the data to export then set the database to SelectHR.
Log in then copy the following SQL:
SELECT VD.[Vacancy Number],
VD.[Vacancy Unique Name],
VD.[Date Opened],
VD.[Date Closed],
VD.[Number of Vacancies],
VD.[Position Reason Number],
VD.[Requisition Template Number],
VD.[Requisition Reference],
VD.Workflow,
VD.[Requisition UUID],
VD.[Sent to CWN],
VD.[Request Date]
FROM Vacancy.Details VD
WHERE VD.[Date Opened] IS NOT NULL AND (VD.[Date Closed] >= GetDate() OR VD.[Date Closed] IS NULL) AND VD.[Number of Vacancies] > 0 AND VD.[Position Reason Number] IS NOT NULL AND VD.[Requisition Template Number] IS NOT NULL AND VD.[Requisition Reference] IS NOT NULL AND VD.Workflow > 0
ORDER BY VD.[Vacancy Number] DESCClick Options then click Paste SQL from clipboard.
Click Data.
If the vacancy that didn't send isn't on this list, the requirements haven't been met. In this case, check the vacancy record and complete the minimum requirements.
If the vacancy is on the list, move on to the next section.
Mark the vacancy for resubmission
If SelectHR fails to process a vacancy record due to an error, it won't attempt to process the record again. To mark the record for resubmission, follow the steps below.
Click Recruitment then click Recruitment.
Click Vacancy Management then select the relevant record.
In the Opening date field, increase the date by one day.
Click Save then, in the Opening date field, change the date back.
Click Save.
Once you've done this, if the vacancy still doesn't submit, raise a new case online and reference the title of this article.
Common errors and resolutions
Error | Recommended solution |
AccessSelect.Changeworknow.dll, Class: ChangeworknowEventHandlers, Method: ProcessVacanciesForAllChangeworknowServers |
|
The 'Number_of_Vacancies' property on 'Vacancy_Request' could not be set to a 'null' value. You must set this property to a non-null value of type 'System.Int32'. | Ensure you've populated the Number of Vacancies field with a number greater than zero. |
Event "OnAccept" on interface type "...IWorkflowService" for instance id "..." cannot be delivered. | This indicates that the workflow failed during the Accept stage, and the vacancy is pending, with no way to progress it.
We recommend you re-raise the vacancy request. |
If you've tried the solution for the relevant error but the error still appears, raise a new case online and reference the title of this article.