Genesys Cloud - Main

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Import Employee ID via Bulk or Script

  Thread closed by the administrator, not accepting new replies.

  • 1.  Import Employee ID via Bulk or Script

    Posted 07-31-2023 09:41
    No replies, thread closed.

    Hi Everyone,

    i am looking for an idea / option for the people import to also add the "Employee ID" in Section HR as we need it for internal reporting.

    Has anyone some hints or experience how to get the ID into Genesys via Bulk Import or any other script?

    I hope someone has some ideads.

    Thanks a lot,

    Christoph


    #SystemAdministration
    #Unsure/Other

    ------------------------------
    Christoph Dittmer
    Sixt SE
    ------------------------------


  • 2.  RE: Import Employee ID via Bulk or Script

    Posted 08-01-2023 03:37
    No replies, thread closed.

    Not that I know of.  You could create a CSV with the user ID and employee ID and then run it through PostMan as a script to update the user through the API.  Also, you can use SCIM to sync this information with your AD.  There is no way right now to do it in bulk easily.  It is one thing to change something to enabled for a group of users like for Auto-answer and another to assign something unique to each user in bulk.  Start and Idea to add Employee ID to the CSV import.  



    ------------------------------
    Robert Wakefield-Carl
    ttec Digital
    Sr. Director - Innovation Architects
    Robert.WC@ttecdigital.com
    https://www.ttecDigital.com
    https://RobertWC.Blogspot.com
    ------------------------------

    Original Message


  • 3.  RE: Import Employee ID via Bulk or Script

    Posted 08-01-2023 08:44
    No replies, thread closed.

    Hi Chris, 

    I had the same need some time ago and struggled for a while trying to find a way to import the employee ID's.  There is a way to add the employee ID via an API, but i was only able to find a way to do it one at a time.  I know one at a time is not ideal, but I will say that doing it via the API was faster than waiting for the screens to render in the app. 

    If you want to attempt this here is the process I used: 

    I used the Get the list of available users API and expanded the employerInfo section in the properties to get all the active users.  I pulled that down into a list and then used that information to begin updating the process of manually updating each user. 

    To update each user, I had to use the Patch Update user API.  You need to put the userID in the appropriate box and then in the body I used the following (you have to have the version number which comes back in from the available users API...anytime you update a member record, that field auto increments so all your users will not have the same version number): 

    {

       "version": X,

                   "employerInfo": {

                      "employeeId": "XXXXX"

    }

    }

    I cleaned up my export so that I only had the columns I needed and wrote a quick formula to give me the code for each user update so I could just copy paste the user ID and then copy paste the update code.  It took seconds for each update after I laid it out in the spreadsheet.  

    I know this isn't the bulk update process you were hoping for, but it was the only solution I found when I was attempting to do the same thing.  

    Thanks! 



    ------------------------------
    Jason Lorden
    Independent Health Association, Inc.
    ------------------------------

    Original Message


  • 4.  RE: Import Employee ID via Bulk or Script

    Posted 08-01-2023 12:18
    No replies, thread closed.

    We use Okta as our user management and SSO platform.  In Okta we link the Windows AD groups to the Genesys Groups. In this manor we manager our Genesys users based on the AD group they belong to.  By adding a user to the AD Group their details are pushed from AD --> Okta --> our Genesys Org. One of the available fields in the Okta integration is employee ID.  Additionally Okta can be configured to pull various fields from AD in our case we pull the users AD login ID which is separate from their HR ID.    

    See https://help.mypurecloud.com/articles/scim-and-genesys-cloud-field-mappings/



    ------------------------------
    Mark Pierson
    Ally Financial
    ------------------------------

    Original Message


  • 5.  RE: Import Employee ID via Bulk or Script

    Posted 08-07-2023 07:06
    No replies, thread closed.

    Hi Mark,

    thanks for your input. We started using Azure Active Directory SCIM integration now.

    At the moment during test we have the issue that the postman code expires after 86399 seconds. Usually our SCIM job should run every 40 minutes.

    Do you know  if an automatic run will keep the connection from expiring?

    Regards,

    Christoph



    ------------------------------
    Christoph Dittmer
    Sixt SE
    ------------------------------

    Original Message


  • 6.  RE: Import Employee ID via Bulk or Script

    Posted 08-01-2023 13:10
    No replies, thread closed.

    Does your org use a platform that could leverage SCIM provisioning?  It's actually included by default in that, and would also negate the need for the manual imports.



    ------------------------------
    Paul McGurn
    Manager, Telecom & DevOps
    GoTo
    ------------------------------

    Original Message


  • 7.  RE: Import Employee ID via Bulk or Script

    Posted 08-07-2023 07:02
    No replies, thread closed.

    Hi Paul,

    yes, we have Azure Active Directory. We implemented it now in Azure Active Directory and works fine. :)

    BTW - We needed to create a token via Postman being valid for 86399 seconds - any idea how to extend this?
    At the moment our SCIM Job is running at request but should run otherwise automatically every 40 minutes (general Org Setting for all integrations)

    https://help.mypurecloud.com/articles/configure-azure-active-directory-for-genesys-cloud-scim-identity-management/



    ------------------------------
    Christoph Dittmer
    Sixt SE
    ------------------------------

    Original Message


  • 8.  RE: Import Employee ID via Bulk or Script

    Posted 08-07-2023 09:15
    No replies, thread closed.

    Chris that time is not a problem, which equates to 24 hours.  This is for an individual session.  Each time Azure initiates a new connections the timer starts over again.  The timer needs to be long enough for any given session to complete all of it's processing.



    ------------------------------
    Mark Pierson
    Ally Financial
    ------------------------------

    Original Message


  • 9.  RE: Import Employee ID via Bulk or Script

    Posted 08-07-2023 09:50
    No replies, thread closed.

    As long as you set up a SCIM-specific OAuth client to generate your token, Azure AD will be all set.  When I was first setting up SCIM on our org, the documentation was a bit weaker, so I didn't realize there was a way to set up a SCIM OAuth client.  A regular OAuth client will work, but will only work until that session dies.  The SCIM-specific configuration will last ~14 months before you need to re-do the token process in Postman.  In my case, that flow lets me create an OAuth client with a session duration of 38880000 seconds (max for the field, even though it says 48 hours is the max).



    ------------------------------
    Paul McGurn
    Manager, Telecom & DevOps
    GoTo
    ------------------------------

    Original Message


  • 10.  RE: Import Employee ID via Bulk or Script

    Posted 08-07-2023 11:23
    No replies, thread closed.

    I guess we can't edit messages here?

    You want to follow this article for setting up the OAuth client specific to SCIM.  Note that it has a "Genesys Cloud SCIM" tab, which is what you want.  You need to assign the "SCIM Integration" role to yourself, so you can assign it to the OAuth client, and that is what lets you increase the session duration to something more practical than 48 hours.

    https://help.mypurecloud.com/articles/create-an-oauth-client/



    ------------------------------
    Paul McGurn
    Manager, Telecom & DevOps
    GoTo
    ------------------------------

    Original Message


  • 11.  RE: Import Employee ID via Bulk or Script

    Posted 08-08-2023 07:19
    No replies, thread closed.

    Thanks Paul,

    very helpful. SCIM is running smooth now. 

    Thanks everyone for quick assistance!



    ------------------------------
    Christoph Dittmer
    Sixt SE
    ------------------------------

    Original Message


  • 12.  RE: Import Employee ID via Bulk or Script

    Posted 08-16-2023 10:29
    No replies, thread closed.

    Hi Paul,

    do you also have experiences with Azure AD and SCIM transferring Profile Pictures from Azure to Genesys as this is not part of the basic SCIM functions of Genesys?

    Regards,

    Christoph



    ------------------------------
    Christoph Dittmer
    Sixt SE
    ------------------------------

    Original Message


  • 13.  RE: Import Employee ID via Bulk or Script

    Posted 08-16-2023 11:48
    No replies, thread closed.

    Hi Christoph,

    As you noted, Genesys' SCIM doesn't support image sync, so you'd have to write a script to do this directly.  Thankfully the PATCH /api/v2/users/{userid} does support that, and in a relatively simple way.  You can set images by passing in the resolution and a URL to the image.  Microsoft Graph (Azure AD) API supports getting those image URL's and you can even specify the resolution you want to get.

    My company doesn't force this, but if I were to attack this as a project, my script would:

    1. Call GET /api/v2/users to get a list of users in GCCX
    2. Iterate that list to find any users that don't have at least one image URL
    3. Query Graph API to get those URL's
    4. Call PATCH /api/v2/users/{userid} to update those users with photos

    If you want a more robust/ongoing sync, you'd call this on a schedule and instead of filtering your GCCX user list by ones with no images, you'd query the graph API for a list of users that have had account changes since the last run, then update those users' photos only.  I would not recommend blindly runing this PATCH API without logic to ignore unchanged recorded unless Genesys can confirm it won't attempt to re-download the image if the URL is unchanged.



    ------------------------------
    Paul McGurn
    Manager, Telecom & DevOps
    GoTo
    ------------------------------

    Original Message


Related Content