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

Problem with UserTask

kaalraa

I am using WFConstructor on TS 6.5 / SP 2 on Solaris 8. In the same i am facing a problem where i have a user task and on which i have to transit to next task using TIMEOUT.

I have a usertask "Wait for Deployment" which have three tasks as successors (A) Deploy Now (B) Reschedule Deployment (C) Notify Missed Deployment. What i have to do is declare a usertask setting its TIMEOUT attribute value as Deploy Now. But when I compute the Job spec file it automatically takes the last defined task in the successorset as its value for TIMEOUT.

If anyone has faced the problem earlier or have any suggestion .... please provide a bit of help.

~ aks

Find more posts tagged with

Comments

jbonifaci

You are likley not defining the timeout transition correctly. If you read the documention, you declare a tasks timeout transition like this:

&link_tasks('TaskBeingTimedOut', 'TaskToTimeoutTo', TIMEOUT);

~Jeff

kaalraa

Jeff,

Thanks for your concern... but it has been done like this only. The problem which i am facing is when i use USERTASK instead of a DUMMYTASK in order to use TIMEOUT transition, then only it gives me this type of error output.

On using of a DUMMYTASK in parellel and defining timeout in that.... gives me exact output as expected.

~ aks

jbonifaci

I use timeouts in usertasks without any problem. Please post the exact &declare_task and &link_tasks function calls for the task you are having problems with. Also post the user task from the job spec and highlight what you are seeing that is wrong.

Thanks,
~Jeff

kaalraa

Jeff,

Following is the code being used

<usertask lock = "f"
name = "Ls_Wait_For_Deploy"
owner = "__TAG__('iw_user');"
start = "f"
immediate = "t"
description = "Ls Wait For Deploy">
<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="ReSchedule Launch">
<succ v="LS_Schedule_Deploy"/>
</successorset>
<successorset description="Finish Job">
<succ v="Ls_End_Task"/>
</successorset>
</successors>
<timeout v="__INSERT__($launchTime);">
<succ v="LS_Prod_OpenDeploy"/>
</timeout>
<activation>
<or>
<pred v = "LS_Notify_Of_Schedule_Deploy"/>
</or>
</activation>
</usertask>

What i expected out of the code is to show 2 buttons at the end of the Usertask (doing so) and when it reaches the value of $launchTime ... it should activate the Deployment to the production (NOT doing).

~ aks

jbonifaci

I thought you said you were using WFConstructor? If that is your code, you are either not using WFConstructor or not using it correctly. What does your actual job spec look like? Is the task not timing out correctly, or is your deployment external task hanging? Give some more details.

~Jeff

kaalraa

I have just provided just like what i am getting out as the job spec file when generated thru WFConstructor. This is because while debugging i moved on to do other changes and forgot to make the copy of the same.

It is not timing out correctly and moreover it is hanging over to this particular task only after the time lapsed. I had also debugged the task using iwgetwfobj and it is giving me proper task expiration time as well as the timout succ time.

I hope the given details are enough to understand the issue.

~ aks

Adam Stoller

Something still doesn't jive though.

If you used WFconstructor to define the WFT - and you're posting the information shown from the instantiated job descirption file - none of those __****__() directives nor $varname directives should be visible - they should already have been expanded.

So - if they're not getting expanded in the job description file - something is definitely wrong with your WFT - and we'd have to see that in order to help debug it for you.

Or am I completely misreading this and you're saying that you're showing the WFT generated from WFconstructor as opposed to the job description file generated during instantiation? Seeing the actual WFconstructor code *and* the instantiated job description file would help - seeing the WFconstructor generated WFT doesn't really help too much.

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

kaalraa

Adam.... i am aware of the fact that i said of using WFConstructor whereas i have provided you the code which is of a static wft file. But at the same point i also expressed my non availablity of the code which is being used due to further changes and development done.

I have specifically written this code out of the box which i was getting when i had generated the Job spec file. In this the problem is it is NOT timing out of the task 'Wait for Deployment'.

I hope this makes sense... or else i apologise to get you confused.

~ aks

jbonifaci

So the problem is, the task is not timing out. This probably means that your timeout value is incorrect. But you have posted nothing to let us trouble shoot this. All we know is that:

<timeout v="__INSERT__($launchTime);">

Which tells nothing. What is actually being output to the job spec for this timeout? Please post the job spec or at least this specific task from the job spec. Also let us know how long from when the task started that you expet the task to time out.

~Jeff

kaalraa

Jeff,

As of now i dont have the code from the Job Spec file. Also to answer you about the time format passed to timeout element is 012520062330. (25th Jan' 06 - 11:30 PM). And the task to be timed out, has been activated at around 10:50 PM.

~ aks

jbonifaci

I'm curious, if you don't have access to the code, why are you trouble shooting this? If what you are outputting is actually getting to the job spec, then it should be working fine. But it obviously isn't. So you're going to need to post the job spec if you want further help.

~Jeff

kaalraa

Its OK Jeff.... but can you tell me as what is wrong in the code which i have given over. This is also not timing out to the Prod Deployment.

~ aks

jbonifaci

As I said above, the only information we have about your timeout is:
<timeout v="__INSERT__($launchTime);">Without actually seeing what is really being outputted, it's hard to say what's wrong. As I said before, I can't really help you further until you post the job spec.

~Jeff

kaalraa

Thanks for all your help and concern

~ aks