Using REST APIs to Create and Manage Learning Assignment Profiles in Oracle Learning Cloud- Part 1

Introduction

Oracle introduced the Redwood Assignment Management experience to provide learning specialists with a unified way to create, manage and monitor learning assignments.

Learning Assignment Profiles play an important role in the design of the Oracle Learning Module. In Part I, I will cover the basics. In Part II, I will explore different use cases and provide sample REST API payloads for each. In Part III, I will explain how to use learning assignment profiles to set up renewal rules as part of learning data conversion.

A central component of this design is the Learning Assignment Profile. Administrators can create either:

• A one-time profile, which evaluates its audience once; or
• A continuous profile, also described by Oracle as an automatic profile or initiative, which periodically reevaluates its audience.

Continuous profiles provide the Redwood equivalent of Learning Initiative functionality. They can assign learning when employees become eligible and, depending on the configured rules, withdraw incomplete assignments when employees leave the target audience. Oracle describes these profiles as “one-time and automatic (initiatives) learning assignment profiles,” so it is more accurate to view the assignment profile as the unified Redwood model than as a completely unrelated replacement object.

What is a Learning Assignment Profile?

A Learning Assignment Profile defines:

• The learning item being assigned
• Whether the assignment is required or voluntary
• The learner audience
• Initial and ongoing start and due dates
• One-time or continuous audience processing
• Validity and expiration rules
• Renewal and retake rules
• Assignment-conflict rules
• The treatment of incomplete assignments when learners leave the audience
• Assignment notes, related materials and descriptive flexfields

When Oracle processes the profile, it creates individual learning assignments for learners in the selected audience.

Learning Assignment Profiles REST resource

The primary REST resource is:

/hcmRestApi/resources/11.13.18.05/learningAssignmentProfiles

Oracle documents support for GET, POST, PATCH, DELETE and Describe operations, subject to the applicable security privileges. The delivered aggregate privilege is Manage Learning Assignment Profiles.

The criteria child endpoint is:

/hcmRestApi/resources/11.13.18.05/learningAssignmentProfiles/{learningAssignmentProfilesUniqID}/child/learningAssignmentProfileCriteria

Oracle exposes a POST operation on this child resource to add another audience criterion to an existing profile.

Oracle supports several ways to identify the audience, including:

• ORA_DEST_INDIVIDUAL- Individual people
• ORA_DESI_PERSON_FILE-Person-number or email CSV files
• ORA_WORKER_ASGN_FLTRD_LST- Worker-assignment filtered lists
• ORA_LEARNER_ASGN_FLTRD_LST-Learning-assignment filtered lists
• ORA_DEST_ANALYSIS-Analysis reports
• ORA_LEARNING_ORGANIZATION-User groups
• ORA_DEST_ORG-Manager hierarchies
• ORA_DEST_DIRECT-Direct reports

The audience is represented by the learningAssignmentProfileCriteria child resource.

Get Ritwick Chatterjee’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

The identifier attribute depends on the selected criteria type. For example:

• User groups use assignmentProfileCriteriaTypeNumber with the User Group Number.
• Filtered lists use assignmentProfileCriteriaTypeId with the filtered-list ID.
• Person number or email csv lists use AsyncTrackerId, FileName and DatatypeCode (value:FILE)
• Analysis-based criteria use reportName.
• Individual peoplecan be represented using the assignmentProfileCriteriaTypeId as person id

Do not assume that every criteria type uses the same ID field.

Important points to remember

The assignmentProfileNumber is generated by Oracle after the profile is created. It should not normally be invented or manually supplied in the POST payload. A successful POST returns the generated profile number and the profile’s REST links.

Required request headers

For POST

REST-Framework-Version: 9
Content-Type: application/json
Accept: application/json

For PATCH

Effective-Of: RangeMode=UPDATE

Query an learning assignment profile by profile number

Request

GET https://<host>/hcmRestApi/resources/11.13.18.05/learningAssignmentProfiles?finder=findByAssignmentProfileNumber;pAssignmentProfileNumber="OLC303073"

Retrieve the profile’s audience criteria

To retrieve the audience, follow the learningAssignmentProfileCriteria child link returned by the parent GET:

GET https://<host>/hcmRestApi/resources/11.13.18.05/learningAssignmentProfiles/{learningAssignmentProfilesUniqID}/child/learningAssignmentProfileCriteria

Example: Create a continuous required learning assignment profile using user group

The following example creates a continuous required assignment profile using an Oracle Learning user group.

The values are illustrative and must be replaced with valid values from the target environment.

{
  "dataSecurityPrivilege": "ORA_LEARN_SPECIALIST",
  "assignAs": "IP_MYLEARNING",
  "assignmentProfileTitle": "Expires 365 days after completion- RestAPILoad-3",
  "assignmentProfileStartDate": "2026-10-01",
  "assignmentType": "ORA_REQUIRE_ASSIGNMENT",
  "assignmentRecordStatus": "ORA_ASSN_REC_ACTIVE",

  "assignmentDueDateType": "ORA_RELATIVE_DATE",
  "assignmentDueIn": 30,
  "assignmentDueInUnits": "ORA_DAYS",

  "processingRule": "ORA_WLF_ASSGN_PRULE_AUTOMATIC",
  "processingFrequency": "ORA_WLF_ASSGN_PRO_FREQ_DEFAULT",
  "ongoingDueDateType": "ORA_RELATIVE_DATE",
  "ongoingDueIn": 30,
  "ongoingDueInUnits": "ORA_DAYS",
  "withdrawOnProcessing": "Y",

  "enableRenewals": "Y",
  "validityPeriodBeginRule": "ORA_AFT_COMP",
  "validityPeriodExpiryRule": "ORA_EXP_RELATIVE_DATE",
  "renewalPeriod": "ORA_REL_TO_PRIOR_COMPLETION",
  "renewalOption": "ORA_RENEW_BF",
  "dueInNumber": 365,
  "dueInUOM": "ORA_DAYS",
  "reassignNumber": 30,
  "reassignUOM": "ORA_DAYS",

  "existingCompletionValidityRule": "ORA_FORCE_RETAKE_EXP_COMPL_CD",
  "retakeRule": "ORA_RETAKE_LEARNING",
  "increaseMaximumCapacity": "N",
  "waivePrerequisites": "N",
  "withdrawOnProcessing": "I",
  "learningItemNumber": "OLC479963",

  "learningAssignmentProfileCriteria": [
    {
       "assignmentProfileCriteriaType": "ORA_LEARNING_ORGANIZATION",
       "assignmentProfileCriteriaTypeNumber": "OLC489991"

    }
  ]
}

For Individual records

  "learningAssignmentProfileCriteria": [
    {
      "assignmentProfileCriteriaType": "ORA_DEST_INDIVIDUAL",
      "assignmentProfileCriteriaTypeId": 3000000000000001
    }
  ]

Conclusion

Learning Assignment Profiles provide the central rule framework for Redwood assignment management in Oracle Learning Cloud. They unify one-time assignments and automatic initiatives under one model while supporting flexible audiences, lifecycle controls, renewals, validity rules and conflict management.

The REST API makes this configuration available for controlled automation. A reliable implementation should:

1. Use the correct learning item and audience identifiers (use dynamic crtieria such as user group, analysis etc.)
2. Let Oracle generate the assignment profile number.
3. Represent audiences through learningAssignmentProfileCriteria.
4. Use finder queries and returned REST links instead of constructing composite keys.
5. Validate both the profile and the learner assignments generated from it.
6. Test audience reconciliation, renewals and withdrawal behavior before moving the integration into production.

Used carefully, the API can reduce manual setup while preserving the assignment, audience and compliance controls expected from Oracle Learning’s Redwood administration experience.