If you wish to synchronize other custom data, please contact Octime directly in order for them to examine the faisability of your request.
How the integration works
-
-
- Solutions involved: Poplee Core HR
- Type of integration: flat file on an FTP
- Integration direction: Lucca to Octime
-
Setting up the integration
To perform the integration, the Lucca database administrator will need to set up an FTP.
This will allow you to synchronize the new users, the modifications of the user files as well as the employee’s end of contract date.
The export transfer will be automated at a time that you need to define (we recommend during the night, 3am for example).
This implementation requires a modification of the settings on Lucca:
-
-
- creation of a user export in the format required by Octime
- creation of a section in the HR file with the necessary data for Octime
-
When sending employee data to Octime, a dedicated section must be created in the employee's HR file with the following mandatory data:
-
- Employee number (the format must be the same as the one required by the payroll software.In the default values of the HR file, you can configure a model of personnel numbers which can be automatically generated at the creation of the employee)
- Last name
- First name
- Birth name
- Login
- Date of birth
- Gender
- Seniority date
- Additional address
- House number
- a, b, etc. (make a drop-down list with A, B, C, D)
- Street name
- Zip code
- City
- Professional email
- Personal email
- Contract start date
- Contract end date
- ETP (data format: text /!\ the administrator must complete the data with 2 decimal places: XXX.00 without that the data will not be integrated → you can add to the label of the data "remember to modify this data when creating a new contract" to avoid forgetting)
- Effective date of ETP
- Contract template
- Contract start reason
- Contract end reason
- Direct line
- Monthly contractual hours (data format: text /!\ the administrator must complete the data with 2 decimal places: XXX.00 without that the data will not be integrated → you can add to the label of the data "remember to modify this data when creating a new contract" to avoid forgetting)
- The following data must be created, but can be sent empty. This is used to maintain the structure of the export file. By default, the information on the employee's job is not recorded. If the customer wants to enter them in Lucca, they should enter this information first in Octime and then replicate it in Lucca. This data originated from Octime, the customer will have to keep this information up to date in Lucca if they want to use it.
- Date of entry to the job
- Job code (data format: list of values)
- Job title (data format: list of values)
- The following data can be created optionally. There can be up to 10 levels. We do not include the "job" data history by default. If the client wants to manage this data in Lucca, they will have to keep the information up to date in both programs
- Date of assignment to the structure
- Structure assignment code (data format: list of values)
- Label of the assignment to the structure (data format: list of values)
Why not manage the job and structure directly in Lucca?
Because this data is created in Octime. Octime must send us this information to be integrated into the data concerned. If you add this data in Lucca and it does not exist in Octime, the import file will be rejected. In addition, if you only modify the code and/or the label without modifying the date of accepting the job/assignment, this will affect the calculations performed by Octime.
The settings in the PSRH export must be done in this order:
| Lucca Data | Export Code | Mode of correspondence/comment |
| Employee number | Employee number | |
| Last name | Last name | |
| First name | First name | |
| Birth name | Birth name | |
| Login | ID | |
| Date of birth | Date of birth | |
| Gender | Sex |
replace Female by F replace Male by M |
| Seniority date | Seniority date | |
| Additional address | Add address | |
| House number | Number | |
| a, b, etc | Extension | |
| Street name | Street | |
| Zip code | Zip code | |
| City | City | |
| Professional email | Email address | |
| Personal email | Personal email address | |
| Start of contract | Contract start date | |
| Contract end | Contract end date | |
| ETP | ETP | |
| Effective date of ETP | Effective date | |
| Contract template | Contract template | |
| Contract start reason | Contract start reason | |
| Contract end reason | Contract end reason | |
| Direct line | Telephone number 1 | |
| Contractual hours | Monthly contract hours | |
| Date of entry to the job | Date of the job | |
| Code of the job | pos_cod | |
| Label of the job | pos_lib | |
| Date of assignment to the structure | Date of assignment | For the data on the structure of the job, there can be up to 10 levels, so it is important to put this data at the end of the export to avoid preventing the integration |
| Code of the structure assignment |
niv_cod1 and if there are several levels niv_cod2; niv_cod3 etc. |
|
| Label of the assignment to the structure |
niv_lib1 and if there are several levels niv_lib2; niv_lib3 etc. |
The export configuration must be:
- Generic CSV format
- Date format dd/MM/yyyy
- Decimal point separator: comma
- Field separator: Semicolon
- File type: CSV file
- select "Generate header row" > Label of the data
Then create an alert of modification type > start> Contract start date.
In the options of this alert, put an informative description such as:
When changing your contract, remember to change the following information:
- ETP (remember to indicate decimals in .xx format)
- Effective date of ETP
- Monthly contractual working hours (remember to indicate the decimals in .xx format)
By default, the following data should be managed by Octime, but if you wanted to integrate them into Lucca, remember to also update:
- date of entry, job code and job title
- date of assignment, the code and label in the structure
The Octime help sheet can be viewed at this link.