Versions Compared

Key

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

...

For every customer we should have one RRM which is the truth and applied to the LMS. Maintain the files within the Professional Services Google Drive folder of every customer (https://drive.google.com/drive/folders/0B7g9LwWIoQa2Vnlacmhobk1xRjQ). Some customers will have slightly different workflows on where the RRM file is being maintained (i.e. a shared drive the customer provides) and how they update/add courses. The section Customer Specific Processes 5440513396 below describes any customer specific requirements.

...

  • 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.


Info

Since release v3.0.5+ any updated registration rule needs to be run manually to bring the rule engine up to date. The rules need to be run because rule changes/invalidate the ‘from’ date that the new rule engine uses internally to scan for changes. If you just let the engine run normally after rule updates it might miss people who are: (a) affected by the new rule, and (b) have not changed since the internal from date the engine records.

There are command lines to run the rules only for specific courses, so if you have only changed the rules for a small set you can just run the rules for those (i.e. reEvaluateOfferingRulesByCoursePathMatch (-logOnly, -debug) [RuleType (Registration, Instructor, All)] [string: startPath] [string: terminalElement] [batchSize: optional, default Core.OfferingRuleEvaluatorBatchSize])

The rule engine doesn’t care that the attributes have been updated (i.e. by the rule generator) and doesn’t make any attempt to determine if rules have changed. So its up to a human in this case to decide what rules have changed semantically and ensure to manually run the rules for those courses.


Info

Before updating any registration rule the rule engine needs to be paused.

Commands to pause/continue/check status of the automatic registration rule processing:

  • PauseAutomaticOfferingRuleProcessing

  • getOfferingRuleStatus

  • ContinueAutomaticOfferingRuleProcessing


 

Customer Specific Processes

...