Skip to main content Skip to complementary content

Setting task parameters

Set task parameters to gather information about Tasks in the cloud.

About this task

Task parameter values are computed by Talend Management Console during the execution of a Task. Task parameter values that you define in the Studio are not published along with the Artifact.

You can import task parameters to a Artifact using the dedicated Flow context group, available from the Talend Cloud demo project under Contexts > TalendCloud > Flow 1.0. This context group contains all the available task parameters.

Prerequisites: To import context task parameters to an Artifact:


  1. In the Studio workspace, open the Contexts view of the Artifact.
    If the Contexts tab does not show in the Studio, click Window > Show view > Talend , and select Contexts.
  2. Click the icon to open the Select Context Variables dialog box.
    This dialog box lists all context groups created and saved in the Repository tree view of the Studio.
  3. Select the check box of the context variables you want to import from the Studio repository and click OK.
    The context variables are imported and listed in the Contexts view.


  4. In the Repository tree view, drop the predefined Joblet under Job Designs > Joblets to the Designer workspace.
  5. Double-click the tJobLog component to open its basic settings view.
  6. In the Log message field, type context.flow and press Ctrl+Space to display the list of the task parameters you can insert.
    Repeat the action for other task parameters.
  7. Run the Artifact in Studio to test it.
  8. Publish the Artifact to Talend Management Console.


When you publish the Artifact to the cloud and run a Task containing this Artifact, you can view the information you have input in the tJobLog component within the Task logs.

By default, the Task Execution ID and Task ID are visible in the execution log of the Task.


Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!