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

WF stops on Validatings files (Temasite 6.7.2)

Hokumet

I am using a workflow to submit dcr......pages to mij production server.
When I submit I can see the workflow status from the Workflow administration tab.

But some times the task stops and I get the following message:
Job Description: Publishes content to one or more target nodes, optionally including a review / revision loop.
Last Comment: Successfully completed task: Attach Dependencies ..........
Task Description: Performs validation on files attached to this job.

I can click the "Start input task" and the following Next Next buttons then the problem is solved. But normally this work, only sometimes I need to login as administrator and click the "Start input task". Can someone please help?

In the servlet_out.log I see at that time:
[http-8080-Processor11] WARN com.interwoven.ui.datacapture.core.dcxp.DTDNodeOrderingStrategy () - Error reading DTD http://localhost/iw-cc/datacapture6.0.dtd. Message: http://localhost/iw-cc/datacapture6.0.dtd
development,production

Find more posts tagged with

Comments

nipper

Workflows are custom code.

For anyone to help we need to know about the custom code. Who wrote the WF ? What step is it running ? Is that step Java or Perl ? You would need ot debug the code or post the code for help.

Validating files is not a OOTB step provided by IWOV, so this is something that someone wrote on your site.

Adam Stoller

[...]
In the servlet_out.log I see at that time:
[http-8080-Processor11] WARN com.interwoven.ui.datacapture.core.dcxp.DTDNodeOrderingStrategy () - Error reading DTD http://localhost/iw-cc/datacapture6.0.dtd. Message: http://localhost/iw-cc/datacapture6.0.dtd
development,production

You can ignore that annoying message, or, as I've done on several implementations, copy the IWHOME/local/config/datacapture6.0.dtd to the proper location inside IWHOME/httpd/webapps/content_center/ and it should go away.

Hokumet

Thanks for your answers nipper and ghoti.
@ghoti. I will copy the file to the proper location.

@nipper. I didn't know that it was custom code. Until now programming of WF and other stuff have been done by an external company, and I am new to teamsite.

I made a little screen shot of the workflow. I hope it helps a bit.
Otherwise I would like to know where I can find this custom code.

I also want to mention again that this problems doesn't occur each time.

Thanks again folks for your help and patience.

Adam Stoller

If I'm reading the diagram correctly, you have a whole bunch of CGI Tasks chained together - why they're all CGI Tasks is beyond me - most of them sound like they should be either External Tasks or URL Tasks (which are essentially the same thing), but CGI Tasks that get transitioned to require special coding to get them to work "immediately" upon being activated, otherwise you have to go the Task Details screen and click on the "Start Input Task" button in order to get them to run.

This is covered in the manuals (at least the Workflow Developer's Guide - as opposed to the Workflow Modeler User's Guide) and in numerous posts here on DevNet (try searching, you might find them) - and should be covered in any TeamSite Workflow Training course, which you should go through if you're going to be doing TeamSite Workflow development and can't figure it out from the manuals and existing DevNet forum postings.

In short - I don't believe your workflow is "failing", I think it was questionably written and you're running into a particular case that doesn't work the way whoever wrote it imagined it would, and thus it requires manual interaction to keep it going.

Hokumet

How can we find out where it goes wrong?
Can you tell us how to debug this workflow anf which log file we need to search for errors?
Also how can we set the loglevel of workflow debugging to "DEBUG"?

thanks

nipper

You need to see what Validate Files is running. That is not in the screenshot. If you click on the variables you can see what variables are there and hopefully one will have the object being executed. It is likely custom Java (possibly Perl).

Hokumet

Hi ...
The object being called is workflow.task.ValidationTask.
I searched in the spring xml file, I saw that this beanID correspondents to the java class(See attachment). I have decompiled the class file.

And I see lots of thing in it. Can you explain me how/where I can turn on debugging to get the error messages that will be throwed according to the java class.

Thanks again

Adam Stoller

What happened to the person / company that wrote this code in the first place? They are the ones you should be talking to right now.

Hokumet

I cant contact them at this moment. Smiley Sad

I thought maybe I can find it out, if I knew where the log files are and if how to set the DEBUG level.

Adam Stoller

I cant contact them at this moment.

I thought maybe I can find it out, if I knew where the log files are and if how to set the DEBUG level.

Unfortunately, when you're dealing with custom code - it's you who is stuck trying to figure out where the log information (if any) is going (if anywhere) - sometimes you just have to modify the scripts to add your own debugging output information and take it from there -- because we don't have your code or your environment, we can't really help you on that regard.

As for getting a CGI Task to start immediately, the requirements for that are covered in the Workflow Developer's Guide, and then it again comes down to custom code - where you have to do the debugging in your environment.

Ideally, the person who wrote the workflow in the first place would have also written a good, detailed, design & implementation document. If they didn't - that's a reflection of their skills and professionalism as a consultant / developer. If such is the case, you should take the time now, while trying to understand the code, to create such documentation - as much for yourself as for the next poor soul who comes after you and has to maintain the same workflow.

nipper

Such well documented code. :-)

Sometime these will get dumped into the servlet_out.log

So you can look there. Otherwise someone has a long task ahead of them.

Hokumet

I can find only that line about dtd in the servlet_out.log file.
I cant find anything else.

Could it be that I need to set something to debug level so I have more logging in some file ?