You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -346,4 +343,52 @@ Sample User Apps/Modules/Scripts
346
343
347
344
``notify_args``
348
345
349
-
This is also a dictionary, any items it carries will be passed to the notification service as input arguments.
346
+
This is also a dictionary. In general, any items it carries will be passed to the notification service as input arguments.
347
+
However, if we want to include detailed result data and/or error information in the notification,
348
+
then what parameter name(s) does the notification service use to receive them?
349
+
We make a convention to use two special keys in this dictionary to indicate these two particular parameter names:
350
+
351
+
- '``[=]``' key: the value of this special key indicates the parameter name through which the notification service will receive detailed **result data**.
352
+
*(this is optional) If not specified, detailed result data will not be sent to the notification service;*
353
+
354
+
- '``[!]``' key: the value of this special key indicates the parameter name through which the notification service will receive detailed **error information**.
355
+
*(this is optional) If not specified, detailed error information will not be sent to the notification service;
356
+
in this case, the notification itself cannot tell whether the process has completed successfully or encountered any errors,
357
+
then the notification service may require some other channel to know whether the process succeeded or failed.*
358
+
359
+
|
360
+
361
+
Let's end this section with an example payload that covers as many options as possible:
0 commit comments