This line was removed.
This word was removed. This word was added.
This line was added.
Comment: Added a note about insert/merge
Changes (2)View page history
|However we do not want an invalid design saved if possible. For example, if the design is saved with a transition missing, the server may calculate the wrong activity as the first activity and any new learners might get an activity PASSED the stop gate as the first activity. They will also get progress bar that has only part of the design. If this occurs it won't do any damage - the live edit + read only check mentioned previously will ensure that the lesson is not damages. However it will look odd and is likely to confuse people. |
|It is not easy change the server to not save an invalid design (as it would mean a major rewrite of the design update code or relying on a database rollback) so the validation to check for missing transitions will be added to the authoring client for edit on the fly. If the staff try to save and exit the live edit mode, mode (using the Apply Changes button), the client will detect the invalid transition and not let them proceed. |
|However if the staff does an insert/merge then the design will become invalid. (Insert/merge was introduced in LAMS 2.1.) When they do the insert, it will save the current design (irrespective of the validity) and call the insert method on the server. Even if the design wasn't invalid before, it will be after the insert. This isn't the most optimal situation, but it is impossible to avoid given the current implementation of insert/merge. Cancelling is now not possible so the Cancel button is disabled. If the staff try to save and exit the live edit mode (using the Apply Changes button), the client will detect the invalid transition and not let them proceed. |
|h4. Converting Data From LAMS 2.0 |