Workflow - Using custom variable in custom task java code

Using Teamsite 7.4

We are trying to allow users to enter text on the custom instantiation screen which can then be included in an custom email task that we have coded.

In the workflow properties I added a job variable and set it as CONFIGURABLE

Name, ID and label are all "AttachBrief"

It is not hidden and not read-only

In custom_instantiation allow this to be edited on screen

item pathid="AttachBrief" name="AttachBrief">

<label>AttachBrief</label>

<description>Please add brief location if known</description>

</item>

Workflow user is able to enter a value into instantiation screen.

In custom workflow java added the code

currentTask.getWorkflow().getVariable("AttachBrief");

but it never has the value which the user enters.

Are these configurable variables only for values which can be set prior to the workflow being invoked?

TIA.

Find more posts tagged with

Comments

Adam Stoller

The easiest way to see what's happening is to enable debug mode for the WFM, fill out the form, and then look at the resultant job specification that is generated by the instantiator.

Based on your initial description of what you did - I believe it should work; but I'm less clear on where / how you are trying to access that information later. Perhaps you could elaborate a bit more in that regard?

SL_CM

Thanks for your reply.

I put the WFM into debug and I can see that the final job spec includes the info I need in the first section

within this workflow I have a pre-exisiting external (custom) task invokedwhich extends

MailNotificationTask

within this custom task I am trying to get the value of AttachBrief using the code

CSWorkflow workflow = client.getWorkflow(currentTask.getWorkflowId(),true);

String workflowBrief = workflow.getVariable("AttachBrief");

but the value is null.

Incidentally in the final job spec on the custom task the variable is not set - how can I access these workflow level variables rather than task specific ones?

Adam Stoller

SL_CM wrote:
Hi
Thanks for your reply.
I put the WFM into debug and I can see that the final job spec includes the info I need in the first section
<workflow owner="tr456" description="job desc" name="Publish to Runtime" creator="tr456">
<variables>
...
<variable key="AttachBrief" value="foo"/>
</variables>

within this workflow I have a pre-exisiting external (custom) task invokedwhich extends
MailNotificationTask

within this custom task I am trying to get the value of AttachBrief using the code

CSWorkflow workflow = client.getWorkflow(currentTask.getWorkflowId(),true);
String workflowBrief = workflow.getVariable("AttachBrief");

but the value is null.

Incidentally in the final job spec on the custom task the variable is not set - how can I access these workflow level variables rather than task specific ones?

Try adding some debugging to make sure that the currentTask.getWorkflowId() is returning the correct value (I don't see how it could be, but since that's how you're getting the CSWorkflow object and the code to get the variable value looks correct ....)

I guess I should add - are you sure you have a valid CSClient object?

I don't understand the last question. You are setting a job variable, not a task variable - so therefore this variable won't be set at the task level.

Garth McMillan

Sorry, disregard this. On a subquent read, it looks like you did set it up correctly. Just make sure you have both the Global Variable and Job Variable defined in the workflow model.

I think your problem is that the workflow instantiation screen creates "Global Variables" not "Job Variables". From within a workflow task via CSSDK you can only access "Job Variables".

What you need to do is map the relevant job variable to the global variable using Workflow Modeller.

For example, to create a new Job Variable called "AttachBrief" mapped to the Global Variable (Names can be the same or different, but you need to use the Job Variable name, when accessing via {task}.getWorkflow().getVariable("AttachBrief")):

Name: AttachBrief

Value: CONFIGURABLE(AttachBrief)

I find this annoying, but the reason is that the "global" values that are sent to the workflow from the instantiation screen only to initially set up the workflow model. They cannot be changed, whereas job variables can.

-----------------------------

Alternatively you can create a task variable via workflow modeller that is mapped to the global variable (same way as for job variable) and access it that way - depends on what you want to do.