...

OfferingRuleGenerator.exe Instructor -f "D:\temp\2022-03-22-Instructor-NewOfferingRuleMatrix.csv" -p /Root/TestOrg -o "D:\temp\2022-03-22-Instructor-NewOfferingRuleMatrix-Commands.txt" -v
OfferingRuleGenerator.exe Student -f "D:\temp\2022-03-22-Registration-NewOfferingRuleMatrix.csv" -p /Root/TestOrg -o "D:\temp\2022-03-22-Registration-NewOfferingRuleMatrix-Commands.txt" -v

Notes

• Registration Rules ignores ignore the rows De-Registration Rules and Users (UserNames)

• Instructor Rules ignores the row Users (UserNames)

...

List user names (separated with pipe '|') who should get registered in the current course independent of their OPF values. It is important to note that all the x for OPF values are ignored for that user - this is realized in creating one registration rule per user.
The any settings for that course (column) are included in the registration rule. Therefore, the users would still adhere to the prerequisites, Registration Type and , certificate configuration and OPF values for the course.

Notes:

• This predicate is used similar to OPFs - it indicates the specific users who should get registered

• De-Registration can be used with the User Users predicate!

• The currently existing predicate IsUser can’t take multiple users - Core needs to be extended to a predicate likeas a (temporary) work-around the Offering Rule generator will generate one offering rule per user (including any other configurations for that column).

• The IsUser predicate will need to be replaced in the future to take multiple users:

  Users(userName1|userName2|…)

  which should work similar to ProfileValueIn with multiple values but checking for users. Any user in the list should get registered. This makes it possible to add one offering rule instead of one offering rule per user.

Instructors

Additional Rows

...

List user names (separated with pipe '|') who should get added as instructors for the course independent of their OPF values set further below. It is important to note that all the x for any selected OPF values are ignored for that user - this is realized in creating one instructor rule per userincluded in the instructor rule as well.

Notes:

• This predicate is used similar to OPFs - it indicates the specific user(s) who should get registered and not necessarily defining under which circumstances (i.e. expiring certificate, prerequisites).Remove Instructor does not have any affect on users mentioned in Users row.added as instructor(s)

• Remove Instructor can be used with the Users predicate!

• The currently existing predicate IsUser can’t take multiple users - Core needs to be extended to a predicate like- as a (temporary) work-around the Offering Rule generator will generate one offering rule per user (including any other configurations for that column).

• The IsUser predicate will need to be replaced in the future to take multiple users:

  Users(userName1|userName2|…)

  which should work similar to ProfileValueIn with multiple values but checking for users. Any user in the list should get registeredget added as instructor. This makes it possible to add one offering rule instead of one offering rule per user.