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

WFM: Globle variable issue

retesh

Hi All,

PURPOSE: My purpose is to define a global variable and assign its value thru an ipl which gets called by an external task

EXECUTION: I have created a glogal variable. Changed its ID to cname. Then I am accessing this global variable by $IW_CV(cname)

my($task) = new TeamSite::WFtask($taskid);
my($workflow) = new TeamSite::WFworkflow($wfid);
$workflow->SetVariable($IW_CV(cname), $task_owner);

I have also tried:

$task->SetVariable($IW_CV(cname), $task_owner);

But nothing seems to work.

I doubt if I am reffering to the global variable in correct way i.e. $IW_CV(cname). Please throw some light on it!!

-Thanks,
Retesh
_____________________________________
Teamsite 6.7.1 SP1 - WFM 1.0.0.1 @ UNIX

Find more posts tagged with

Comments

moonkhanna

Hi All,

PURPOSE: My purpose is to define a global variable and assign its value thru an ipl which gets called by an external task

EXECUTION: I have created a glogal variable. Changed its ID to cname. Then I am accessing this global variable by $IW_CV(cname)

I have also tried:

But nothing seems to work.

I doubt if I am reffering to the global variable in correct way i.e. $IW_CV(cname). Please throw some light on it!!

-Thanks,
Retesh
_____________________________________
Teamsite 6.7.1 SP1 - WFM 1.0.0.1 @ UNIX

Where did you get a reference on calling the variable like $IW_CV(cname). I would believe it works as below

$workflow->SetVariable("cname");

retesh

Where did you get a reference on calling the variable like $IW_CV(cname). I would believe it works as below

$workflow->SetVariable("cname");

Hi,
I read that in pdf. Even scripts on conditional links showed using script variable in the similar way.

I have tried:

$workflow->SetVariable("cname");

It is not working.

I am writing a log file to debug the code but when I use SetVariable method then the external task gets stucked up and log file doesnt generate.

-Thanks,
Retesh

retesh

Hi All,

Please tell me how do I refer a WFM configurable global variable in my ipl.

Following are the attributes of this variable:

Id: cname
Label: Manager
Default value:
Description:

-Thanks,
Retesh

moonkhanna

Retesh, there have been various posts on this issue. People not able to get the config variables in their external tasks.. but that for previous version of WFM.. with your version, it should just work fine...

Just search for WFM or configurable variable keyword on devnet and you will get to those posts.. If you cannot find, post back and I will search and give you the link

retesh

Retesh, there have been various posts on this issue. People not able to get the config variables in their external tasks.. but that for previous version of WFM.. with your version, it should just work fine...

Just search for WFM or configurable variable keyword on devnet and you will get to those posts.. If you cannot find, post back and I will search and give you the link

Thanks for reffering me to other posts. It provided some information which I will use in my debugging approach.

Now I know that this issue of Global variable is really global :-)

My problem is not solved yet, $IW_CV(cname) is the way to refer global variable in javascript. But in perl ????

-Retesh

Annad

Hi Retesh,
If you have set a CV variable in the WFM, then you should create a task variable in the WFM properties (same place where you create the CV variable). Once you have defined a task variable then in your external perl script create a wf object using the current job id. And access the CV variable like this:

$wf->GetVariable("cname");

I hope this works,

I just started working on the WFM and I got that working.

Regards,
Anna.

retesh

Hi Retesh,
If you have set a CV variable in the WFM, then you should create a task variable in the WFM properties (same place where you create the CV variable). Once you have defined a task variable then in your external perl script create a wf object using the current job id. And access the CV variable like this:

$wf->GetVariable("cname");

I hope this works,

I just started working on the WFM and I got that working.

Regards,
Anna.

Yes GetVariable and SetVariable methods are working on Workflow Variables:

$workflow -> GetVariable('cname');

But My problem is that I am not able to get/set the value of a Workflow Configurable variable thru ipl.

I am using a conditional link in my workflow. The scriplet allows only Configurable variables to be used. Hence I cannot work with Workflow's normal variables in my case :-(

-Thanks,
Retesh

Migrateduser

Hi Retesh -

Did you ever find a solution to updating a configurable variable or gobal variable in an external task? If you did, I was wondering if you wouldn't mind sharing the code. I am trying to do something similiar with the wfm environment. This is something that apparently they don't teach in any Interwoven class or book to my knowledge.

Mike H
Teamsite 6.7.1 Windows WFM 1.0.0.1

Migrateduser

Hi Retesh,

Do you see any error like "Use of uninitialized value in concatenation (.) or string at ....ipl"

Of course it should be something like the below.

my $job = TeamSite::WFworkflow->new($wfid);
my $jobUserEmail = $job->GetVariable('userEmail');

And this to set it:
$job->SetVariable('userEmail');

I believe upgrading your wfm to 1.0.1.0 should fix your problem, where if you are using a global variable, you need to set a JOB variable too. Once you have a look at the job specs screens shot with having and not having a Job Variable, you will understand it.

Thank you
Paul

Migrateduser

Hi All,

PURPOSE: My purpose is to define a global variable and assign its value thru an ipl which gets called by an external task

EXECUTION: I have created a glogal variable. Changed its ID to cname. Then I am accessing this global variable by $IW_CV(cname)

I have also tried:

But nothing seems to work.

I doubt if I am reffering to the global variable in correct way i.e. $IW_CV(cname). Please throw some light on it!!

Hi Ritesh,

Following is the syntex for getting and setting workflow global variables:
$workflow->GetVariable("cname");

$workflow->SetVariable("cname", "NEW_VALUE");

Try this and let me know if this dont works

retesh

Hi atulg,

It's been 3 months that I encountered this issue and eventually got it resolved. Thanks for taking interest in the thread.

The suggestion you have provided is absoloutely correct and I had applied the same. This is mentioned in the guide as well.

But if you go thru this thread in more depth then you will realise that I am talking precisely about the WFM's Configurable variables that have been defined globally thru WFM. Now how would you refer that in your ipl script??

You cannot refer WFM's Configurable Variable in your ipl the same way we use to do with normal workflow variable. I have tried many ways to implement it but got no success!! Hence I did not closed this thread, perhaps I had taken measures to get around this problem. After all project needs to be completed :-)

-Retesh

Migrateduser

Retesh. When you took measures to get around this, then I take it you reverted to the older workflow scripts and abandoned WFM?

Thanks.
Mike

DevIntervowen

Hi Ritesh,

Try this:

1)Suppose you have Global Configurable Variable (name it as "GVVar1") in WFM

2) Create an JobVariable [say name "JVVar1"] and assign it to "GVVar1" created.

3) Then change variable using

$workflow->SetVariable("cname", "NEW_VALUE");

It will change both variable JVVar1 as well as GVVar1 variable

Hope this helps..

Migrateduser

Just as an FYI, there is nothing called a 'Job Variable' inside of the workflow modeller. However, there are 'task', 'global', 'workflow', 'VAVariables' . We may be talking symantics here which is neither our fault.

I have found very little if 'no' information at all on how this environment operates and how to use and assign variables. I wonder if possibly Interwoven themselves can provide some insight or some documentation as this is the only programming environment I have ever worked in that has been so hard to come by very basic operating principles.

DevIntervowen

Hi Mikey,

Sorry for confusion...

Here "Job-Variable" I mean is workflow-variable. If you look into WFM, you will find "variable" at workflow level under "Job Variable" section.

Moreover, I can able to change Global variable using java code by calling it in preprocessor command. It works fine for me and changes Global variable value.

In Java, I achieved through following steps

1)Create an Global Configurable Variable (name it as "GVVar1") in WFM
2) Create an JobVariable [say name "JVVar1"] and assign it to "GVVar1" created.
3) Then change variable using
workflow.updateVariable("GVVar1","NEW_VALUE"); [Here workflow is object of WFMWorkflow]

Please note that once this code is executed in preprocessor code, in instantiation code, you will find value of global variable [GVVar1] has been set to "false"

It will change both variable JVVar1 as well as GVVar1 variable

I didnt tried it in perl but I think instead of updateVariable API, it may be something like
$workflow->SetVariable("GVVar1", "NEW_VALUE");

Data Sample.xlsx

auli

Hi,

Has anyone got this problem resolved? I am using WFM 1010 and still facing the issue. Not able to get or set Global variables from perl script though I can get and set Workflow Variables but in script expression of conditional links, only Global Variables can be used Smiley Sad

I have tried the suggestions mentioned in this post, but no luck.

Retesh - Can you please tell what is the workaround that you have opted for, probably that can help Smiley Happy

auli

Any poinetrs? This is a bit urgent.

Thanks in advance.

scorpian

I am having the same problem on wfm 1.0.1.0 .Please share code if ur able to set the global variable and access that on conditional links Smiley Happy

Brittany

Hi does anyone have any additional experience on getting this to work. I've tried using URL tasks as well as Post Processor Tasks and haven't gotten either to work.

My issue is that during instantiation the user selects from a multi select a number of options. I need to get those options and set a global variable for each of those options. As i mentioned before i tried some of the suggestions of the form.

1) Create a global variable : GV1
2) Create a job variable : JV1
3) Make JV1 = GV1
4) Use java code to change the value of JV1, which should in turn change the value of GV1.

the last step does not work for me. I successfully change the value of JV1 but not the value of GV1. Can anyone help? Did i misunderstand the suggestion?

Crsb

you can change the value of global variables anytime from an external task, but you can only use the update value from another external task.
Conditional link value is set as soon as the job specifications are compiled, so once the job starts, you can not update the value of the conditional links.
but you should be able to set conditional link value from the instantiation form.
this is how you do it:
1) Create a global variable : GV1
2) Create a job variable : JV1
3) Make JV1 = GV1
4) Set conditional link value to some script to evaluate GV1 and return false or true.
5) create an item in the instantiation form named GV1
6) set the value of GV1 item either by using input or using item.setValue().

when the job starts, the conditional link will have the value true or false based on what the script returns using GV1. that will be the value of the conditional link for the rest of the job's lifetime.

if you need a dynamic OR gateway, consider creating an external task called "Gateway Task" where you can check the value of job variables and choose the transition you want.

Adam Stoller

What's your time frame for implementation?
If you need it fast - I'd suggest turning on debug mode for the WFM - generating the job specification file - take that and convert it into a WFT - and then do what you want in Perl in the WFT.

I'm not saying you cannot do what you want in WFM - just that (apparently) it is non-trivial, whereas it's pretty trivial in WFT....

Brittany

you can change the value of global variables anytime from an external task, but you can only use the update value from another external task.
Conditional link value is set as soon as the job specifications are compiled, so once the job starts, you can not update the value of the conditional links.
but you should be able to set conditional link value from the instantiation form.
this is how you do it:
1) Create a global variable : GV1
2) Create a job variable : JV1
3) Make JV1 = GV1
4) Set conditional link value to some script to evaluate GV1 and return false or true.
5) create an item in the instantiation form named GV1
6) set the value of GV1 item either by using input or using item.setValue().

when the job starts, the conditional link will have the value true or false based on what the script returns using GV1. that will be the value of the conditional link for the rest of the job's lifetime.

if you need a dynamic OR gateway, consider creating an external task called "Gateway Task" where you can check the value of job variables and choose the transition you want.

So this is basically what I currently have where each of the global variables are radio buttons in the instantiation form and the conditional links are looking at those variables. What i want to move to is instead of having a radio button for each of these global variables is to have 1 multi select and then getting the values that are selected and setting each of those values a global variable. So I was trying to use a post processor to set those global variables before the job spec is created.
But the issue is when I
1) Create a global variable : GV1
2) Create a job variable : JV1
3) Make JV1 = GV1
and then change JV1, its not changing GV1 and thereby not setting the conditional links properly.

So are you saying that instead of setting the conditional link to equal GV1, i use a script to determine the value of GV1 and use an external task to change the value of GV1? I was under the impression that you can't change the values of global variables once a workflow has started.