Dynamic Core Fields
Dynamic Core Fields (DCF) streamline the job posting process by providing a way to populate common Extra Fields across different Portals.
While not mandatory, DCFs may simplify the integration and limit the number of choices users need to make when interacting with Extra Fields. You can identify DCFs using the Portal's detailed information method. Each <extrafield> XML element associated with a DCF will have a dynfield attribute when retrieving Portal data - consult the Extra Fields section for more details.
DCFs aggregate frequently used data from Portal-specific Extra Fields while still allowing per-Portal customization when needed.
If a DCF is included in the XML payload, and the destination Portals use that DCF, the provided value will populate each corresponding Portal's Extra Field - unless the latter is already provided under that Portal's <board> element as an <extrafield> on its own (in which case such individual Extra Field will take priority).
For example, most Portals allow providing an Application URL - an external page where candidates are redirected to apply instead of using the job board's native form. By using the app_url DCF, you can send a link to your system's application page dedicated to the given Job, allowing to specify screening questions and better control the application process (and bypassing idibu's Applicant Management entirely). The link would then populate the Application URL Extra Field on all Portals that support it. However, the extra convenience is that you can still provide a Portal-specific Application URL in each Portal's individual Extra Field, if you find it necessary to track the source of the candidates.
Similar to the Core Fields, DCFs are provided under the <job> element.
Disclaimer: Portal behavior with the DCFs may vary. idibu does not track these variations.
Fields description
| XML element | Type restrictions | Required? | Notes |
|---|---|---|---|
app_url | String (URL) | No | URL of an external page to which candidates will be redirected instead of using the Portal's default application functionality. Please consult this section for more info. |
salaryOverride | String | No | Textual description of the salary. On the majority of applicable Portals, this will replace the display of the full salary information while still using the other salary fields for search. |
startDateOverride | String | No | Textual description of when the candidate would begin working. On the majority of applicable Portals, this will replace the date provided in the startdate Core Field. |
Format
The below format only details the Dynamic Core Fields. For the full list of fields that go under the <job> element, refer to the Job Section.
<job>
<app_url>[string:url]</app_url>
<salaryOverride>[string]</salaryOverride>
<startDateOverride>[string]</startDateOverride>
</job>
Example
The below format only details the Dynamic Core Fields. For a full <job> example, refer to the Job Section.
<job>
<app_url><![CDATA[https://www.idibu.com]]></app_url>
<salaryOverride><![CDATA[Textual salary override]]></salaryOverride>
<startDateOverride><![CDATA[Textual start date override]]></startDateOverride>
</job>