This guide explains how the AI job description features use your configured choice lists, the recommended way to set things up for the best results, and what to expect from each feature.
Create Job with AI and Revise with AI are two different features that work differently. Different configuration matters for each, and some behavior applies to one but not the other. They are documented separately below — read the section for the feature you care about.
1. Overview
Create Job with AI — generates a whole draft job description from a job title.
Revise with AI — rewrites a single section of an existing job description.
Both can use your choice lists (dropdown options like Education Level or Experience Level) so the AI fills those dropdowns with your values rather than generic defaults — but they obtain and enforce those choice lists by different mechanisms.
How strictly the AI sticks to your choice list — two modes referenced throughout this guide:
Guaranteed — the AI can only return values that are exactly on your choice list. It cannot invent or substitute anything.
Best-match — the AI is shown your list and asked to use it, but it can return something else. The system then matches its answer to the closest value on your list. If nothing matches, that field may come back blank or with an unexpected value.
2. Create Job with AI
How it uses your configuration
When generating a new job, the system scans your default master template's building blocks and collects the choice lists from the relevant ones (Education, Licenses & Certifications, Work Experience) to send to the AI.
Required configuration (per building block you want populated)
A content binding — an AI Content binding, or (if that isn't set) the block's Job Posting binding as a fallback. This does two things: it marks the block as one to gather a choice list from, and it tells the system what content type the block is (Education / Licenses / Experience) so the values land in the right place. Without a binding, the block's choice list is not sent, and the AI falls back to generic defaults.
"Send as Background Info to AI" enabled on the block. For Create Job with AI, this flag is the opt-in that allows the block's choice list to be sent. If it is off, that block's list isn't included in generation.
Column designations (Content Settings) — in the Bullet List Designer → Content Settings tab, designate the level dropdown as Main and the Required/Preferred dropdown as Required/Preferred — so the right columns' choice lists are sent and the AI's answer maps back correctly. (The Details column is free-form text the AI writes — there is no choice list there, so it is not one of the designations that matter for choice-list behavior.)
How it behaves
Create Job with AI is always best-match (see the modes above): the AI is shown your options and asked to use them, but it is not forced to, and its answer is matched back to your list. It is never guaranteed to your exact list. The best match rate comes from good configuration plus clean, meaningful values (see Section 4).
3. Revise with AI
Prerequisite: a block must have "Data can be Revised with AI" enabled to offer the Revise option in the first place.
How it uses your configuration
Revise operates on one section at a time and takes the choice list directly from the building block you are revising — it does not use the content binding or the gathering process that Create Job with AI uses.
Nothing special is needed for the block's own choice list. Because revise reads the choice list straight off the block being revised, you do not need a content binding or the "Send as Background Info to AI" flag on that block for its options to be used.
"Send as Background Info to AI" has a different purpose here. For revise, this flag on other building blocks controls whether those blocks' content is shared as background context to help the revision (for example, letting the AI see the Summary while revising Experience). It is not about the choice list of the block you are revising.
Column designations work the same as in Create Job with AI (see Section 2) — the level dropdown as Main, and the Required/Preferred dropdown designated — so the AI's result maps back into the correct columns.
Required configuration (per building block you want populated)
Column designations (Content Settings) — in the Bullet List Designer → Content Settings tab, designate the level dropdown as Main and the Required/Preferred dropdown as Required/Preferred — so the right columns' choice lists are sent and the AI's answer maps back correctly. (The Details column is free-form text the AI writes — there is no choice list there, so it is not one of the designations that matter for choice-list behavior.)
How it behaves
For small, clean choice lists, the result is Guaranteed: the AI can only return values that are actually on your list — it cannot substitute anything else.
It switches to best-match when the list is very large (about 1,000+ options) or contains certain characters (
"or\). In those cases the AI cannot be locked to your list, so it is guided and its answer is matched back instead. This is a limitation of the AI engine, not a defect.Why this matters: Revise can guarantee on-list values for small, clean lists, whereas Create Job with AI is always best-match. Expect tighter adherence to your list in Revise.
4. Choice-list value guidance (applies to both features)
Avoid
"(double-quote) and\(backslash) in choice values. They prevent the Guaranteed mode in Revise and are almost always accidental. The system still works in best-match mode, but adherence is looser.Use meaningful labels. "Bachelor's Degree" guides the AI far better than "Level 2."
Include a blank/empty option where "no selection" is valid (for example, an and/or connector column), so the AI is not forced to pick.
Very large lists (about 1,000+ options) cannot be Guaranteed — expect best-match rather than guaranteed on-list selection.
Typographic characters are preserved. En-dashes, em-dashes, curly quotes, and accents in your values are kept intact and matched correctly.
You can use your own values. The AI uses whatever values you have configured in your choice lists — you do not have to use the default values JDX ships with.
5. Setup checklists — making sure it works
Use these checklists to confirm a building block is set up so the feature works end to end. Most settings live on the block's edit dialog (the Settings, Access, and Data tabs); column designations live in the Bullet List Designer → Content Settings tab.
Revise with AI — getting the wand to appear and good results
The Revise (✨ wand) option only appears on a block when all of the following are true:
Generative AI is enabled for your organization.
The block's "Data can be Revised with AI" setting is checked.
The block is bound to a field — on the block's Data tab, Binding Type is set: either a bindable field, or User_Defined with a User-Defined Field selected.
The block's Input/Output Mode (on the Data tab) is "Get/Set Value". This is the one most people miss: if it is "Get Value Only" or "No Impact", the block is read-only — it only displays a value and can't be edited — so the wand will not appear. ("Set Value Only" also allows the wand.)
The block is one you can edit in the current mode (your edit permissions allow it and the block isn't locked or read-only by inheritance).
For bulleted lists, the block is not set to "use default rows only."
Note: "Send as Background Info to AI" is not required for the wand. That setting only shares a block's content as background context for other blocks' revisions — it does not control whether the wand appears.
To get your choice-list values into the result:
Designate the dropdown columns in Content Settings (Bullet List Designer → Content Settings tab): the level dropdown as Main, the Required/Preferred dropdown as Required/Preferred. Without this, the AI uses the default (out-of-the-box) options instead of yours.
Create Job with AI — getting sections populated in the new job
For a section to be generated and actually appear in the created job:
The block has a content binding — an AI Content binding, or its Job Posting binding (used as a fallback). This is required both for the choice list to be sent and for the generated content to have a place to land. Without a binding, a section may be generated but won't be written into the job.
"Send as Background Info to AI" is enabled on the block (the opt-in that allows its choice list to be sent).
Dropdown columns are designated in Content Settings (as above).
This applies to sections like Education, Experience, Licenses, and Essential Functions — if a section seems to generate but doesn't show up in the created job, check that the block has one of the bindings above.
6. Quick troubleshooting
No. | Issue | Resolution |
|---|---|---|
1 | Create Job with AI produces values that aren't in my choice lists | Verify the building block has the AI Mapping set. Verify that "Send as Background Info to AI" is selected for the building block. Verify the column designations exist in Content Settings (Bullet List Designer → Content Settings tab). |
2 | Revise with AI produces values that aren't in my choice lists | To ensure the choice list is guaranteed to match, verify that the choice list options for the block are not excessively long and there are no special characters ( |
3 | Fields are blank after accepting the AI results | Possibly a wrong or missing column designation in Content Settings (Bullet List Designer → Content Settings tab — Main / Required-Preferred), or the AI's value couldn't be matched to your list. Possibly not running in guaranteed mode (for revise) — see problem no. 2 above. |
4 | The Revise (✨ wand) doesn't appear on a block | Confirm Generative AI is enabled for your org, "Data can be Revised with AI" is checked, and the block is bound to a field. Most commonly, check the block's Input/Output Mode on the Data tab — it must be "Get/Set Value" (not "Get Value Only" or "No Impact"), otherwise the block is read-only and can't be revised. ("Send as Background Info to AI" is not required for the wand.) |
5 | A section generates in Create Job with AI but isn't in the created job | Confirm the block has a content binding — an AI Content binding, or its Job Posting binding as a fallback. Without a binding, the generated content has nowhere to land and is dropped. |
Comments
0 comments
Please sign in to leave a comment.