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

Submit Task

MrShake

You guys have been SOOO helpful. I have to thank you all..

Hopefully a quick question...

I'm trying to use the Update task to move some files for me, instead of doing it in an exteral perl script.

Will the Update task move an entire directory structure as long as the root of that structure exists?

As well, is there any error catching for the Update task?

Find more posts tagged with

Comments

ISCBorisB

You guys have been SOOO helpful. I have to thank you all..

Hopefully a quick question...

I'm trying to use the submit task to move some files for me, instead of doing it in an exteral perl script.

Will the submit task move an entire directory structure as long as the root of that structure exists?

As well, is there any error catching for the submit task?

Submit Task does not "move" anything anywhere. It submits contained files to Task's
Areavpath Staging. Perhaps you meant an Update Task?

MrShake

Your Correct, I meant Update Task

nipper

The update task again will move all files in the task only from Staging to the workarea. If there are new folders, then new folders will be created.

There are things that can stop an update (conflicts), I expect they will return an error if the conflict is not overridden.

Adam Stoller

The update task again will move all files in the task only from Staging to the workarea. If there are new folders, then new folders will be created.

There are things that can stop an update (conflicts), I expect they will return an error if the conflict is not overridden.

An Update Task will move files from the srcareavpath to the areavpath associated with that task - the latter must be a workarea - the former can be any area (workarea, staging, or even an edition).

The files are all moved with respect to the area-relative paths from source to target area - you do not get to alter that aspect of the path.

As well, is there any error catching for the Update task?

An Update Task can have either one-or-more basic Default Links - or it can have both Success and Failure Links. I don't recall, if you use just Default Links, whether a failure results in a Resolve Conflicts window or not. If you use Success / Failure links - you are responsible for providing whatever error handling you want.

MrShake

I'm thinking more and more that the update task may not be able to accomplish what I want it to.

Example:

\foo\bar\foobar\2012\files

I want to copy all those files to

\foo\bar\foobar\2013\files

Thats the simplistic situation, its actually a little more complicated than that

\foo\bar\foobar1\2012
\foo\bar\foobar2\2012
\foo\bar\foobar3\2012

copied to

\foo\bar\foobar1\2013
\foo\bar\foobar2\2013
\foo\bar\foobar3\2013

And there are other directories under foobar1/2/3 that I don't want copied.

Adam Stoller

In your situation - no, and Update Task would not work. You could, potentially use an External Task that ran iwupdate or iwcp (or CSSDK equivalent) - or (still in an External Task) use a more traditional copy procedure and then, if need be, use iwextattr (or CSSDK equivalent) to
transfer EAs - or you could use OpenDeploy (with or without EA transfer) ... but no, an Update Task would not work for what you are requesting.

MrShake

Hrm... I hadn't considered using Open Deploy... thats not a bad idea!