#1818: no longer send triggered send key / id during CREATE and dont …

…save it during templating to ensure a clean new clone in the journey metadata
Accenture · Nov 2, 2024 · e350d1e · e350d1e
1 parent 6916f4c
commit e350d1e
Showing 1 changed file with 28 additions and 0 deletions.
diff --git a/lib/metadataTypes/definitions/Journey.definition.js b/lib/metadataTypes/definitions/Journey.definition.js
@@ -118,12 +118,40 @@ export default {
             retrieving: true,
             template: true,
         },
+        'activities[].configurationArguments.triggeredSendKey': {
+            // if used during create then we are stuck with old data
+            isCreateable: false,
+            isUpdateable: true,
+            retrieving: true,
+            template: false,
+        },
+        'activities[].configurationArguments.triggeredSendId': {
+            // if used during create then we are stuck with old data
+            isCreateable: false,
+            isUpdateable: true,
+            retrieving: true,
+            template: false,
+        },
         'activities[].configurationArguments.triggeredSend': {
             isCreateable: true,
             isUpdateable: true,
             retrieving: true,
             template: true,
         },
+        'activities[].configurationArguments.triggeredSend.id': {
+            // if used during create then we are stuck with old data
+            isCreateable: false,
+            isUpdateable: true,
+            retrieving: true,
+            template: false,
+        },
+        'activities[].configurationArguments.triggeredSend.key': {
+            // if used during create then we are stuck with old data
+            isCreateable: false,
+            isUpdateable: true,
+            retrieving: true,
+            template: false,
+        },
         'activities[].configurationArguments.triggeredSend.autoAddSubscribers': {
             isCreateable: true,
             isUpdateable: true,