Submit to stageing

I have created a simple custom workflow using Workflow builder, it works fine but it is not submitting files to staging. I am using <submittask> tag. Do I need to add any custom code to push the files to stage?

Find more posts tagged with

Comments

Migrateduser

What specifically do you mean that it is not pushing the files to staging? Is it stuck in a conflict resolution state? Does the submittask fail? Does the workflow contune on to the next task after the submittask? What does your ToDo list look like after the submittask executes? Please supply as much detail as possible.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

This is exactly what the submittask is for; submitting files to staging.

When you ran you workflow, did you have any file attached to the job? Did the job complete? (You can check the list of all jobs from WebDesk Pro.) If there were any problems with the submittask (at runtime) -- like a file version conflict -- then the task will still be active and will have an error message that indicates the problem.

Brinko Kobrin
Interwoven Staff Engineer

akalve

Submit task is the last task in the workflow. Job does get finished with success but without pushing files to staging. Job gets cleared from the in box. ToDo list is empty after the workflow is completed. It does not have any conflict with other.

Migrateduser

Are you certain the job finishes with success? Did you try pulling down the View menu and selecting All Jobs? I suspect that your submittask is owned by someone other than the person executing the job, and the Resolve Conflicts state is sitting there in someone else's queue.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

I would suggest that you look through your iwevents.log to see if the sequence of activities is what you expected. This is easier if you could "grep" for those lines that contain the task ID from your test (expressed as a hex number). You should also check iwtrace.log to see if any errors or warning were reported.

If that doesn't work, I would suggest that you post your WFT for review (along with your platform and version info), or contact customer support.

I know that it is of little consolation, but it "should work" (this is a frequently used feature). You are on the right trail.

Brinko Kobrin
Interwoven Staff Engineer

Adam Stoller

Also - just to be sure - are there any modified files associate with the workflow? It's been known to happen in the past that someone tests a workflow like this by preselecting a bunch of files in their workarea without actually modifying them. If there are no changed files - the submittask is a no-op.

As suggested, attaching the wft (or better, the instantiated job description file) might be helpful as well as verifying any entries in iwtrace.log and/or iwjoberrors.log

--fish
(Interwoven, Curriculum Development)