Data sync (form)
The “New sync job” screen (or “Edit sync job” when you open an existing one) sets up a connector that moves data between goPrevina and another company system. When editing, the job has two tabs: “Settings” and “Runs”.
1. Job details
Enter a “Name”. In “Integration” choose the external system (only integrations set up with a data connector appear; if there are none it says “No integrations configured”). In “Direction” choose “Pull (import)” to bring data into goPrevina, “Push (export)” to send it out or “Pull + Push” for both. In “Schedule (cron)” type the expression in UTC (for example, 0 6 * * * for every day at 6:00); leave it empty to run by hand only, and tick “Schedule enabled” for the schedule to work.
2. Destination and export
“Destination” decides what an import does: “Staging records only” leaves the data in an intermediate table, and “Workforce (workers)” hires, updates and removes workers on each run. With “Workforce (workers)”, “Maximum leavers per run (%)” appears: a full load that would remove more workers than that percentage is “blocked” and writes nothing.
If the direction includes export, tick “Allow export (writes to the external system)” and choose “What to export”: the synced rows, training, medical aptitude (fitness result and validity only, no clinical data), incidents or preventive measures.
3. Alerts
In “Alerts” set “Alert after this many failed runs in a row”, “Alert when no run succeeded in (hours)” (empty = no window check) and “Send alerts to”, with e-mail addresses separated by commas; new jobs start with yours. Open alerts are shown in “Integration monitoring”.
4. Field mappings
In “Field mappings” press “Add mapping” for each piece of data: the “Source field” (or “External field” if you export), the “goPrevina field”, and a “Transform” if needed (trim spaces, upper case, lower case, ISO date, default value). Mark one as the “Key”: it is the field used to recognise whether a record already exists, so it is updated instead of duplicated. You cannot save without a mapping marked as key.
To avoid starting from nothing, choose “Start from a payroll preset” (for example A3 Nom, Sage or Meta4) and check its column names against the first line of your file. “Save these mappings as a profile” stores them under a name; the chosen “Mapping profile” is shared: on saving, the mappings change in every job that uses it.
5. Save, dry run and review runs
“Save” stores the settings. On a saved job, “Run now” runs it at once and “Dry run” performs a test run that writes nothing. The “Runs” tab shows the “Run history”: start, status (running, succeeded, partial, failed or blocked), records read, written and failed, and the errors; dry runs carry the “dry run” tag. On a workforce job, the same tab lists the “Workers to review”: doubtful matches on national ID or name, for which you choose “It is a new person”, “It is …” (an existing worker) or “Leave it out”.