nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

use of variables in usertask, grouptask, submittask

niniti

variables element is used for defining a variable, which can be used in a script. These variables are passed to a script in externaltask at command line. If there is no externaltask then there is no script to use these variables. So whats the use of variables for such tasks like submittask, usertask, grouptask etc. How will the variables defined in these tasks be used ?

Thanks

Find more posts tagged with

Comments

vaibhav2288

variables element is used for defining a variable, which can be used in a script. These variables are passed to a script in externaltask at command line. If there is no externaltask then there is no script to use these variables. So whats the use of variables for such tasks like submittask, usertask, grouptask etc. How will the variables defined in these tasks be used ?

Thanks

About grouptask, we can use this global variable value in "shared by" property of task.

ISCBorisB

variables element is used for defining a variable, which can be used in a script. These variables are passed to a script in externaltask at command line. If there is no externaltask then there is no script to use these variables. So whats the use of variables for such tasks like submittask, usertask, grouptask etc. How will the variables defined in these tasks be used ?

Thanks

Job and Task variables are WF persistent entities that you can use to provide some information to
the tasks and exchange information between tasks during Job execution.

Variables value can be set and modified during instantiation (within wft code in your case) or run-time
during Job execution or both. Variables may be obtained by the Task's code, both custom (external, url,
cgi tasks) and OTB like the code behind submittask.

IMO you should not pass variables to the tasks through command line flags/parameters. There is of course
nothing to stop you from doing it but that's a serious blunder. Both Perl and CSSDK provide an API to
get/set Job and Task variables.