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

Submittask sumits everything

dazzlad

All, I have a simple workflow (see attached). My problem is that the submittask submits all files that are modified in the workarea rather than just those specified by the files element in my start task.

Can anyone suggest why this may be happening.
The workflow is being instantiated via a WFT on TeamSite 6.5 SP3 on Solaris.

Many Thanks!

Find more posts tagged with

Comments

jagadesh

Submit task will submit the files to Staging if any file has attached to the workflow means. If no file has selected on the submit event means ie workflow instantiation from submit click, it will take all the modified files from Workarea.

Just select one file then intiate the submit event kind of workflow.
Through new job it wont instantiate the workflow if no file has selected

Then do what ever logic in your custom script

dazzlad

Thanks but your answer doesn't consider my question or provide any useful information towards a solution.

You are just stating how a submit task *should* behave which I already know.

In the workflow spec which I attached to my original post you'll see that my job does have a single file attached yet everything is still being submitted.

TOCWithPageNumbers.rptdesign

Adam Stoller

All, I have a simple workflow (see attached). My problem is that the submittask submits all files that are modified in the workarea rather than just those specified by the files element in my start task.

Can anyone suggest why this may be happening.
The workflow is being instantiated via a WFT on TeamSite 6.5 SP3 on Solaris.

Many Thanks!

Just to make sure:

...
      <file path='path/to/file/which/attached/****_yyy_zzz_form_EN.pdf' comment='Added by Workflow'/>
...

The "path/to/file/..." is an area-relative path - yes?
Was it created automatically via the WFT or did you manually hard-code it?
(I can read the comment there, but I just want to make sure it's accurate)

Also:

...
    <command v="/web/soft/iw-home/iw-perl/bin/iwperl /web/sites/****/xxxxxxxx/****_documents/set_edition_variable.ipl" />
...
    <command v="/web/soft/iw-home/iw-perl/bin/iwperl /web/sites/****/xxxxxxxx/****_documents/clean_folders.ipl" />
...
    <command v="/web/soft/iw-home/iw-perl/bin/iwperl /web/sites/****/xxxxxxxx/****_documents/validate_metadata.ipl" />
...

None of the above scripts add or remove files from the job - right?

(note: since you're on Unix, as long as the scripts have the correct #! line and are executable, you don't need to preface them with the iwperl engine path in the command element)

Other than the above, I don't see anything to suggest a cause for the behavior you say you're seeing - the only other explanation I could arrive at is that you're looking at the wrong workflow template and that it's some other template that is causing the behavior you're seeing.

dazzlad

Thanks for the response!

The "path/to/file/..." is an area-relative path - yes?
Was it created automatically via the WFT or did you manually hard-code it?

Path to the file is area relative.
The files tag is generated during WFT instaniation, not manually.

None of the above scripts add or remove files from the job - right?

No, I've removed the callbacks from validate_metadata.ipl and ensured that there is only 1 file attached to the workflow prior to the submit task.

Other than the above, I don't see anything to suggest a cause for the behavior you say you're seeing - the only other explanation I could arrive at is that you're looking at the wrong workflow template and that it's some other template that is causing the behavior you're seeing.

I just verified again, I'm 100% sure I'm looking at the correct WFT, besides the workflow spec once instantiated shows only a single file attached!

I'm puzzled!

Report.docx

dazzlad

OK, I was being an idiot.

My fault!

My iwpublish command was publishing based on a workarea rather than staging.....

doh