Hi, Richard!
1. Yes, cmi.location should be stored and retrieved to/from LMS. But there are some issues when cmi.location will be ignored by module: it may depend on module statuses (for example, if the received from LMS completion_status is "not attempted", then location will be ignored), or if the cmi.suspend_data is corrupt. If you can give us guest access to this module, then we will tell the reason.
2. Unfortunately, in current version run-time variables are not saved...
Hi, Richard!
1. Yes, cmi.location should be stored and retrieved to/from LMS. But there are some issues when cmi.location will be ignored by module: it may depend on module statuses (for example, if the received from LMS completion_status is "not attempted", then location will be ignored), or if the cmi.suspend_data is corrupt. If you can give us guest access to this module, then we will tell the reason.
2. Unfortunately, in current version run-time variables are not saved...