I might be missing something but I realized that if the LRS specified by "endpoint" is down/invalid the whole course just breaks. Is there any way to force the Storyline content to load without bothering with the TinCan stuff, even if it was published with TinCan being enabled?
I noticed that changing tincan in the launch URL param to 'false' makes no difference. I can see that the call to fetch the state from the LRS endpoint fails and the whole course just breaks.
I was more thinking about the use case when you want to allow people to still access your training material even if your LRS system is down (e.g. in view-only mode). In some cases it would be better than not being to view anything at all.
My other related concern was around whether it's possible to disable calls to the State API and only have Statement API calls being made from the exported Storyline content?
Thanks Vadim for the clarification! It sounds like a interesting scenario for the community to tackle, as we don't have a supported method for removing individual Tin Can calls or changing how the content would launch and behave if a LMS/server is down.
Keep us posted on what you come up with - could be interesting for the rest of the community!
3 Replies
Hello Vadim!
Can you catch me up here? I see you posted another issue here, but seems that you were able to sort that one out.
I'm not clear on why you would want to 'ignore the TinCan stuff', when the course was published for TinCan?
Wouldn't it need to make the connection? What would/could the risk be if not connected as it relates to tracking?
Hi Leslie,
I was more thinking about the use case when you want to allow people to still access your training material even if your LRS system is down (e.g. in view-only mode). In some cases it would be better than not being to view anything at all.
My other related concern was around whether it's possible to disable calls to the State API and only have Statement API calls being made from the exported Storyline content?
Thanks Vadim for the clarification! It sounds like a interesting scenario for the community to tackle, as we don't have a supported method for removing individual Tin Can calls or changing how the content would launch and behave if a LMS/server is down.
Keep us posted on what you come up with - could be interesting for the rest of the community!
This discussion is closed. You can start a new discussion or contact Articulate Support.