SAP SuccessFactors logoGoodHabitz logo

Training and certificates

SAP SuccessFactors to GoodHabitz integration: access from Employee Central, completed training as external event in SuccessFactors Learning

With an integration between SAP SuccessFactors and GoodHabitz, Employee Central decides who has access to GoodHabitz, and every training completed or test passed in GoodHabitz then appears as an external learning event in the SuccessFactors Learning history. HR can therefore report on all training in SuccessFactors, also when employees learn directly on the GoodHabitz platform.

What the integration does

Organisations with SuccessFactors Employee Central and Learning that use GoodHabitz alongside their own learning offering only see in SuccessFactors what runs through their own learning platform. When employees learn directly on the GoodHabitz platform, those trainings are missing from the learning history and are checked by hand for audits.

  1. Employee Central decides per company or department who may use GoodHabitz.
  2. The sign-in environment gives those employees access through single sign-on; leavers lose it after the last working day.
  3. KoppelHet fetches period by period which trainings and tests were completed, and adds the title.
  4. Every completion goes to SuccessFactors Learning as an external learning event, on the right employee.
  5. KoppelHet checks per record whether SuccessFactors has accepted it, and reports what was rejected.
SAP SuccessFactors → KoppelHet → GoodHabitzSOURCESAP SuccessFactorsTARGETGoodHabitzKoppelHetmapping · logging · monitoringSAP SuccessFactors → KoppelHet → GoodHabitzSOURCESAP SuccessFactorsTARGETGoodHabitzKoppelHetmapping · logging · monitoring
Out: Employee with work email, company and department · Access to GoodHabitz through the sign-in environment · Training catalogue with titles
Back: Completed trainings · Passed tests with score

What to watch for with SAP SuccessFactors and GoodHabitz

  • For an external learning event SuccessFactors Learning shows no completion status; the grade field is free text there. KoppelHet puts the GoodHabitz test result or the word passed in that field, so it is also visible in SuccessFactors reports.
  • The SuccessFactors Learning API processes a list of learning records on a best-effort basis and returns 201 even if part of them was not accepted. KoppelHet therefore checks the response per record and queues rejected completions again or reports them to HR.
  • GoodHabitz identifies a user by the ID passed at launch, usually the work email. SuccessFactors Learning works with the user ID. KoppelHet looks it up through the work email in Employee Central, and remembers old addresses so earlier training stays with the same employee.
  • GoodHabitz delivers progress per organisation within one API key. If a group has several GoodHabitz organisations, for example per country, KoppelHet links each organisation to the right company in Employee Central.
  • GoodHabitz returns completions per period of at most seven days and allows only ten requests per minute. KoppelHet keeps track of how far it has fetched, and fetches the catalogue separately rather than per completed training.
  • GoodHabitz names SAP as a learning platform it works with, and provides links for LTI 1.1, LTI 1.3 and the web per training. If employees launch GoodHabitz from SuccessFactors Learning, Learning may track progress itself; KoppelHet then only sends completions from outside the learning platform, so nothing appears twice.
  • SAP is ending sign-in to the SuccessFactors APIs with username and password. KoppelHet uses OAuth, with read-only rights in Employee Central and write rights on learning events in Learning.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Why as an external learning event and not as a catalogue training?

An external learning event does not need an item per GoodHabitz training in SuccessFactors Learning. If HR also wants the GoodHabitz trainings as catalogue items, that can follow later as an extension.

Does the integration create accounts in GoodHabitz?

No, the GoodHabitz API cannot do that. Access runs through single sign-on, and who may sign in there follows Employee Central.

Does this work without SuccessFactors Learning?

Access does. For completed training Learning is needed, or another place in SuccessFactors that we choose together.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • SuccessFactors Employee Central through the OData API (v2) with OAuth 2.0 (PerPerson, PerEmail, EmpEmployment, EmpJob with company and department). SuccessFactors Learning through the learningevent-service OData service (ExternalLearningEvents); the response is checked per record because 201 is also returned when processing partly failed.
  • GoodHabitz API v2 with an API key from GoodHabitz support: /v2/contents, /v2/deleted-contents, /v2/milestones (Started, Finished, TestPassed, TestFailed) and /v2/progress (test_score), grouped per organisation. Time window 0 to 7 days; 10 requests per minute per key. No endpoint to create users; access through SSO with SAML 2.0.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in SAP SuccessFactorsField in GoodHabitzNotes
user_id (meestal het werkadres)SuccessFactors-gebruikers-IDLooked up through PerEmail in Employee Central
content_idTitel en omschrijving van het external eventThrough the GoodHabitz content catalogue
timestamp van Finished of TestPassedDatum afgerond
test_score (0 tot 100)GradeFree text field on an external event
durationAantal uren
Organisatie in de GoodHabitz-responsBedrijf (FOCompany) in Employee Central
EmpJob.company en departmentToegang ja of nee

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.