Pipeline return payload different in ultra vs triggered

For the benefit of anyone who’s been following this thread, I ran a simple test using a pipeline with a single Mapper snap:

Running the pipeline as a triggered Task returns:

[
    {
        "StudentXNumber": "X002221",
        "StudentVersion": "7",
        "StudentLoginId": "X002221"
    }
]    

Running the pipeline as an Ultra task returns:

    {
        "StudentXNumber": "X002221",
        "StudentVersion": "12",
        "StudentLoginId": "X002221",
        "original": {
            ... original payload
        }
    }

The two key differences are:

• Regular pipeline returns an array containing the JSON object with the return payload
• Ultra pipeline returns a single JSON object
• Ultra pipeline also includes the original payload.

@dmiller this distinction should probably be noted on the documentation page for Ultra tasks because it means that client code that is calling a triggered task will not work if the task is reconfigured as an Ultra task.