Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The customer would get a pre-filled RRM (courses/OrgProfileField values) where they are able to tick all the requirements for their courses
    1. Preferably, we would fill in the course paths ahead of sending the file to the customer rather than let the customer fill in courses. The customer would only need to tick the OrgProfile values for the courses and decide on de-/re-registration/expiry periods,...
  2. We will double check the validity of the returned RRM
  3. Generate the registration rules using the RRG
  4. Upload/replace all registration rules with the freshly generated reg rules
  5. Upload the RRM file to Google Drive location (and possibly to the customer as a reference)

...

  • Send the full RRM to the customer
  • Send a partial RRM which only contains the new courses/courses they need to update. Because of the amount of courses some customers have, this may make it easier for the customer and us to manage the changes

Generate Registration Rules via RRG Tool

TODO: add full manual on how to use/where to get the RRG tool.

Replace/Upload Registration Rules in LMS

TODO: add full manual on how to replace/upload registration rules created by the RRG.

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@a03
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("registrationrulegenerator","registrationrulematrix","registrationrules") and type = "page" and space = "PS"
labelsRegistrationRules RegistrationRuleGenerator RegistrationRuleMatrix

...