Timeline for outArguments not appearing correctly in Custom Activity
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2020 at 12:00 | history | tweeted | twitter.com/StackSalesforce/status/1263439461888786435 | ||
| Aug 14, 2017 at 13:18 | comment | added | Doug | Correct, the values are being set on Execute, so they are on the server not client side. In the JSON above, you can see the schema already contains the required outArguments so no need to actively add them to "toJbPayload". or...am I missing something? | |
| Aug 14, 2017 at 8:58 | comment | added | Doug |
the UpdateActivity is certainly called function save() { console.log(ActivityConfig); ActivityConfig.TemplateId = $("#finalTemplate").data("TemplateId"); console.log(ActivityConfig); Object.assign(toJbPayload.arguments.execute.inArguments[0], ActivityConfig); toJbPayload.metaData.isConfigured = true; console.log(toJbPayload); //return to Activity connection.trigger('updateActivity', toJbPayload); }; Also, the outArguments are appearing in the Journey Metadata when accessing it via API.
|
|
| Aug 13, 2017 at 23:58 | comment | added | Eliot Harper | Regarding your second point "Salesforce Activities cannot see the outArguments at all", Out Arguments from Custom Activities can only be used by other Custom Activities, not by Standard Activities. You would have thought that you can use Data Binding (in the Interaction Context) to use Out Arguments from a Custom Activity in a Standard Activity, but this does not appear to be the case. | |
| Aug 12, 2017 at 13:32 | history | asked | Doug | CC BY-SA 3.0 |