Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Server version of UpRaise can integrate with In large organizations, it is typically seen that they use 3rd party systems such as AD, LDAP, HRIS, DaaS softwares software for centralized user management. Typically, these systems should push reports to In the case of UpRaise, it becomes easy for organizations to have seamless integration with such tools to manage users and teams. This is where we brought HRMS sync feature.

As of now, this sync was only available via a pre-configured SFTP server connection, from where where these 3rd party systems would push updated files on the SFTP, and UpRaise can poll pull data at a set frequency from the SFTP and update it within UpRaise Company directory.

Now along with the above option, we bring more flexibility to this feature. Now you can import xls, xlsx, and JSON files to UpRaise and sync the user and team data. Let us see how these options work.

Sync via SFTP

Expand
titleSync via SFTP

If you wish to use the SFTP option follow the below steps.

Setting up SFTP connection

As UpRaise Admin/super admin

can

, navigate to

company directory under administration & then

the Company directory >> click on

'HRMS Sync' tab. This is where the SFTP connection is configured. 

Import or sync HRMS data >> Import data tab.

  • By default Auto sync toggle is turned off. Turn on this toggle and you will notice more options to set up the SFTP connection.

View file
nameInvalid file id - 5e827da1-60c0-4b4c-b4e9-b473c797f18e

  • Import file option is always available. When Auto sync option is turned on, clicking on Import file will display options to import files as shown in the below images.

Image Added

Once you turn on the Auto-sync option, below fields are displayed.

  • Auto-sync -

on
  • On/off, dictates whether UpRaise will connect to the SFTP server daily night 11 o'clock to retrieve the JSON files.

  • SFTP Server -

host name
  • Hostname or IP address

  • Port -

usually SFTP is
  • Usually SFTP is configured at 22

  • username & password -

to
  • To connect with the SFTP server

  • Directory -

relative
  • Relative path to the directory where the JSON/excel files will be available

Add the above information & click on

'

Save

'

. On a successful connection, the configuration will be saved. Otherwise, a relevant error message will be displayed.

Note

Do note that, the SFTP user must have read & write permissions in order for the entire process to work properly.

Image Removed Info
Image Added

How does Auto Sync work?

Once the above setup is done UpRaise will reach out to this SFTP server daily night 11 o’clock & pick up the file/s generated that day.

After processing, all UpRaise administrators will be notified via email

& a status JSON/xls will be dumped on the same SFTP location

and sync status will be updated under Logs tab.

Do note that name of the file to be picked up by the system should have the following pattern -

  • Syntax -

UsersDataYYYYMMDD
    • UsersData<filename>.json

      • Eg. UserData20230422.json

or

UsersDataYYYYMMDD.xls 

or

TeamsDataYYYYMMDD.json

    • UsersData<filename>.xls/xlsx

      • Eg. UserData20230422.xls/xlsx

    • TeamsData<filename>.json

      • Eg. TeamsData20230422.json

    • TeamsData<filename>.xls/.xlsx

      • Eg. TeamsData20230422. xls/xlsx

The first time around, it may take a few

trial

trials & errors to get the JSON format right.

That is why there is a manual trigger. Manual trigger accepts name of the JSON file & searches for it in the SFTP folder. Once you get the format correct, just start dumping these JSONs on a daily basis in the configured folder. Expected naming of the file follows the pattern - UsersDataYYYYMMDD.json

For incremental updates, the process will be completed fairly quickly based on the updates.

You can download sample templates from the links provided on the Import or sync HRMS data tab as shown in the image below -

Image Added

Once completed, UpRaise will generate a file with execution status in the same SFTP (for which it needs Write permissions on the SFTP).

Format

The standard format & content of

these reports

the files should be as explained below

Employee data JSON structure

UpRaise expects to receive only the user records in which one or more of the following attributes have been updated - designation, manager, team, UpRaise role. If there are updates to other user attributes in the external system, UpRaise doesn't need to know.

Employee Data JSON Structure
Code Block
languagejs
{ 
 "users":[   
      {   
         "id":"11081", 
         "jirausername":"Jane.Doe", 
         "designation":{   
            "id":"94", 
            "name":"Consultant, eLearning & Systems" 
         }, 
         "userrole":"USER", 
         "manager":{   
            "id":"9195", 
            "jirausername":"John.Doe" 
         }, 
         "teams":[   
            {   
               "id":"10017", 
               "name":"HR" 
            } 
         ] 
      } 
   ] 
} 

Note

This file is supposed to be incremental. Meaning, only those users whose data is updated should be present in the JSON file. For the first run, all users should be part of this JSON.

Parameter details

Parameter

Type

Details

id

- string -

String

Id of the user in the external system. Should be unique for each user.

jirausername 

- string-

Jira username of the corresponding user. UpRaise assumes that the users in the file are already part of Jira. 

designation

-

complex type

-

UpRaise can store only one designation per user

id

String

id - string - The

Designation id is the unique identifier for the designation. If at the time of processing, this id does not exist in UpRaise designations master, it will be created and assigned to the corresponding user. If it exists, designation name would be updated if required.

name

- string -

String

e.g. Software Engineer, Project Manager etc

userrole

-

this parameter is mandatory in case user based access is turned on. Possible options are 'USER' & 'NO_ACCESS'

manager

-

complex type

-

UpRaise can store only one manager per user

id - string - Id

Id

String

Manager id of the user in the external system. Should be unique for each user. UpRaise expects the manager to be a user himself in the external system.

jirausername 

- string-

String

Jira username of the corresponding user. UpRaise assumes that the users in the file are already part of Jira. 

teams

-

complex type

-

UpRaise can store multiple teams per

user

id

String

id -  string - The

Team id is the unique identifier for the team. If at the time of processing, this id does not exist in UpRaise teams master, it will be created and assigned to the corresponding user. If it exists, team name would be updated if required.

name

name - string -

String

Team name for e.g. Inside Sales, Software Development etc

Team data JSON structure

UpRaise expects to receive team records in which one or more of the following attributes have been updated - team name, team id, team lead id & name, parent team name & id, team type & description. If there are updates to other team attributes in the external system, UpRaise doesn't need to know.

Employee Data JSON Structure
Code Block
languagejs
{
  "teams": [
    {
      "id": "741",
      "name": "Sales",
      "teamLead": {
        "id": "1",
        "jirausername": "John.Doe"
      },
      "parentTeam": {
        "id": "249",
        "name": "Business Development"
      },
      "teamType": {
        "name": "Department"
      },
      "description": {
        "name": "Team responsible for bringing in Dollars."
      }
    }
  ]
}

Parameter details

Parameter

Type

Details

Team

Complex type

id - string -

One team can have multiple users in it.

id

String

Id of the team in the external system. Should be unique for each team.

name

- string-

String

Name of the team. If the team does not exist in UpRaise already, it will be created and then updated in the database. 

teamLead


id - string -

Complex type

Team lead is not predefined. One of the existing users is defined as team lead

id

String

team lead's user id in the system. It should be a unique id.

jirausername

- string -

String

jirausername of the team lead.

parentTeam

id - string - Id

Complex type

One of the teams is assigned as parent of other multiple teams from the existing teams

id

String

Id of the parent team in the external system. Should be unique for each team

name

- string - 

String

Name of the parent team.  If the team does not exist in UpRaise already, it will be created and then updated in the database. 

teamType

String

name - string -

team type e.g. department, division, team etc

description

name - string -

Complex type

This will be the free text defined to describe the team, its details, etc.

name

String

Description of the team. 

Manual update via SFTP

Sometimes it is possible that you want to sync date immediately instead of waiting for the UpRaise job that runs every day. Or for the first-time sync, it may take some time to update files so you can also go for the manual update of the file.

  • Click on Import file

  • Select SFTP server (your SFTP server) here SFTP server (amoeboids10.files.com)

  • Update the File name

  • Click on Fetch

Image Added

This will trigger the manual sync of the file from the SFTP server and the system will immediately retrieve the file on the SFTP server and start the sync.

You can check logs for the status.

Import files from your system

On this page

Table of Contents
minLevel2
maxLevel6
outlinefalse
typelist
printablefalse

In this section

Child pages (Children Display)
pageCompany Directory