Integration allows us to establish interaction between CloudAssess and onCourse enrol system. 1. Add enrolments to CloudAssess automatically as they are enrolled in onCourse.

cloudassess {
    name "cloud assess integration 1"
    action "enrol"
    enrolment e
}

Name property here is the name of CloudAssess integration which should be created in onCourse beforehand. 2. Specify a CloudAssess course code which is different to the onCourse course code with the options 'code' parameter.

cloudassess {
    name "cloud assess integration 1"
    action "enrol"
    enrolment e
    code "ABCT.2017"
}

3. Create a course in CloudAssess.

cloudassess {
    name "cloud assess integration 1"
    action "course"
    courseName "ISH Test Course 1"
    code "ABCT.2017"
    qualification "SITHFAB201"
}

This syntax will create a course with the name and code as specified. CloudAssess has a concept of "qualification" which is different to the onCourse Qualification. In CloudAssess it represents something more like a "course template". If this course code already exists in CloudAssess, then this script does nothing and doesn't throw an error. Because CloudAssess doesn't cope well with thousands of enrolments in a single course, this feature is useful to split up enrolments into one CloudAssess course per month (or any other period). 4. Fetch outcomes from CloudAssess

updated_outcomes = cloudassess {
    name "cloud assess integration 1"
    action "outcomes"
    since now - 7
}

This will return a list of outcomes modified in CloudAssess in the last 7 days. These outcomes are in a different context to the one the script runs in, so you'll need to copy them across in order to save the data in onCourse.

updated_outcomes.each() { o ->
    def o1 = args.context.localObject(o)
    o1.status = o.status
}
args.context.commitChanges()

 
        public 
        CloudAssessSpec
     {
}