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

create a task object in CGI

infoForDj

Hi,

I have written following code snippets to get task information within a CGI:

my ($task_id) = $cgi->{form}{'taskid'}; # taskid is a hidden field within the form.
my ($task) = new TeamSite::WFtask($task_id);

my ($workflow_id) = $task->GetWorkflowId();
my ($job) = new TeamSite::WFworkflow($workflow_id);

my($workflow_area) = $task->GetArea();
$workflow_area =~ s/\\/\//g;

my @iw_files = $task->GetFiles();

However, when I print the values within a log file, I get the following output:

Workflow ID:
Task ID: ARRAY(0x12d4d0)
Area:
Number of files attached:

I am using CGI_lite package.
Please help me debug why the task object is not getting created and why am I getting an object instead of "taskId" as a value for $task_id.

Thanks in advance,
Dhruv

Find more posts tagged with

Comments

JonathonG

I don't recall the exact context in which it can happen, but here's what we use to deal with the fact that task_id is sometimes an array:

# Get the value of the task ID.
my($taskID) = $cgi->{form}{task_id};
# If the parameter has multiple values, just use its first value.
$taskID = $$taskID[0] if (ref($taskID) eq "ARRAY");

Jonathon
Interwoven Developer
Allstate, Inc.

reddyl

TeamSite::CGI_lite is returning a reference to the 'taskid' CGI variable, check if its a array using ref bulit in function.

my($task_id) = $cgi->{form}{'task_id"};
$task_id = $$task_id[0] if(ref $task_id eq "ARRAY");

infoForDj

Hi,

Thanks for the solution.

Dhruv

jbonifaci

Actually, the reason you are getting an array is that task id is passed with 4 separate names:
iw_taskid
taskID
task_id
taskidBecause you are asking for 'taskid', you are getting an array that contains both 'taskid' and 'taskID'. If you use either iw_taskid or task_id, you will only get a single value. I personally always use iw_taskid, as it appears to be more in line with the other variables passed. If you use iw_taskid, instead of taskid, you will always get a single value instead of an array.

~Jeff

Adam Stoller

Jeff - are you sure about that?
I believe that the namespace in a hash / form variables - is case-sensitive not case-insensitive and the reason you get the reference to an array has to do with the way the variables are created while being read from the data into the %form hash - if it sees two variables with the same name, it turns the hash value into a reference to an array instead of a scalar.

I could be wrong though - I haven't really debugged / debunked the code in any detail.

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

jbonifaci

Actually, I think I was smoking some crack. I've been working way too many hours and not getting a lot of sleep. I don't think I've ever run into this issue, so assumed it wasn't a real issue. I was thinking that it was case-insensitive and it was treating both taskid and taskID as the same parameter and therefor creating an array. But I just tested this and I realized I am truly on crack. Thanks for keeping me inline Adam,

.

~Jeff

Migrateduser

Very nice to know that I'm not the only one you accuse of being on crack!

Environments:
(1,2) TS6.5SP1, TS6.5SP2 on W2K3
(3) Vignette V7 Portal on Solaris 9

sample report.rptdesign

jbonifaci

Hmmm, I must have gotten the good stuff from my dealer last time, as I just now checked some cgi tasks I've written and I am checking for an array as well,

. I then checked the manual, and although it doesn't say why there is ever more than one task id, it has similar code to what I am using, what JG posted and what reddy posted in the one example.

So, that leads me to ask, do you happen to know when and why multiple task ids are ever passed? If I knew, I can't seem to remember at the moment.

I think I need to lay off the crack...

~Jeff

Adam Stoller

I believe the coding example in the manual probably came from my tutorial work.

The reason why this happens is usually with regard to a recursive or reiterating CGI such that your scripts posts data back to itself to perform a second pass at processing. I believe that in some (albeit not defined right now) cases TS will actually do this itself.

Basically - CGI_lite (and perhaps even standard CGI) sees something like this: key1=value1
key2=value2a
key2=value2b
key3=value3And transforms it into: $cgi->{form}{key1} = "value1";
$cgi->{form}{key2} = ["value2a", "value2b"];
$cgi->{form}{key3} = "value3";and it doesn't matter if "value2a" and "value2b" are identical or different - as soon as it sees a second value for the same key it turns that key into an array reference.

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