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; } } }

WF level Variable (TS 6.5 , Windows 2003)

wild123

Hi

I have a series of tasks to be performed like this :-

(1)External Task :: deploy to Branch B from Branch A and submit to staging ------>(2)External Task :: Build Edition --------->(3)External Task :: deploy
edition----------->(4) User Task abc --------->(5) End

Now I want to create a workflow level variable editionNo . This variable will be passed on to (2) task to build edition , later it will be passed on to (3) task to deploy this edition.

I am building the workflow level variable based on the timestamp. I will have to loopback from (4) to (3) as per the requirement. How can I make sure that when I loop back from (4) to (3) , the edition number that was used the first time by task (3) is used the second time as well incase of loop back ? I fear that it might change as per the timestamp assigned to the workflow level variable .

How do I resolve the problem?

Thanks in advance

Find more posts tagged with

Comments

Ambuj

Hi

I have a series of tasks to be performed like this :-

(1)External Task :: deploy to Branch B from Branch A and submit to staging ------>(2)External Task :: Build Edition --------->(3)External Task :: deploy
edition----------->(4) User Task abc --------->(5) End

Now I want to create a workflow level variable editionNo . This variable will be passed on to (2) task to build edition , later it will be passed on to (3) task to deploy this edition.

I am building the workflow level variable based on the timestamp. I will have to loopback from (4) to (3) as per the requirement. How can I make sure that when I loop back from (4) to (3) , the edition number that was used the first time by task (3) is used the second time as well incase of loop back ? I fear that it might change as per the timestamp assigned to the workflow level variable .

How do I resolve the problem?

Thanks in advance

Please post your code as how you are creating the editionNo and how you are transferring / passing it to next external task...

wild123

Please post your code as how you are creating the editionNo and how you are transferring / passing it to next external task...

I have attached my WFT file.

Thanks

kaalraa

I have attached my WFT file.

Thanks

I dont think it should get changed once your workflow got initiated. I hope you have the understanding of the difference between a Workflow and a Job.

So, dont fear... and try to run the workflow. Also if needed, use the CLT iwgetwfob {jobid/taskid} to see as what is the value of the variable at any point of time (When you job is activated).

wild123

I dont think it should get changed once your workflow got initiated. I hope you have the understanding of the difference between a Workflow and a Job.

So, dont fear... and try to run the workflow. Also if needed, use the CLT iwgetwfob {jobid/taskid} to see as what is the value of the variable at any point of time (When you job is activated).

What I assumed was :

Timestamp when task (3) was initiated would be 23456 (fetched from wf variable) but when loop back happens and (3) again takes place a new time stamp lets say 78923 is fetched. This is not required. 23456 is needed the second time aswell.

Natasha

Are u looping back to the task where u have created ur job variable?
If yes then u can first fetch the value of the variable in the beginning and if that variable is defined then dont set it again and if it is not defined then set it(which means the script is being called for the first time).
And if the loop back is done to the task in which the variable is not set then no need to do anything as that variable will remain the same through out the job and will not change with the timestamp.

wild123

If yes then u can first fetch the value of the variable in the beginning

How do I achieve it?

Natasha

How do I achieve it?

lets say the variable name is editionNo


my $editionNo =  $job->GetVariable("editionNo);
if(!$editionNo){
    $job->SetVariable("editionNo",$desiredEditionNo);
    where $desiredEditionNo will be the edition no which u want to set with the timestamp.
}

This u can write at the beginning of the script and I guess there wont be any issues regarding the variable being set again and again on the call of the file.

Thanks,
Natasha.

kaalraa

lets say the variable name is editionNo
my $editionNo = $job->GetVariable("editionNo);
if(!$editionNo){
$job->SetVariable("editionNo",$desiredEditionNo);
where $desiredEditionNo will be the edition no which u want to set with the timestamp.
}
This u can write at the beginning of the script and I guess there wont be any issues regarding the variable being set again and again on the call of the file.

Thanks,
Natasha.

Hey Natasha,

Could you pls explain as from where you can get the value for $desiredEditionNo??

Natasha

Hey Natasha,

Could you pls explain as from where you can get the value for $desiredEditionNo??

I guess that will be set as per the requirement i.e the edition which the user wants to deploy.
I have mentioned it as for giving the example that how the user can avoid setting it again and again on the call of the script.

I hope i have made myself clear.

Thanks,
Natasha.

wild123

I guess that will be set as per the requirement i.e the edition which the user wants to deploy.
I have mentioned it as for giving the example that how the user can avoid setting it again and again on the call of the script.

I hope I have made myself clear.

Thanks,
Natasha.

Hey if you look at the file attached above . the editionNo. is generated on timely basis and passed on to a WF variable . All this happens in the wft. and then using get variable it is fetched in the ipl.

Natasha

Hey if you look at the file attached above . the editionNo. is generated on timely basis and passed on to a WF variable . All this happens in the wft. and then using get variable it is fetched in the ipl.

Could u plz post ur code out here as in where u r setting the workflow variable and retrieving the same in th ipl file?

kaalraa

Hey if you look at the file attached above . the editionNo. is generated on timely basis and passed on to a WF variable . All this happens in the wft. and then using get variable it is fetched in the ipl.

Buddy,

As suggested earlier, run your workflow and when it is in active state, just run a CLT - iwgetwfobj {jobid} through command line and read as what value is being defined for your job variable.

You can cross-verify your value with the value you had received in any of the external task from its logs.

HTH

wild123

Buddy,

As suggested earlier, run your workflow and when it is in active state, just run a CLT - iwgetwfobj {jobid} through command line and read as what value is being defined for your job variable.

You can cross-verify your value with the value you had received in any of the external task from its logs.

HTH

Thanks a lot Kaalraa and Natasha
Smiley Happy

Adam Stoller

Hey Natasha,

Could you pls explain as from where you can get the value for $desiredEditionNo??

It should probably be derived at the time that the edition is cut - so something like:

use Date::Format;
...
my $editionNo =  $job->GetVariable("editionNo);
if(!$editionNo){
my $desiredEditionNo = time2str("%Y%d%m_%H%M%S", time);
    my $result = qx($iwhome/bin/iwpublish $vpath STAGING $desiredEditionNo "wf-automated edition" 2>&1);
    if ($?) { 
        # handle potential error
    }
    $job->SetVariable("editionNo",$desiredEditionNo);
    where $desiredEditionNo will be the edition no which u want to set with the timestamp.
}