Configure Task Output

click the integration, outputs tab to configure how swimlane will handle the task's output to add new output, first specify the output type update current record sets field values for a current record this method, which modifies an existing record with the task's output data, must be initiated with triggers, workflow, or by manual integration you can have one mapped per task send an email sends parameters in an email create / update records creates or updates records from the data returned by running the task if the task returns a sequence of data, you can create or update multiple data records save to file saves to specified file execute another task associates the task output to another task, passing the output to the next task as an input make sure that the swimlane field and the source field type are both set up to handle the parameters for the output! the next steps will help you map task output data and parameters to swimlane fields you can also specify specific parameters for the task's output, for example, attachments parameter values you have to map, or review, parameters for output types, although mapping can be different for each configuration either you, or swimlane's automapping process can assign parameter values during the mapping some parameters such as output parameters and run status parameters are available for automapping however, standard output, input parameter, and system output parameters are never part of auto mapping and will need to be mapped manually for additional information on automapping, see docid\ hhop0sufcmyxmb64p6zjj here are the parameter values that can be assigned standard output uses the standardized stream of data produced from your command line program or script input parameter uses your input parameters (from script or integration data) and converts them directly to output without any modifications output parameter uses data emitted by the task in its formal output variables for tasks, you can review parameters on the output parameters tab for python script tasks, the parameters are those added to sw outputs as seen in the code example below you can discover and add scripted parameters to your tasks from the output parameters tab prior to mapping them in your task for example, here is some python code ip addr = "10 10 1 1" mac addr = mac getaddr() sw outputs append({"ip address" ip addr, "mac address" mac addr}) you can use jsonpath or jsonpath in output mapping to query objects for a tutorial on using jsonpath, please see the rest api tutorial, https //restfulapi net/json jsonpath/ you can also utilize this https //jsonpath com/ for jsonpath examples, please see docid 3wpfrs iqla1e6udcfoai for more on jsonata, see the https //docs jsonata org/overview\ html and use this https //try jsonata org/ as a playground within which you can test your jsonata run status parameters output parameters that contain information about the status of the execution of the task, and any potential errors the following 4 parameters are available sw task status the status of the execution can be either success or failure sw task error type in case of failure, contains the type of python exception that has been raised (i e attributeerror ) otherwise, it contains an empty string sw task error message in case of failure, contains the python error message otherwise, it contains an empty string sw task stack trace in case of failure, contains the python stack trace otherwise, it contains an empty string example if you try to import a python package that is not installed or does not exist, the status output parameters will have the following values { "sw task status" "failure", "sw task error type" "modulenotfounderror", "sw task error message" "no module named 'swimlane'", "sw task stack trace" "traceback (most recent call last) \n file \\"/app/tasks/pythonqueue/abpe b4d3yjyn gso/script 4593168cdbeb6eeb61277749ab4b6f647148ce0868314d4d675e07ff9394430d py\\", line 58, in \<module>\n import swimlane\nmodulenotfounderror no module named 'swimlane'\n", } status parameters ensure that every task execution has outputs in some cases, this can cause empty records to be created, even if the task did not return any other outputs for example, if there is a scheduled task that pulls unread emails from a monitored mailbox, it will create a blank record even if there are no new emails to pull if any of the status parameters are mapped