WFM: accessing variables

TS: 7.1
WFM: 7.1.0.0 (Build 1264)

I'm fairly new to WFM and still figuring things out, so sorry if this seems a simplistic question.

I have a worfklow that needs to perform 2 deployments - one to a Pre-Prod environment and then one to Prod. I have a configurable deployment scheme where I pass the "level" as a substitution string. I want to use a task variable to act as a flag for the JavaScript in the OD Variable script.

When setting variables I appear to have these options:

Configurable - accessible through $IW_CV
Datasource - accessible through $IW_DS
Script - accessible through $IW_SCRIPT
System - $IW_HOME, $IW_PORT, etc.
Hardcoded (not set by any of the above) - how to access?

How can I access the hardcoded variable in my "script" variable below? I have a task variable "deployLevel" hardcoded to "QA" in one task and "Prod" in another.

Code for OD Variable $IW_SCRIPT(level):

 
if ( "$IW_SERVER" == "devserver" ){ 
  level = "Dev";
} 

if ( "$IW_SERVER" == "prodserver" ){
  if ( "????(deployLevel)" == "QA" ){
   level = "PreProd";
  } else {
   level = "Prod";
  }
}

$IW_CV, $IW_DS or $IW_SCRIPT in place of ???? won't work, so what will?

Thanks,
Mark

Find more posts tagged with

Comments

Adam Stoller

I'm not working with WFM right now, but from recollection:

Hope that helps.

dinaish20

I have gone through multiple posts and wfm documentation but haven't found the ans yet.

We are having the same issue as bagman.
We have a global variable "Reviewer Group" set to a teamsite group.
We have Java program which adds a variable called "locale" to the another Job in workflow.

So in wfm - We have a task (say Start Review) to start "sub review workflow" and set teamsite group specified in "Reviewer Group" as owner of the sub workflow.

In the Start Review task we are able to access "Reviewer Group" variable, but want to access this "locale" variable now and based on that send reviewer group information (mainly revieer is going to change based on locale),
but it is not accessible by $IW_CV or any other way. So how to access 'locale' which is a hardcoded variable in this task.
( I am able to access this locale variable in scripts by $job->GetVariables Smiley Wink

We are using 6.7.2 and WFM 1.0.0.1.

Appreciate any help.

Adam Stoller

Take a step back and think about the order of processing.

$IW_CV() variables are variables whose values are configured before / during instantiation - so if you have some program adding job variables to existing workflows (which is what it sounded like from what you wrote) - then there's no way that the value of that additional job variable can be used before / during instantiation, it can only be accessed after instantiation (and after this other program has been run)

Next - when you say you're initiating a "sub workflow" - how are you doing that? With iwmodelc or with a nested WF task or some other method? If I recall, the nested WF task works primarily with job specs (though it is supposed to handle IPM or WFT files too). The manual indicates that the parent task can pass variables to the child task - but you seem to be indicating that the "locale" variable is not associated with the parent task, but being set on the (sub-workflow) child task by some external program - as such, again, you wouldn't be able to do that until the job was instantiated and thus there is no way that you could reference it within the model itself.

Perhaps I'm not understanding what you're saying, but it seems to me that you're putting a cart in front of your horse with your current description.

dinaish20

Thanks for the reply Ghoti.
We are using nested workflow task to invoke that.

Here is the scenario
Start --> CGI Task (decide locale)--> URL Task (start review workflow) --> Nested workflow task

So the URL task is invoking a java program with workflow name, its owner and few other parameters (which are global configurable variables) - please find in screen shot.

So now we want to pass owner to this URL task based on the language selected which was stored in "locale" variable in the previous CGI task.
That variable is job variable and I think should be available to all the tasks in workflow.

So in URL task when I try to access in script variable to set reviewer group , locale doesn't return anything.

if ("TARGET_LOCALES" == "ja-jp")
{

"Translation-Approvers";

}

else

{

"ReviewerGroup";

}

Thanks in advance for any clue.

Sorry for not being clear at first go.

Take a step back and think about the order of processing.

$IW_CV() variables are variables whose values are configured before / during instantiation - so if you have some program adding job variables to existing workflows (which is what it sounded like from what you wrote) - then there's no way that the value of that additional job variable can be used before / during instantiation, it can only be accessed after instantiation (and after this other program has been run)

Next - when you say you're initiating a "sub workflow" - how are you doing that? With iwmodelc or with a nested WF task or some other method? If I recall, the nested WF task works primarily with job specs (though it is supposed to handle IPM or WFT files too). The manual indicates that the parent task can pass variables to the child task - but you seem to be indicating that the "locale" variable is not associated with the parent task, but being set on the (sub-workflow) child task by some external program - as such, again, you wouldn't be able to do that until the job was instantiated and thus there is no way that you could reference it within the model itself.

Perhaps I'm not understanding what you're saying, but it seems to me that you're putting a cart in front of your horse with your current description.

Rick Poulin

So in URL task when I try to access in script variable to set reviewer group , locale doesn't return anything.

That's because TaskVariables!=ModelerVariables.

$IW_CV, $IW_DS and $IW_SCRIPT get evaluated at instantiation time. In other words, when your above script gets evaluated, your 'locale' variable is legitimately undefined. So either decide on your locale in the wf instantiation screen, or rewrite your CGI to resolve the URL task and set the sharedby directly.