Training and certificates
Oracle HCM to GoodHabitz integration: access from Oracle, completed training back as an external learning record
With an integration between Oracle HCM Cloud and GoodHabitz, Oracle automatically decides who can use GoodHabitz, and every completed training or passed test arrives as an external learning record on the employee in Oracle Learning. Anyone who leaves or does not show up loses access as soon as Oracle records it.
What the integration does
International organisations with Oracle HCM Cloud that offer GoodHabitz to their Dutch or European employees often manage access with lists per country. What employees complete in GoodHabitz is not in Oracle Learning, so the learning history there is incomplete as soon as HR reports on development or mandatory training.
- KoppelHet follows new employees, changes and departures in Oracle HCM for the legal employers with a GoodHabitz licence.
- Those employees get access through the sign-in method of your GoodHabitz environment, such as single sign-on; leavers and no-shows lose it.
- KoppelHet fetches completed training and passed tests from GoodHabitz and adds title and language.
- KoppelHet looks up the employee in Oracle through the work address and creates an external learning record with date and score.
Back: Completed trainings · Passed tests with score
What to watch for with Oracle HCM Cloud and GoodHabitz
- A learning record in Oracle belongs to the internal person ID, while GoodHabitz identifies an employee by the ID passed when a training is launched, usually the work address. KoppelHet keeps track of which work address belongs to which Oracle person ID, including after an address change, so earlier completions stay with the same person.
- GoodHabitz trainings are not in the Oracle catalogue. Oracle Learning can record external learning with a non-catalogue learning item on the learning record. KoppelHet creates such an external record per completion with title, date and score, instead of rebuilding the whole GoodHabitz catalogue in Oracle first.
- Oracle reports in a separate feed when a work relationship is cancelled, for example when someone does not show up. Such a person may already have been given GoodHabitz access. KoppelHet then withdraws that access, just as with a normal termination.
- A hire with a future start date already appears in the Oracle feed. KoppelHet only grants GoodHabitz access on the start date, so a licence is not used by someone who ends up not starting.
- GoodHabitz delivers progress per GoodHabitz organisation, while Oracle works with legal employers. A group with a separate GoodHabitz organisation per country gets a translation per organization_id to the legal employer in KoppelHet, so a completion never lands on a namesake in another country.
- GoodHabitz returns a test score from 0 to 100 and Oracle has a field for the achieved score on the learning record. KoppelHet only puts the score of a passed test into Oracle, so a failed attempt does not appear as a result in the learning history.
- GoodHabitz allows ten requests per minute per API key and returns progress per window of at most seven days. Oracle calls are not bound by that. KoppelHet fetches GoodHabitz steadily period by period and then writes the records into Oracle, so a slow run skips no completions.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Does the integration create accounts in GoodHabitz?
Not directly; GoodHabitz has no API for it. Access runs through your environment's sign-in method, and KoppelHet makes it follow Oracle HCM.
Do we need Oracle Learning?
For writing back, yes, because the learning records belong there. Without Oracle Learning the integration is limited to access.
Do single lessons go to Oracle too?
No. Only a completed training or a passed test becomes a learning record, so the history stays clear.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM is read through the Employee Atom feeds (newhire, empupdate, empassignment, termination and cancelworkrelship) and the workers REST resource (PersonId, PersonNumber, WorkEmail, legal employer). Learning records go to Oracle Learning through POST /hcmRestApi/resources/11.13.18.05/learnerLearningRecords with the learningItemDetails child resource for external learning, with assignedToId, completedDate, actualScore and learningItemTitle (at most 250 characters).
- GoodHabitz is read through the GoodHabitz API v2 with an API key from support (10 requests per key and 20 per IP per 60 seconds). GET /v2/contents with modified_since, /v2/deleted-contents, /v2/milestones (Started, Finished, TestPassed, TestFailed) and /v2/progress (progress_percentage, test_score), per organization_id, window at most seven days. No endpoint to create users; access through SSO.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in GoodHabitz | Notes |
|---|---|---|
PersonNumber | Sleutel in de koppeling | |
WorkEmail | user_id | The ID GoodHabitz receives at launch |
Legal employer | Toegang en GoodHabitz-organisatie | Per organization_id |
Termination of cancelworkrelship | Toegang intrekken | |
content_id (terug) | learningItemTitle | Title from the catalogue, at most 250 characters |
event Finished of TestPassed (terug) | Extern leerrecord | Started and TestFailed stay in GoodHabitz |
timestamp (terug) | completedDate | |
test_score (terug) | actualScore |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud