Appearance
Check Configuration and field validation
Check Configuration checks whether an employment job or services proposal is ready for a person to apply, receive a contract, and send data to any enabled integrations.
PICMI runs this check when you select Check Configuration. It is also run automatically when you send an invite, duplicate an opportunity, make an offer, or complete an application.
note
Users see this as Check Configuration. Behind the scenes, PICMI is validating the fields needed by the workflow, contract template, opportunity, organisation, and integrations.
Check Configuration has failed and there is a field with Not found in the Passed column
If any fields show in the Passed column Not found and the Source column has Integration, PICMI cannot find where that required value should come from.
The most likely cause is a duplicate workflow question. The question may exist, but the active workflow or integration mapping may be referencing a different question with the same name.
For example, with PayHero, KiwiSaver fields usually need to come from workflow question fields. If those questions are missing, removed, or not mapped, the integration cannot pass Check Configuration.
To fix this:
- Check the opportunity has the correct workflow
- Check the workflow includes the required questions or information fields from the Title column
- Check whether there are duplicate questions with the same name
- Check the integration mapping points to the question used by the workflow, not another duplicate
- If the integration should not be used for this opportunity, turn it off or remove that integration setting
Save the changes and run Check Configuration again
See Managing Duplicate Questions for more detail.
note
A field can pass even if the participant has not answered it yet. Check Configuration is checking that the field has a valid source, not that the participant has already supplied the value.
Run Check Configuration
Check a job or proposal
- Go to either:
- Employment > Jobs
- Services > Proposals
- Locate the opportunity row
- Click ⋮ (vertical dots) to open the menu
- Select Check Configuration
- Click Check Configuration in the dialog
- Use Hide Passed to focus on rows that need action
- Fix any failed rows, save the changes, and run Check Configuration again
Read the results
| Column | Meaning |
|---|---|
| Title | Field being checked |
| Passed | means it passed. Not found, Empty, or Not Available failed. |
| Group | Area the field belongs to, such as Organisation, Job, Personal, PayHero, or another integration |
| Source | Whether the field is needed for the Contract or an Integration |
| Current Value | The value or source PICMI can currently use |
| Description | Extra detail about what the field is for |
What Check Configuration checks
Check Configuration reviews:
- the application workflow
- the contract template in the workflow
- organisation details needed by the contract
- opportunity/job details, including remuneration
- active integrations on the opportunity
- required integration mappings and default values
It does not check answers that only exist later, after the participant completes the workflow.
note
Use workflow Review mode when you need to audit the workflow's pages, item order, participant text, descriptions, choices, required state, and Library Item usage. Use Check Configuration when you need to confirm an opportunity can use the workflow, contract, opportunity fields, and integrations correctly.
Failed contract fields
Empty
Empty means a contract field is required, but the opportunity or organisation has no value for it yet.
Check:
- organisation profile/details
- opportunity title, location, dates, and work details
- remuneration or pay rate fields
- information fields used in the contract template
Add the missing value, save, and run Check Configuration again.
Not Available
Not Available means the contract template contains a field that does not apply to this opportunity type.
This can happen when:
- an employment contract template is used for a service proposal
- a service agreement template is used for an employment job
- a custom template includes fields for the wrong recipient type
Check the opportunity type and the contract template attached to the workflow. Replace the template or remove the incompatible fields.
Missing or multiple contract templates
The workflow must have exactly one contract template.
If the workflow has no contract template, add the correct contract step. If it has more than one, keep the correct one and remove the duplicate or outdated template.
Missing workflow
The opportunity must have an application workflow before PICMI can check contract fields or integration fields.
Open the opportunity, select or create the correct workflow, save, and run Check Configuration again.
Failed integration fields
Not found
Not found means an enabled integration requires this field, but PICMI cannot find a valid source.
If the missing value should come from a workflow question, this is most often caused by duplicate questions. A person may see the right question name in the workflow or mapping, but PICMI may be referencing a different question with the same name.
The source might need to be:
- a workflow question
- a personal or information field in the workflow
- an organisation field
- an opportunity/job field
- an integration configuration value
- a default integration value
Review the integration settings for the opportunity, update the mapping, save, and run Check Configuration again.
note
If a mapped workflow question was deleted or replaced, the mapping may need to be updated even though the integration was previously working. If there are duplicate questions, check that the mapping points to the same question used by the workflow.
Successful rows that need no action
Some rows may pass without showing an actual participant value, but there is an entry in the Current Value column.
| Current Value | Meaning |
|---|---|
| Workflow (Question) | The participant will answer this in the workflow |
| Workflow (Personal) | The value will come from a personal or information field |
| Opportunity | The value will come from the job or proposal |
| Integration (Configuration) | The value will come from integration settings |
| Default (Integration Setting) | The integration supplies a default value |
| Optional (Not Used) | The field is optional and does not need a value |
| Excluded | The field is intentionally excluded by configuration |