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

CGI Task failing in dispatching to method: completeTask and spins always

Anil Kumar

Hi Folks,

I've replaced a OR gate with 3 transistions(tr) to a CGI Task with 3 tr.

And CGI Task is always showing process status and spins. however when I refresh the job it has moved to next task.

My issue is once it is transistioned to next task, it has to close the processing window which is not happening.

Any clues, if more info is required ask me,

WFM7.3.1 | CSSDK

Regards,

Aneel

Find more posts tagged with

Comments

Rick Poulin

You'd have to provide sample code for your CGI task, because it could be doing just about anything.

It sounds as though your code correctly triggered the callback in workflow, but the UI didn't correctly handle what came afterwards. Depending on how you built it, you might have a JS exception.

Anil Kumar

here is the sample code added.

Yes I got JS exception, when I view it trhough Firebug.

Rick Poulin

If you can see the exception in Firebug, can you not trace it yourself? If not, provide the details of the exception, the line number, and your JSP (the Java class is kinda useless in this case).

Anil Kumar

in Errors its showing urlNode is Null -- WebTask.do(line:274)

looks like xmlDoc is not getting Url. I'm debugging since 4 hours, please help.

The Javascript used in my JSP and error XML response have been attached.

Does my JAVA file should have execute method overrided? or the method what I mentioned in my JS of JSP "updateABCExecute" has definition in my JAVA file would suffice.

note on typo: updateABCExecute in JS methodName is equivalent to updateHasPages methodName in JAVA

Rick Poulin

You should most definitely NOT override the execute() method.

If you always want to close the window, then your completeTaskHandler is unnecessarily complex and the fact that urlNode is null is irrelevant. Try this:

function completeTaskHandler(xmlDoc, text) {
  window.close();
}

Anil Kumar

If I simply close the window, the next task is CGI task, will it continue to show the processing message of next CGI task?

I'm trying this option and let you update. thanks

Rick Poulin

No it won't. Your very first post in this thread asked about closing the processing window. That's not the same at all.

If you want it to proceed with the next task, then you need to figure out why the urlNode is null. Turn on debug logging for your class and see what comes out. Based on your description, I'm guessing that you don't have a transition called taskName + " Success". What you probably want in this case, is to override the completeTask method in your class (or better yet, call it something else entirely to avoid confusion) so that it picks one of the three transitions and then returns the appropriate result. You can look at the implementation of AbstractAjaxWebTask#completeTask() to understand what yours should be doing.

Anil Kumar

Thanks for Info.

Even in the logs by default it is looking for TaskName+ " Success" transition, which I don't have in my Workflow. I wonder if the program doesn't have a valid callback(chooseTransition), the job should stall; developer will have correct his code. Why it is forcing to have a tr-link name as TaskName+ " Success"

Anyhow, I'm trying out the option by adding Success transition.

Anil Kumar

No Luck,.

I've debug further and found that task became inactive and thrown RuntimeException("Task " + taskId + " is invalid or inactive."); and so not able to createBaseResponseDocument

CSWebTaskAction#execute()#

Do I need to reduce the delay time(window.setTimeout) to show processing Message or put some(3secs) wait time in my Java class sothat by that time it will createBaseResponseDocument, before the task becomes inactive.

I'm lost. I'll post some finding tomorrow.

Rick Poulin

To be honest, it sounds like you're a little unclear about how this code works, or intended to work. It looks for a transition called $taskName+" Success" because that's what the parent class of your implementation does. If you got a "task is inactive" message, it's probably because now you're trying to call both completeTask() and a new task completion handler. Timeouts are not a solution at all here.

There's no training or docs to explain how these things work. All I can say is rather than trying a bunch of different things, take some time to look at your JS code and understand the flow of what's happening. Or alternatively, stop subclassing code you don't fully understand and write your CGI handler from scratch.

Anil Kumar

Looks like we should not use chooseTransition for CGI tasks in JAVA code, these transitions should take care in JSP, probably through embedded javascript.

I've removed chooseTransition code from JAVA and then it gives proper responseDocument (and redirects to taskName +" Success" transition by default), I'm going to add transitionLinkName to this doc and set in ajaxContext. which I'll retrive in JS and will be using a JS function getImmediateTransitionUrl() available in ResolveErrorWebTask.jsp

I'll post more updates on this, Please correct me incase I'm doing something outside.

Regards,

Aneel

Rick Poulin

I don't know if there's necessarily anything useful to copy from ResolveErrorTask (be careful about any assumptions/restrictions the copied code might make), but otherwise that sounds right.

Anil Kumar

I was successful somehow. Here's the story and yet to add scenarios for error/ exceptional cases.

attached is the Java and JS in JSP code.

Suggest me if any fallbacks/ exceptions.

Thanks rpoulin for motivation for enabling me to do some more analysis on JS code and tweaking it.

Regards,

Aneel

Rick Poulin

Glad to hear you figured it out. Please mark one or more of these posts as the "solution" to effectively close the thread.

Minor notes about your code:

* You should never use the Impl classes. Instead of CSCGITaskImpl, use CSCGITask (the interface). It doesn't change your code, but it keeps you on the supported path in case they change the implementation down the road.

* Your "don't use chooseTransition()" comment isn't going to help you remember the reasoning 3 months from now. While it's still fresh in your mind, put yourself a note here as to how the transitioning actually works so you can remember and help other developers that might maintain your code after you're gone.