AdenDesk Overview
|
|---|
| Note: |
The jobs posted on AdenDesk will be automatically published on Cadremploi, Keljob and CadresOnline. If client has a contract with pack distribution feature then CadresOnline board should be used - in which case jobs will be sent to other boards based on the distribution packs selected at the time the jobs are posted in eQuest system |
| Known Issues: |
Client needs to specify at the board setup in eQuest admin the method candidates should apply to their jobs based on the contract the client has with the board by setting up additionaldata 'CandidateResponses' to either 'Email' or 'URL'. |
| eQuest Pipeline ID: |
AdenDesk |
| Batch Type |
Full Replace |
| Delivery Time: |
9:07pm PST |
| HTML Allowed: |
no |
| Character Limit: |
no |
| Posting Period: |
35 days |
| Board Specific Data: |
yes |
| Special Requirements: |
-- |
| Needed for eQuest Setup: |
codeBDR |
| Other: |
AdenDesk requires a test file for each new customer with information about that client in the file in order to receive the below needed information. Therefore the client should use something like "test_codeBDR". We added an additional data named 'Testing' - this one needs to be switched to 'Yes' for the testing phase. The client needs to post a test job through our system. While in testing phase the delivery is email to 'flux@adenclassifieds.com'; once they receive the test file they provide us or the client with the valid CodeBDR. If the client doesn't want the test posting to go live we have to make sure they send a delete action before we switch 'Testing' to 'No' ('active' phase) and replace the values with the ones provided by the board. |
