Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Dynamic Workflow
kaalraa
Hi,
I am using a IPL file to create a dynamic workflow using WFconstructor.... but at last when i want to call back its stucked up. Also for info this IPL is also called from a static workflow itself. Thats the reason i need a callback to move on to next task in the static workflow.
$wfFile = get_job_spec();
my $wf = $system->CreateWorkflow($wfFile); ...... using WFsystem object
$wf->Invoke();
$task->CallBack(0, "Dynamic Workflow initialized succesfully");
If anyone can... please help me out
- AKs.... The Shadow
Find more posts tagged with
Comments
nipper
You are not providing nearly enough information here
Besides the standard, OS, TS rev etc
Has this ever worked ?
Is there any debug information or errors being generated ?
Have you dumped the XML to a file & confirmed that it is valid ?
That being said, I hope you have some time to work on this (likely alone). I spent the last 3 weeks
debugging an IPL generated workflow. It is difficult to say the least and it is unlikely that a
great deal of help can come from the forum unless you have very specific questions.
good luck
Andty
kaalraa
Hi Andy,
Thanks for replying so soon
Has this ever worked ?
No.. its the first time i am invoking the same.
Is there any debug information or errors being generated ?
Yeah.. i am making a log of the same .. when i call invoke method... it stucks up. Whereas the dynamic workflow created is working fine. but my problem is to get back to my static workflow next task.
Have you dumped the XML to a file & confirmed that it is valid ?
Yeah.. dumped correctly.. and also checked the same using IsVaild() method.
I think... now you understand the problem i am facing. Also FYI i am using TS 6
- AKs.... The Shadow
Adam Stoller
You're saying that the dynamic/sub-workflow is working fine - right? and that the only problem is that the script from which the dynamic workflow is invoked does not seem to be properly calling back to the workflow engine to transition the static/parent workflow - right?
Are you sure the $task object is valid and correct with respect to being the correct task associated with the parent workflow?
The code you showed ($task->CallBack(...)
looks correct in and of itself - but without knowing the rest of the context of the script in which that line exists - it's kind of hard to provide any suggestions for fixes.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
kaalraa
Hi Fish,
I know ... understanding the situation with knowing all the facts are really horrible in Interwoven. I try to make you understand again....
There is a workflow.. (launcher workflow) which has 3 tasks; a cgitask which takes input from the user and dumps the data in form of XML - next is the externaltask which reads out the XML and creates / invokes the dynamic workflow and third is the EndTask for launcherworkflow.
The workflow created by the second task is very much working and properly invoked BUT the problem lies after that. when the workflow is invoked.. then it should callback to the 3rd task of the launcher workflow.
Also you have written is $task object is Valid.... can u provide some info as how to check the same.
- AKs.... The Shadow
Adam Stoller
Okay - prett much as I thought: [cgitask]->[externaltask]->[endtask]
Unclear if you really need the externaltask, as the same code could possibly be included in the cgitask script code - but that's probably irrelevant.
I suggest you read the perldoc for TeamSite::WFtask and TeamSite::WFworkflow - you will see that both include an IsValid() method which can be used to determine the validity of the particular object - in general terms.
However - it would be useful, for debugging purposes, to verify the name, type, and/or some other defining characteristic of the task that $task refers to - in order to remove doubt that the problem is with that object as opposed to its calling of the CallBack() method [again, read the perldocs to figure out how to retrieve the information and add debugging print statements, or Log::Log4perl statements to capture the information for debugging purposes]
The other thing to do is verify that the CallBack is actually being made - again, debugging statements in your code will help determine this.
Hopefully the above is sufficient to help you on the road to debugging your issue
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
kaalraa
Thanks Fish.... i have just manipulated and topple up some commands .. and it work. Its just order of some commands.... with in the IPL file.
Thanks again... to all who make out time for providing me the help.
- AKs.... The Shadow