Release overview
This release includes Temps Placements being exported to Mid-Office (MO), a new export to Tempest, and a Temps Dashboard using PowerBI, as well as several minor enhancements.
Temps placements can be exported to MO. Mandatory fields are checked by the service before they are exported, and valid Temps placements and their shifts are exported to MO. Temps Placement shifts can be viewed in MO.
A new integration has been created with Tempest. Confirmed placements are available for export to Tempest. When the export it run, you can select which placements you wish to export, and the export files are created. These files can then be imported into Tempest, or create new records or to update existing records.
Power BI offer dashboard functionality that can be shared within your organisation and displayed on large monitors to make users aware of various statistics. Infinity utilises this functionality by exporting the relevant data to OneDrive which can be viewed by Power BI. The initial version supports Temp placements only.
Other enhancements include changes to the way bespoke reports are viewed, and changes to the Exchange Sync audits.
Misc
Enhancement 61636 – Bespoke reports have had their description prefixed with 'This is a custom report, built to an individual client specification.'
This is to help users identify which reports are not core system reports, but rather are custom/bespoke reports that have been specified by or for a particular customer
Enhancement 54730 - New databases will not include bespoke reports and only contain the standard reports
Existing databases will continue to display both bespoke and standard reports.
If you wish to have the bespoke reports removed from an existing database, please contact Customer Services on This email address is being protected from spambots. You need JavaScript enabled to view it.
Enhancement 60375 - Launching the Comms Centre from interview page will prompt to save changes
This ensures that the changed data is available when merging from the Interview Comms Centre if required.
Enhancement 50642 – Exchange Sync Audits are turned on by default for new users
This is for users created via user admin and via the first usage wizard
Enhancement 61844 – Exchange Sync Audit files to record 28 days rolling data
A new audit file is created each week, and files over 4 weeks old are deleted
Enhancement 60861 – An Exchange Sync ‘401’ error will retry multiple times, before sending an alert to the user via the Connectivity Centre
If a user has changed their password, both their old password and new password will be tried multiple times.
Enhancement 62083 - The 2.12 SaaS client install uninstalls old versions of Microsoft Visual Studio Tools for Office (VSTO) before installing the Infinity Client
This will run when the SaaS client is upgraded to 2.12. This will not run on upgrades after 2.12.
You will need to answer ‘Yes’ when asked if ‘vsto’ can update your computer
When upgrading Infinity SaaS to 2.12, users may not see the UAC (User Account Control) prompt if they do not have UAC enabled on their workstation. If users do not have local admin rights over their workstation, they will still be prompted to add in the details of an Admin account to carry out the upgrade.
The client install screen will appear.
You will also need to answer ‘Yes’ when asked if ‘Voyager Software Infinity SaaS Client’ can make changes to your computer.
The client install will then continue
Infinity/Mid-Office(MO) Integration
Enhancement 56502 – When the first Temps shift is ‘confirmed’, the placement and all its shifts are exported to MO
Enhancement 61235/56503/60950 – Once a Temps placement has been exported to MO, any changes to its shifts are also exported to MO
This includes creating, editing and deleting shifts.
Enhancement 59544 – Once a Temps placement has been exported to MO, any changes to the placement are exported to MO
This includes any change to the placement page
Enhancement 60514 – Mandatory field checks will run on Temps placements
Perm, Contract and Fixed Term placements have their mandatory fields checked by a business rule when the placement is confirmed. As the process is different for Temps, this business rule does not run when a shift is confirmed.
When any placement (Perm, Contract, Fixed Term and Temp) is picked up by the service to export to MO, a mandatory field check is done (as per the business rule), to confirm that this will pass, before it is exported to MO.
If the placement passes the mandatory field check it is exported to MO.
The business rule one, should exist by default and is called ‘Infinity – MO’. This should be ‘active’ on any database that is configured to export to MO.
If the placement fails the mandatory field check it is not exported to MO and its status is set to ‘Validation Failed’
Enhancement 61376 – An additional ‘Pending’ Status has been added to the MO Export status, to indicate that the placement has been set to be exported, but the mandatory field check has not yet run
In the following scenarios placements are exported
- If a Perm, Contract or Fixed Term placement is confirmed for the first time
- If a Temps placement has its first placement shift confirmed
- Any placement previously exported, is edited
The initial status of the placement is ‘Pending’
When the service runs, it will look at all ‘Pending’ placements and run the ‘Infinity – MO’ business rule to check Mandatory fields.
If the business rule passes, it is exported to MO
If the business rule failed it is not exported
We recommend that defaults are configured in Infinity to ensure that data auto-populates with the correct values, to ensure that placements pass the mandatory field checks where relevant e.g. Back Office Sectors / Divisions / Departments can be configured per User or per Client or per Job to ensure that the correct defaults are set
Enhancement 61714 – Records that fail validation are not exported to MO
If a placement fails the validation check, the export status is set as follows:
My Infinity will alert the user if any of their placement have failed validation via My Infinity
You can view the placements that have failed validation for all users via the application menu.
When the placement is edited its status will be changed to ‘Pending’ and will be picked up by the service when it next polls.
Enhancement 60954 – Changes to worker type in MO are updated in Infinity, for related temp placements as well as the candidate page
If a candidates’ worker type is changed in Infinity, you are asked to select which placement you wish to update and are given a list of the ‘current’ placements, for you to select which placements you wish to update.
If a candidates’ worker type is changed in MO, the change is synchronised to Infinity, and all the candidates ‘current’ placements are automatically updated.
Power BI for Temps
Configuring Power BI - Overview
To enable Power BI to access the data required we have used Power BI’s abilities to import CSV’s from a OneDrive account. There are two types of OneDrive account, OneDrive (Personal) and OneDrive for Business.
If you are on Office 365 Business account, then you can use the OneDrive for Business. If you are not on Office 365 then you will need to setup a OneDrive (Personal) account, it is a free service, click here.
Infinity will update the CSV files every hour, this will sync to your OneDrive account, you can then set Power BI to “Get Data” from the OneDrive account.
https://powerbi.microsoft.com/en-us/documentation/powerbi-refresh-desktop-file-onedrive/
Scheduling a Refresh
https://powerbi.microsoft.com/en-us/documentation/powerbi-refresh-scheduled-refresh/
Configuring Infinity to use OneDrive (Personal)
This section is for users configuring infinity using a ‘OneDrive (Personal)’ account. If you are using a ‘OneDrive for business account’, please see the ‘Configuring Infinity to user OneDrive for business’ section.
You can use a personal OneDrive account to drop CSV files into that can then be linked to Power BI for reporting. Within the Power BI administration area you should click on Authorise:
Click Yes:
Enter your OneDrive (Personal) credentials and once setup then screen will display a hyperlink to the OneDrive (Personal) storage:
The OneDrive (Personal) folder will need to be sync’d to a network drive for Power BI to be able to read the data.
Download the OneDrive App here - https://onedrive.live.com/about/en-GB/download/ and install it.
Once the OneDrive app is installed, it will appear on your taskbar as cloud icon like this -
If you now perform a right mouse click on the cloud icon to open the application, you can start to synchronize the OneDrive (Personal) folder with your local drive
From the application menu select Settings -
Then chose the Account tab and the Choose Folders button -
From here, you can now select the Power BI folder to be synchronised form the OneDrive (Personal) to your local system
Every hour Infinity will send numerous CSV files to the OneDrive (Personal) account and once linked to your Power BI reports will ensure the reports are kept up-to-date.
Configuring Infinity to use OneDrive for Business
This section is for users configuring infinity using a ‘OneDrive for business account’. If you are using a ‘OneDrive (Personal)’ account, please see the ‘Configuring Infinity to user OneDrive (Personal) section.
You will need an Office365 subscription to use OneDrive for business.
Go to https://portal.azure.com
Log into your Office 365 account and click on Azure Active Directory:
Then click on App registrations:
Then click on Add:
Enter the details, Name Voyager Infinity, Application Type Native and Redirect URL https://login.live.com/oauth20_desktop.srf and click create (NB:- if the Create button does not enable click into an alternative field):
Select the newly created entry:
Click on Required Permissions:
Click on Add:
Click on Select an API and then Microsoft Graph:
Click select, once Microsoft Graph is highlighted:
Select the permissions for sign in and read user profile, Read User Files, have full access to user files, read all files that user can access and Have full access to all files user can access (5 permissions), click Select:
Click Done:
Copy the Application ID:
Paste it into the OneDrive for business application ID field within the Power BI administration area of Infinity and Authorise:
Once authorised, it will display a direct hyperlink to the OneDrive for business storage area:
Every hour Infinity will send numerous CSV files to the OneDrive for business account and once linked to your Power BI reports will ensure the reports are kept up-to-date.
Installing Power BI application
Download Power BI desktop via the link:
NB: you do not need to register to download the program
Install the desktop application
Opening the Power BI Template
You can download the Power BI template via the link:
Setting up the Template to use OneDrive (Personal)
This section is for users setting up a Template using a ‘OneDrive (Personal)’ account. If you are using a ‘OneDrive for business account’, please see the ‘Setting up the Template to use OneDrive for business’ section.
Link the CSV files to your Power BI reports by inserting the file path to your local OneDrive (Personal) files:
To get the file path you can open your OneDrive (Personal) folder within file explorer:
Right click in the path field and Copy address as Text:
Setting up the Template to use OneDrive for Business
This section is for users setting up a Template using a ‘OneDrive for business’ account. If you are using a ‘OneDrive (Personal) account’, please see the ‘Setting up the Template to use OneDrive (Personal) section.
Link the CSV files to your Power BI reports by inserting the URL
You can get the URL from the Infinity Administration screen. Click the copy icon on the right-hand side to copy the URL
Loading the data into the Power BI Template
Paste into field and click Load:
Wait for Power BI to pick up all the CSV files and run its queries:
Within Power BI you can edit and adjust content, this is NOT supported by Voyager but as with all Microsoft products there are numerous tutorials and support documentation online.
Each report is accessible via the tabs across the bottom of the page:
Creating a Power BI Dashboard
To setup your dashboard ready for sharing, you can Publish your reports, via the Publish button (it will prompt you to save a copy locally):
Select My Workspace and Select:
On completion, click on Open ‘nameoffiel.pbix’ in Power BI:
This will open the report within your Office 365 (online) environment:
Go to a desired report (one at a time) and click on Pin Live Page:
Input a dashboard name applicable:
Access other reports and pin. To then access the dashboard, go to the ‘hamburger’ button and click on the Dashboard name you entered:
You can make numerous dashboards for differing users or reasons:
In the dashboard, you can layout each report as desired:
Sharing your Dashboard
You are able to then send out your dashboard to users via the ‘Share’ button:
You can then enter the email address of user(s) and set their permissions:
Once shared, any changes to the dashboard will show in the user’s dashboard.
Updating Reports - Manually
The CSV file will update every hour to your OneDrive account, you can then go to your Power BI desktop program and Refresh the reports:
Then Publish:
Ensure you overwrite the old report files to update the existing reports.
Updating Reports - Automated
Power BI will facilitate an automated update once a day (Free) or hourly (Pro Power BI).
https://powerbi.microsoft.com/en-us/documentation/powerbi-refresh-scheduled-refresh/
List of csv files created
The following files are created and used by the Temps Power BI Template
Enhancement 56036 – The Connectivity Centre can now alert ‘roles’ and not just ‘users’ about issues
Enhancement 56037 – The Connectivity Centre displays a history
The history is grouped by service e.g. Power Bi issues are grouped together
Enhancement 56041/56148/56151- The Connectivity Centre will alert users of connectivity issues with Power BI
The Infinity connectivity centre, will alert the dbmanagers roles (a security role that by default contains the dbmanager user) with Authentication and Sync alerts
Enhancement 55612/58682/60858 - Admin screen allows configuration of Power BI
- In the administration screen, the ‘reports’ tab has been renamed ‘Power BI and Reports’
- A ‘Power BI Settings’, tab had been added alongside the previous ‘Reports’ tab
- The ‘OneDrive Client Type’ can be set to ‘OneDrive’ (personal) or ‘OneDrive for Business’
- If ‘OneDrive for Business’ is selected, the OneDrive Application ID field will need to be populated.
- The ‘i’ icon displays help on how to create a OneDrive Application ID
- iCapture and Power BI can use the same OneDrive (Personal) account
- Power BI stores the data in a folder called ‘Infinity Power BI VIC_code’ on SaaS
- Power Bi stores the data in a folder called ‘Infinity Power BI database_name’ On Premise
- If you are using iCapture with a OneDrive (Personal) data source, there will also be a folder called ‘Infinity iCapture’
Enhancement 55613/59488/61826/61219/60943 - Default Temps Template
A Default Power BI Template is accessible via the admin screen
This Template currently only displays Temps data. There are future plans for this to be extended to Contract, Perm and Fixed Term data.
Each group has an explanation stating what it is displaying.
If the PowerBI Template fails to connect to the OneDrive data, the reports will all display as 0.
Enhancement 55777 - Power BI data is exported from Infinity to OneDrive once every hour
- When Power BI is configured, the maximum wait before files are generated is one hour.
- A new set of files will be generated once an hour.
- When the files have finished uploading initially they go into the ‘Live’ folder.
- When the files are re-uploaded, they go into a separate folder, which is used to replace the ‘Live’ folder once the upload has completed. This ensure that Power BI is always generating data from a complete dataset.
Enhancement 55765 - Temp placements are exported to OneDrive for use by Power BI
Temp Placements created up to 6 months in the past are exported
Fields exported are:
- placement id, job id, candidate id,
- placement location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
- pay currency, charge currency
- placed date
This is exported to the following files:
- placement file
- placement location file
- placement div dept file
- placement consultants file
Enhancement 55763 – Temp placement shifts are exported to OneDrive for use by Power BI
Placement Shifts up to 6 months in the past are exported, and all placement shifts in the future
Fields exported are:
- placement id, candidate id, start date, end date, status (dates are UTC)
This is exported to the following files:
- ‘Placement Shift file’
Enhancement 55764/61611 - Temp placement rates are exported to OneDrive for use by Power BI
Any Temp placement created up to 6 months in the past will have all its rates exported
Fields exported are:
- placement id, start date, end date, total pay, total cost, charge, profit, interval, rate type
This is exported to the following files:
- Placement Rate file
- Rate Interval file
- Rate Type file
Enhancement 55768 – Temp Jobs are exported to OneDrive for use by Power BI
Any Temp job created up to 6 months in the past will be exported
Fields exported are:
- jobid, company id, job title,
- job location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
- pay currency, charge currency
- created date
This is exported to the following files:
- Job file
- Job Location file
- Job div dept file
- Job Consultant file
- Job Title file
Enhancement 55767 – Temp Job shifts are exported to OneDrive for use by Power BI
Job Shifts up to 6 months in the past are exported, and all job shifts in the future
Fields exported are:
- job id, start date, end date, total pay, total cost, profit
- interval id
- rate type id
This is exported to the following files:
- job shift file
Enhancement 55766 – Temp Job rates are exported to OneDrive for use by Power BI
Any Temp job created up to 6 months in the past will have all its rates exported
Fields exported are:
- job id, start date, end date, total places (dates are UTC), filled placed
This is exported to the following files:
- job rate file
- Rate Interval file
- Rate Type file
Enhancement 55761 – Candidates are exported to OneDrive for use by Power BI
Temp candidate created less than 6 months ago are exported.
The candidate will need to be marked as a temp candidate as follows:
Fields exported are:
- Id, and Status
This is exported to the following files:
- Candidate file
Enhancement 55762/52187 – companies are exported to OneDrive for use by Power BI
All companies are exported (excluding internal companies)
Fields exported are:
- Id, Name, Company type, business sector
This is exported to the following files:
- Company file
- Company type file
Enhancement 55769 – Consultants are exported to OneDrive for use by Power BI
All Users are exported
Fields exported are:
- Id, Shortname, Division, Department
This is exported to the following files:
- User file
Enhancement 55770 – Teams are exported to OneDrive for use by Power BI
All Teams are exported
Fields exported are:
- Id, Name, List of users in each team
This is exported to the following files:
- Team file
- User team file
Enhancement 55771 – Back Office Sectors, Divisions and departments are exported to OneDrive for use by Power BI
All Back office sectors, divisions and departments are exported
Fields exported are:
- Id, Back office sector name
- Id, Back office sector id, Department Name
- Id, Back office sector id, Division Name
This is exported to the following files:
- Back office sector file
- Division file
- Department file
Enhancement 61349 - Contract placements are exported to OneDrive for use by Power BI
The Power BI Template released with Infinity 2.12 only displays ‘Temp’ data. Work has started on the Contract, Perm, Fixed Term version and some data currently exports to csv. There are future plans to export more Contract, Perm, Fixed Term data and to create a default Template to view this data in a dashboard.
All contract placements with an end date less than a year ago are exported. Also all contract placements with a blank end date that has a start date less than 2 years ago are exported
Fields exported are:
- placement id, job id, candidate id,
- placed date, start date & end date, pay currency, charge currency, hours, hours per, placement status
- placement location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
Enhancement 61354 – Contract Placement Rates are exported to OneDrive for use by Power BI
The Power BI Template released with Infinity 2.12 only displays ‘Temp’ data. Work has started on the Contract, Perm, Fixed Term version and some data currently exports to csv. There are future plans to export more Contract, Perm, Fixed Term data and to create a default Template to view this data in a dashboard.
All contract placements with a rate end date less than a year ago are exported. Also all contract placements rates with a blank end date that has a start date less than 2 years ago are exported
Fields exported are:
- placement id, start date, end date, total pay, total cost, profit, charge rate, , hours, hours per
- interval
- rate type
Enhancement 61350 – Perm Placements are exported to OneDrive for use by Power BI
The Power BI Template released with Infinity 2.12 only displays ‘Temp’ data. Work has started on the Contract, Perm, Fixed Term version and some data currently exports to csv. There are future plans to export more Contract, Perm, Fixed Term data and to create a default Template to view this data in a dashboard.
All Perm placements with a start date less than a year ago are exported.
Fields exported are:
- placement id, job id, candidate id,
- placed date, start date, pay currency, charge currency, salary, package, per, fee %, fee value, placement status
- placement location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
Enhancement 61351 – Fixed Term Placements are exported to OneDrive for use by Power BI
The Power BI Template released with Infinity 2.12 only displays ‘Temp’ data. Work has started on the Contract, Perm, Fixed Term version and some data currently exports to csv. There are future plans to export more Contract, Perm, Fixed Term data and to create a default Template to view this data in a dashboard.
All Fixed Term placements with a start date less than a year ago are exported.
Fields exported are:
- placement id, job id, candidate id,
- placed date, start date & end date, pay currency, charge currency, salary, package, per, fee %, fee value, placement status
- placement location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
Enhancement 60859 – Contract Jobs are exported to OneDrive for use by Power BI
The Power BI Template released with Infinity 2.12 only displays ‘Temp’ data. Work has started on the Contract, Perm, Fixed Term version and some data currently exports to csv. There are future plans to export more Contract, Perm, Fixed Term data and to create a default Template to view this data in a dashboard.
All Contract jobs with a start date less than a year ago are exported.
Spec Jobs are not exported
Fields exported are:
- jobid, company id, job title,
- created date, start date & end date, pay currency, charge currency, min pay rate, min charge rate, min rate/per, min profit, hours, hours per, job status, date search first run, no. of places, no. remaining
- job location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
- table of 'filled by' - place, filled by
Enhancement 61347 – Perm Jobs are exported to OneDrive for use by Power BI
The Power BI Template released with Infinity 2.12 only displays ‘Temp’ data. Work has started on the Contract, Perm, Fixed Term version and some data currently exports to csv. There are future plans to export more Contract, Perm, Fixed Term data and to create a default Template to view this data in a dashboard.
All Perm jobs with a start date less than a year ago are exported.
Spec Jobs are not exported
Fields exported are:
- jobid, company id, job title,
- created date, start date, pay currency, charge currency, min salary, min package, per, min fee %, min fee value, job status, date search first run
- job location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
- table of 'filled by' - place, filled by
Enhancement 61348 – Fixed Term Jobs are exported to OneDrive for use by Power BI
The Power BI Template released with Infinity 2.12 only displays ‘Temp’ data. Work has started on the Contract, Perm, Fixed Term version and some data currently exports to csv. There are future plans to export more Contract, Perm, Fixed Term data and to create a default Template to view this data in a dashboard.
All Fixed Term jobs with a start date less than a year ago are exported.
Spec Jobs are not exported
Fields exported are:
- jobid, company id, job title,
- created date, start date & end date, pay currency, charge currency, min salary, min package, per, min fee %, min fee value, job status, date search first run
- job location
- back office sector
- table of divisions and departments inc. % split
- table of consultants inc. % split
- table of 'filled by' - place, filled by
Tempest
Enhancement 60886 – Configure the Admin screen to export to Tempest
The ‘Financial Settings’ tab of the Administration screen, has an ‘Export To’ field.
When ‘Export To’ is set to Tempest, the ‘Tempest Options’ tab can be populated.
The path needs to be accessible to the machine running the Back Office Export Service on the server.
A service creates the export files. The ‘Tempest export polls every’ option specifies the maximum time you will need to wait for the service to start exporting placements.
This option is available ‘On Premise’. This option is greyed out for ‘SaaS’ customers.
Enhancement 60895 – Permissions control who can export to Tempest
By default, only DBManager, VoyagerSupport and VoyagerSupport2 have this permission
This permission is off for all other users. This permission should be given to the user who wants to initiate the creation of the export files.
Enhancement 60888 – When a placement is confirmed, it’s status is set to ‘Export to Tempest Available’
The Export Status is changed by the service, and therefore status changes are not immediately shown on the placement page. If you close the placement and open it again, you will see the most up-to-date status.
Enhancement 61387 – If a placement is cancelled when it has a status of ‘Export to Tempest Available’, the placement status is changed back to ‘Not Exported’
If the status is ‘Export to Tempest Available’ and the placement is cancelled, the placement will NOT be sent to Tempest.
The Export Status is changed by the service, and therefore status changes are not immediately shown on the placement page. If you close the placement and open it again, you will see the most up-to-date status.
Enhancement 61342/60893 – Creating the Export files
From the application menu the ‘Placements for Export’ screen is used to select the placements you wish to export
The ‘Placements Available for Export’ screen opens.
Ctrl-Click or Shift-Click the placements you wish to export, and click ‘Exported Selected Placements’
Alternatively, ‘Export All Placements’ can be selected from the drop down menu.
When the ‘Export’ button is pressed, the placements are added to the ‘Back Office Export Queue’ and their Status is changed to ‘Export Pending’.
Users without the ‘TempestExport’ permission will not see the ‘Back Office Export’ options from the Application menu.
If the admin screen is not configured to export to Tempest, you will not see the ‘Back Office Export’ options from the Application menu.
Enhancement 60897/60899/60901/60902/60898/60903/60900/61332 – The export files are created as follows:
| Filename | Contains |
| ASSGNMNT.DAT | Contract & Temp Placements |
| CLIENTS.DAT | Clients |
| SUPPLIERS.DAT | Ltd Company & Umbrella Companies |
| WORKERS.DAT | Candidate |
| ASSIGNRATE.DAT | Contract & Temp rates |
| CLIENTADDR.DAT | Client Addresses |
| PLACEMENT.DAT | Perm & Fixed Term Placements |
| TISHIFTS.DAT | Temp Shifts |
Infinity will not overwrite current export files if the previous files are still present.
If the previous files are still present, the placements that you are trying to export will have their status set to ‘Export Pending’ and remain at that status.
When the files that are preventing the export are imported into Tempest (or are deleted), on the next poll the service will create a new set of files to export all ‘Export Pending’ placements
Infinity will not prevent you pressing the export button if the files already exist
If you are unsure, you may wish to check for the presence of the export files, before initiating in export.
These files can be imported into Tempest
When the files are being created, .CTL files are also created e.g. ASSGNMNT.CTL, CLIENTS.CTL.
When the export has finished creating the files, the .CTL files are removed.
If .DAT files exist and no .CTL files exist, then the export has finished.
When Tempest imports it also creates .CTL files, so the presence of these files means that either Infinity is in the process of export files or Tempest is in the process of importing files.
During testing 10 placements were exported immediately after a poll which is set as default at 120 seconds. It is expected that larger numbers of placements e.g. 100 would also export relatively quickly.
The data is exported in using the following rules. A field map document is available on request.
- Infinity reference numbers are exported with the leading 0s removed i.e. CN0000000012, will be export to tempest as CN12.
- Placement locations must be linked to a company location within Infinity, in order to be exported to Tempest. Custom addresses will not be exported.
- If a candidate worker type is blank, the candidate will be sent to Tempest as PAYE. (Tempest will assume PAYE if this is not set)
- If Infinity has more consultants linked to a record (e.g. Placement, Candidate) than can be exported to Tempest, they are selected based on % split (if a % split exists), and then by alphabetic order
Enhancement 60889 – When the placements are exported their status changes to ‘Exported’
The service picks up any placement with a status of ‘Export Pending’, exports it, and then sets the placement status to ‘Exported’
From the application menu the ‘Back Office Export Queue’ screen is used to see the placements awaiting export.
Once the placements have been exported, the ‘Exported’ tick box in the ‘Back Office Export Queue’ will be ticked. You will need to refresh this screen once the service has run.
The ‘Back Office Export Alerts’ screen displays any placement that has an issue exporting the files from Infinity.
Users without the ‘TempestExport’ permission will not see the ‘Back Office Export’ options from the Application menu.
If the admin screen is not configured to export to Tempest, you will not see the ‘Back Office Export’ options from the Application menu.
Enhancement 60890 – Once a placement has been exported it can be re-exported by editing the placement
If the candidate and/or the client has been edited, you will need to edit the placement to initiate a re-export.
You can do this by pressing the ‘Save’ button on the placement page.
The placements status will then be set to ‘Re-export to Tempest Available’
Enhancement 60923/60904 – When the ‘export’ button is pressed, placements with a status of ‘Re-export to Tempest Available’ are also exported.
When the export button is pressed their status is changed to ‘Pending Re Export’
When the service picks them up and exports them, their status is changed to ‘Exported’
Enhancement 60920 – If placements have previously been exported from Voyager Professional to Tempest, new placements with an existing client will use to the same client page in Tempest
This enhancement is only relevant for clients that have previously been exported from Voyager Professional to Tempest
If a placement is exported from Infinity, where the client already exists in Tempest (Due to an export from Voyager Professional), the placement will re-use the client page in Tempest
Enhancement 60921 – If placements have previously been exported from Voyager Professional to Tempest, new placements with an existing candidate will use to the same candidate page in Tempest
This enhancement is only relevant for candidates that have previously been exported from Voyager Professional to Tempest
If a placement is exported from Infinity, where the candidate already exists in Tempest (Due to an export from Voyager Professional), the placement will re-use the candidate page in Tempest
Enhancement 60926 – If placements have previously been exported from Voyager Professional to Tempest, any placements that were yet to be confirmed, can be confirmed in Infinity and will be exported to Tempest.
This enhancement is only relevant for candidates that have previously been exported from Voyager Professional to Tempest
Any placement in Infinity that was produced by a ‘Data Conversion’ from Voyager Professional and not confirmed (i.e. not exported) can be exported from Infinity to Tempest.
When you confirm the placement, it will exported in the same way as any new data created in Infinity
Enhancement 90924 – If placements have previously been exported from Voyager Professional to Tempest, any changes to these placements will NOT automatically be sent to Tempest
This enhancement is only relevant for candidates that have previously been exported from Voyager Professional to Tempest
If a placement is exported from Voyager Professional to Tempest, when the same placement in Infinity is edited, it will not automatically be re-sent to Tempest
Enhancement 90925 – If placements have previously been exported from Voyager Professional to Tempest, they can be un-confirmed and re-confirmed for changes to be exported to Tempest
This enhancement is only relevant for candidates that have previously been exported from Voyager Professional to Tempest
If a placement is exported from Voyager Professional to Tempest, when the same placement is un-confirmed (via the status ‘On Hold’) and re-confirmed in Infinity, it will be sent to Tempest.
It will update the placement/client/candidate/supplier page in Tempest.
Once the Infinity placement has a status of ‘Started’ it is not possible to un-confirm and re-confirm.
If this is an issue, then the Data-Conversion team can ensure relevant placements have a status of ‘confirmed’ and not ‘started’ or ‘finished’ when the Data is exported from Voyager Professional into Infinity.
Alternatively if there is one particular Placement that you wish to be re-exported, please contact Voyager Support.
Only set these placements (i.e. placements exported from Voyager Professional to Tempest) to ‘Started’ if you are sure you will not want to them to be re-exported to Tempest
Enhancement 60929/90931 – The Infinity export to Tempest will support multiple Back Office Sectors, Divisions and Departments, on different placements
Each placement in Tempest can only have 1 Back Office Sector, Division & Department.
Different placements can have different Back Office Sectors, Divisions & Departments.
Enhancement 60934 – Mandatory fields will need to be checked by a Voyager Infinity Business Rules before it is exported, to ensure that incorrect data is not sent to Tempest
A business rules as listed below will need to be created and made active.
It is important that this business rule is created, to prevent issues importing the data into Tempest.
The business rule as detailed below is set to make all fields that are ‘Mandatory’ for the import into Tempest, Mandatory to confirm a placement (and therefore Mandatory to export from Infinity)
Infinity to Tempest Export Limitations
The current export from Infinity to Tempest will export Cont, Perm, Fixed Term & Temp placements
The current business rules run for Cont, Perm & Fixed term placements, but not for Temp placements. There are future plans for Business rules to run for Temp placements
The Tempest Export put the files on the file system. This option is not available for SaaS customers. There are future plans for the files to export to OneDrive, which will allow the integration to work for SaaS database, as well as On Premise.
Request an Upgrade
|