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

Passing a variable to WFT

summergs

Hello,

I am trying to pass a variable, via SMTP, into a workflow. Does anyone know how to get the value of the variable into the workflow? project_number is the value I am trying to pass....
Snippet:
http://server/iw/webdesk/assign?iw_template_file=default/test_assign.wft&project_number=123&iw_template_name=Project_Contributor_Assignment&vpath=/default/main/Test/WORKAREA/workarea/templatedata/Templates/bubba/datacapture.cfg

I thought that $projectNumber=__VALUE__('project_number'); would do it but it doesnt.

Thanks in advance!

Find more posts tagged with

Comments

Adam Stoller

I'm not sure if this will work, but you could try using:

...&iw_setwfarg_project_number=123&...

This *might* set the form variable -- and if it does, it might also automatically set a job variable (without the 'iw_setwfarg_' prefix.

However - even if this does work - it probably isn't officially supported and could change at any time without notice.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

summergs

Thanks Fish!
How would I acquire the value of this variable in the WFT?

Adam Stoller

IFFF it works (and it's a BIG IF) - then it would either be __VALUE__('iw_setwfarg_project_number') or __VALUE__('project_number') [probably the former]

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

summergs

I was afraid you were going to say that...boohoohooo (doesnt work)
Is there no was possible to pass a variable into the WFT using the http string?

Dwayne

Unfortunately, the list of available parameters to give to the "assign" command doesn't include the ability to "preset" the various TAG CGI variables. I believe that there's a "hidden" form that gets processed between the URL that you give and the WFT instantiation form that the user sees. So if Interwoven hasn't made an explicit 'tunnel" for that data (and it appears that they haven't) then it won't get through.

I'll let the idea rumble around in my brain, to see if anything pops up, but don't hold your breath.

Current project: TS 5.5.2/6.1 W2K

summergs

ugg... Thanks for the input (and anyone can think of anything it would be awesome).

Adam Stoller

If you're creating the URL string - you could tack on the project number to the filename and then in the wft, include special code to process the iw_file list and strip off the project number at that point....

It's a hack/work-around but it probably has a reasonable chance of working...

Something like:

http://.../assign?vpath=/some/filename#123&...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

summergs

Interesting....I will try that. Thanks!

Dwayne

Another idea: Instead of tacking on data to the end of the vpath, which leaves me feeling a bit uneasy, why not build it into the name of the WFT? So instead of using this url:


http://server/iw/webdesk/assign?iw_template_file=default/test_assign.wft&project_number=123&iw_template_name=Project_Contributor_Assignment&vpath=/default/main/Test/WORKAREA/workarea/templatedata/Templates/bubba/datacapture.cfg

use this:


http://server/iw/webdesk/assign?iw_template_file=default/test_assign.wft&iw_template_name=Project_Contributor_Assignment(123)&vpath=/default/main/Test/WORKAREA/workarea/templatedata/Templates/bubba/datacapture.cfg

You can get that name in the WFT file using __VALUE__('iw_template_name'), and then extract the project number with a regex

--

Current project: TS 5.5.2/6.1 W2K

Edited by Dwayne on 08/30/04 09:34 AM (server time).

Adam Stoller

That sounds good - I like it better than putting it on the file too - unfortunately the documentation in the manuals on the URI's seems somewhat limited and I didn't realize you could pass the path and *name* of the workflow within the URI...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

summergs

Thanks for the additional idea. I will try that too!

Dwayne

The downside of this approach, of course, is that this "hidden" info will be visible to the user on the data collection page.

In this particular case, that might actually be a good thing, but if the data being passed in were more "esoteric," it might confuse the users.

--

Current project: TS 5.5.2/6.1 W2K

summergs

You are correct when saying this variable is not hidden, but in this case it is acceptable. This solution works great for what I need!!
Many Thanks!

Dwayne

I'm glad it worked out for you.

Sounds like fodder for a feature request, though: the ability to set the default value for TAG_info fields using the CCI URLs

--

Current project: TS 5.5.2/6.1 W2K

summergs

I TOTALLY agree

Migrateduser

I created an enhancement request for you - 55811.
regards,

lissa

summergs

Thanks!!