Custom job instantiation variables

All,

I've poured over the forums looking for what is probably an obvious solution. Through workflow modeler, we have created two global variables of variable type CONFIGURABLE:

ID1239745140095
ID1239745147751

We used the iwmodeldct to generate the custom_instantiation.cfg file. It generated a file with a lot of FormAPI javascript along with the "Config" container:

[html]

ITEST
ITEST CUSTOM

FTEST
FTEST CUSTOM2

[/html]

I've verified that IDs in the default_config.xml file for this workflow matches the custom_instantiation.cfg file:

[html]

ITEST
ITEST
$IW_TIME
false
false

Workflow Properties1
false
Global Variables
ModelProperties
true
text

FTEST
FTEST
$IW_AREAOWNER
false
false

Workflow Properties1
false
Global Variables
ModelProperties
true
text

[/html]

We can successfully display the custom fields, however, I can't figure out how to reference them within a workflow task using the CSSDK. I'd like use task.getWorkflow().getVariable(String) to retrieve these values.

When viewing the "expanded workflow model" via debug, the fields show up as a ModelProperties element:

[html]
value1|value2
[/html]

("value1" and "value2" entered in the job instantiation form).

These values don't show up anywhere in the final job specification. My questions are:

1) What am I doing wrong?
2) How do I populate these values as variables of the workflow?

Thanks for your help.

Configuration details: Teamsite 6.7.2 using CSSDK

Find more posts tagged with

Comments

Faizi

There are lots of thread related to access of global variable in workflow. But there is no direct solution. Through ipl it is shown achieved (by threads). But there is no any such point for WFM (java). While going through CSSDK docs and Workflow API docs (you can get it from httpd's lib directory as a jar file) there is no such method to get Global variable or configurable variable of a workflow. But there are various method of get variable for a task and other.
You can ask to support for quick and best solution.

zed0901

Based on Faizi's recommendation, I posted this question to support. Configurable variables aren't available after the workflow is instantiated. In my case, I needed to add two additional job-scoped variables which reference the configurable variable values: Job variable Type Source ITEST SCRIPT “$IW_CV(ID1239745140095)” FTEST SCRIPT “$IW_CV(ID1239745147751)”

Thanks all!

Jcse

Based on Faizi's recommendation, I posted this question to support. Configurable variables aren't available after the workflow is instantiated. In my case, I needed to add two additional job-scoped variables which reference the configurable variable values:
Job variable Type Source
ITEST SCRIPT “$IW_CV(ID1239745140095)”
FTEST SCRIPT “$IW_CV(ID1239745147751)”
Thanks all!

Kindly explain a little more ?

Faizi

Based on Faizi's recommendation, I posted this question to support. Configurable variables aren't available after the workflow is instantiated. In my case, I needed to add two additional job-scoped variables which reference the configurable variable values:
Job variable Type Source
ITEST SCRIPT “$IW_CV(ID1239745140095)”
FTEST SCRIPT “$IW_CV(ID1239745147751)”
Thanks all!

Is there something missing in your post? Or it is fine. Because there is too much gap between para.
Anyway if you will get solution then share on forum. It would be helpful to others.

zed0901

Here's a summary of what I did:

1) Add a custom variable to the workflow properties via the workflow modeler.

Name: CUSTOMVAR
Value: (Select CONFIGURABLE)

2) Save and publish workflow.

3) Generate custom_instantiation.cfg using iwmodeldct CLT. Make sure pathid and name in this file matches the id in the file default_config.xml.

4) Instantiate this workflow in debug mode and you will find a job specification similar to:

[html]

<-----------

[/html]

5) Access this CUSTOMVAR variable from a task using CSSDK via:



//task is an instance variable

task.getWorkflow().getVariable("CUSTOMVAR");

I've attached a zipfile containing a sample workflow (.ipm and corresponding custom_instantiation.cfg and default_config.xml) which demonstrates everything above, except for accessing the property via CSSDK.

Thanks for all of your feedback.

Jimbean

I dl'd your example and tried it . I set the description of the dummy task to
a script variable = task.getWorkflow().getVariable("CUSTOMVAR"); to see if the variable indeed has value after instantiation.
It did not, it showed "undefined" in the workflow list.
I then added a cgi task "show_env.cgi" and the variable was nowhere to be seen.

What am i missing? Anyone else get this example to work?

Jimbean

... I see.