From 4c7aa0920fbde3e8c1fe264ab2e5fbdfed1715c1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=A9sar=20Montilla?= Date: Mon, 24 Apr 2023 19:01:39 +0000 Subject: [PATCH] docs: Add note related to CCX compatibility --- .../decisions/0008-lti-1p3-puggable-lti-configuration.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/decisions/0008-lti-1p3-puggable-lti-configuration.rst b/docs/decisions/0008-lti-1p3-puggable-lti-configuration.rst index f29df85e..fb2ddbb8 100644 --- a/docs/decisions/0008-lti-1p3-puggable-lti-configuration.rst +++ b/docs/decisions/0008-lti-1p3-puggable-lti-configuration.rst @@ -59,6 +59,14 @@ Note: We aren't completely clear on what might need to change appart from _get_lti_1p3_consumer and get_lti_1p3_launch_info in xblock-lti-consumer to allow the use of LTI 1.3 external configurations. +We also need to modify the LtiConfiguration model to sync the changes on +the config store field and external ID field on all CCX XBlocks related to +the master courser XBlock beign modified, this could be achieved by two method, +first by copying the config store and external ID values when a CCX XBlock +LtiConfiguration is beign created and by also sync changes from the master +LtiConfiguration with a post save signal, in that signal we can iterate over +any CCX LtiConfiguration related and sync the config ID and external ID values. + Changes on lti_store ~~~~~~~~~~~~~~~~~~~~