<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00008j6C5YSAUOkta Classic EngineLifecycle ManagementAnswered2024-03-25T19:50:53.000Z2020-06-11T14:24:17.000Z2020-06-18T15:34:13.000Z

eifjo (eifjo) asked a question.

Contractor conversion to Employee

We are using WDAAM and contractor to employee is not working in our preview environment. Our WD POC ends the contract with conversion reason in WD, but OKTA is not deactivating the contract account nor it is disabling the AD account. Its seems that OKTA is not even processing the conversion transaction from WD. Few weeks ago we successfully tested this process. Right before going live, we rolled back (mastered by AD) and then roll forward (mastered by WD). After the roll forward, we started to experiencing a lot of issues with termination and conversions.


  • For contractor conversion to full time employee you will need (WORKDAY_VERSION29_API_UPGRADE_AND_PERFORMANCE_IMPROVEMENTS). This feature is Generally Available for new orgs only. For existing orgs, it remains in Early Access; contact Okta Support to enable it.

    In order to be able to use Workday Contractor to Full-Time Employee conversion support, you must modify your Workday tenant setup to configure Universal ID for workers first. Once configured, Universal ID only applies to newly created workers of the tenant. In order to back port it to existing workers you must manually update these Workday profiles using Workday's API. Without a Universal ID, Okta will be unable to detect that a contractor has been converted to full-time. This may lead to duplicate workers in some cases.

     

    Expand Post
This question is closed.
Loading
Contractor conversion to Employee