Netvisor

Nepton can be configured to send work hour and work times data to Netvisor system. Data can be sent on a scheduled basis or with manual run. This guidance explains the integration when Nepton directly sends the information into Netvisor.  This is a different implementation than using Nepton API and using the Netvisor export  does not require Nepton API to be used. 

The data being sent is defined in integration ruleset settings. The data is transferred using a REST API, which is described in more detail below.

Please make sure that all necessary settings have been done in Netvisor before you start data integration

Configuration

Setting person identifiers

Person's personal identification number can be set by editing person's information in Employees -> Person's information view.

It is also possible to use personnel number as identifier, which can be set person's personnel number by editing person's information in Employees -> Person's information view, in Identifiers section.

To use personnel number as identifier, you need to use UserData table and have the following addition in all integration ruleset rules:

UserData.Personnelnumber AS NetvisorFieldEmployeeId,
'number' AS NetvisorAttributeEmployeeIdType

For example:

SELECT UserSalaryData.*, SUM(UserSalaryData.Amount) As OverrideAmount,
  UserData.Personnelnumber AS NetvisorFieldEmployeeId,
  'number' AS NetvisorAttributeEmployeeIdType
FROM UserSalaryData
JOIN UserData ON (UserSalaryData.UserId = UserSalaryData.UserId)
WHERE UserSalaryData.CompensationType = 'BasicTime'

Creating an integration ruleset

Using this API requires an integration ruleset. You can read more about defining integration ruleset rules here.

Data export

To export data directly to Netvisor, you first need to

1. Add a new API identifier to Netvisor. You can get the API identifier from your Netvisor service provider. Remember to record the user ID and key of the identifier as you need to enter them to Netvisor settings in Nepton.
2. Grant access to API for Nepton service. You can get the instructions from your Netvisor service provider. Nepton integration key is C846174055BF5C1C633207B79780D1CA
   
   Nepton will need access to workday.nv API interface resource.

After this, you can configure API identifier user ID and key to Nepton. This can be done from working community settings: Worktime -> Administration -> Working community settings -> External services -> Ruleset you created. Settings can be found under "Export to web service" heading.

In addition to API identifier user ID and key, you also need to configure the following:

• Export web service address. This needs to be https://integration.netvisor.fi/workday.nv
• API business ID. Business ID for which working hours are sent to Netvisor.

Export options

The scheduled export can be defined as instructed in the "Ruleset Export options" article. The difference in configuration is that the data on the SFTP server does not need to be configured, as the data is sent directly to Netvisor via the webservice. Export format is Netvisor.

Export from User interface

This is done like any worktime integration run. Instructions for this can be found here.

When running the integration, you can choose whether to download worktime data (Email report to the following email addresses) or send it directly to Netvisor (Send export data by web service).

Limitations

• Persons with Employee number "0" (zero) will not be included in the export data

Sent data

Example of set data

<root>
  <workday>
    <date format="ansi" method="replace">2016-03-14</date>
    <employeeidentifier type="personalidentificationnumber">111111-1111</employeeidentifier>
    <workdaytime>
      <starttimeofday>12:30</starttimeofday>
      <endtimeofday>16:00</endtimeofday>
      <breaktime type="minutes">0</breaktime>
      <collectorratio type="number">123</collectorratio>
      <acceptancestatus>confirmed</acceptancestatus>
      <description>Iltapäivä</description>
    </workdaytime>
  </workday>
</root> 

Expected response

Example response

<Root>
  <ResponseStatus>
    <Status>OK</Status>
    <TimeStamp>01.01.2020 12:00:00</TimeStamp>
  </ResponseStatus>
</Root>