HCM Studio
Sign in

Reference

Resources

Where to look, and how much to trust each kind of source. A source is only useful if you know what it is authoritative for and what it is not.

  • Oracle documentationExternal

    Authoritative for behaviour in a given release. Read the release-specific version, not a blog post describing it, because configuration differs by release.

  • Oracle UniversityExternal

    Official training and certification outlines. Where our coverage and theirs disagree, theirs wins.

  • HCM Studio glossaryInternal

    26 terms across 7 modules, with the confusions each term is commonly confused with.

  • ProceduresInternal

    Step-by-step configuration with pre-checks, required evidence, failure modes and rollback paths.

  • Source registerInternal

    Every claim in this academy, with its source, last verification date and recorded gaps.

Reading HCM sources critically

  • Check the release before the detail. Task names and eligibility rules change between releases. Advice written for 24D that has not been re-checked for 26D is a guess.
  • A blog post is an opinion until linked to a doc. Vendor documentation states what the product does; a blog states what one person did once.
  • A screenshot is not evidence. If it does not show the release and the client groups, it cannot be acted on.
  • A step with no verification is not a procedure. If you cannot say how to confirm it worked, you cannot tell whether it is safe to proceed.