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

filelist to submittask

jkm

Hi,

We create filelist to do content deployments and I want to use the same filelist to be submitted to STAGING area using submittask after content approval.
I dont want to attach the file list with my workflow. Is there any other way where we can feed information from filelist to submittask for submitting the files to STAGING area??

I dont think I can use this kind a piece of code as I create the filelist as a task of the workflow and this is something compile time info Smiley Sad

for (my $i = 0; $i < @submit_file; ++$i) {
__INSERT__("
"comment='__TAG__(iw_file_comment_$i);'/>");

}

Cheers!

Find more posts tagged with

Comments

ISCBorisB

Hi,

We create filelist to do content deployments and I want to use the same filelist to be submitted to STAGING area using submittask after content approval.
I dont want to attach the file list with my workflow. Is there any other way where we can feed information from filelist to submittask for submitting the files to STAGING area??

I dont think I can use this kind a piece of code as I create the filelist as a task of the workflow and this is something compile time info
[html]for (my $i = 0; $i < @submit_file; ++$i) {
__INSERT__("
"comment='__TAG__(iw_file_comment_$i);'/>");
}[/html]Cheers!

Depending on when and how "...we create filelist..." you may be able to add your Files on the fly from the external or cgi task.
TeamSite::WFtask::AddFile and TeamSite::WFtask::AddMultipleFiles.

jkm

I am creating filelist using an external task when workflow starts.
I dont want to attach the files in the start because in the approval mail I dont want to send a long filelist.

After approval, I have the filelist but it is not attached to workflow and I need to run another task to attach the files.

I dont like this way much .. seems to be a crude way of doing things

yes, i know I can attach the files using an external task but I wonder if I can just supply a OD-deployment filelist to submittask and same should be submitted to STAGING as well..some more sophsticated and elegant way to do this rather than running as an external task to attach files Smiley Happy

Migrateduser

You can do any of this but it will involve a little more work on your part.

For instance, you could write your own submit task. Instead of using the nice, neat OOTB functionality that Interwoven provides, write an externaltask that will do effectively the same thing. But you could create an OD-type filelist in your initial task and then attach them (and then submit) in your externaltask. Just a note -- you may want to have separate externaltasks: one for attaching the files and then the next for submitting them.

There are a few other ways I can think of going about this but, just like the others I'm thinking of, the example above doesn't seem like much additional work.

Dave

Adam Stoller

I am creating filelist using an external task when workflow starts.
I dont want to attach the files in the start because in the approval mail I dont want to send a long filelist.

After approval, I have the filelist but it is not attached to workflow and I need to run another task to attach the files.

I dont like this way much .. seems to be a crude way of doing things

yes, i know I can attach the files using an external task but I wonder if I can just supply a OD-deployment filelist to submittask and same should be submitted to STAGING as well..some more sophsticated and elegant way to do this rather than running as an external task to attach files

OD and iwsubmit both allow for filelists - but the format of those lists are different - so you cannot use the same filelist for both operations.

If you're concerned about email notification having the full list of files you could modify the notification mechanism to strip out some of the files (if it's programmatically feasible to do so) and thus you could attach the files to the task and use the submittask as-is.

If you don't like doing that then, as has been mentioned - it's a matter of programming. You can have your externaltask that performs the deployment also perform an iwsubmit (preferably before the deployment), or you could have it add the files to the job and then transition to another submittask (though that's "wrong"), or you could have your externaltask the performs the notification send out the notification and then add the files to task (though that makes it difficult to use one of the provided scripts for notification).

examination_broadsheet.rtf

jkm

OD and iwsubmit both allow for filelists - but the format of those lists are different - so you cannot use the same filelist for both operations.

Just curious Adam, what is the filelist format for submitask? May be helpful in future. IWOV should follow same pattern rather than different ones Smiley Wink

If you're concerned about email notification having the full list of files you could modify the notification mechanism to strip out some of the files (if it's programmatically feasible to do so) and thus you could attach the files to the task and use the submittask as-is.

Yes, there are couple of way arounds for this problem and this is always possible but I wanted to do minimum amount of work which is just to add a new external task to attach files.

I have implemented this using external task now...but should be cool if formats are compatible or some flag in the submittask to accept different file format Smiley Happy

examination_broadsheet.zip

kaalraa

Just curious Adam, what is the filelist format for submitask? May be helpful in future. IWOV should follow same pattern rather than different ones

That would be something like dream come true!! There are many file formats being used by IWOV to accomplish different commands or CLTs.

Can log in as a feature request. :-)

Adam Stoller

OD and iwsubmit both allow for filelists - but the format of those lists are different - so you cannot use the same filelist for both operations.
Just curious Adam, what is the filelist format for submitask? May be helpful in future. IWOV should follow same pattern rather than different ones

I could understand this question better if not for the fact that the format of the filelist for iwsubmit is documented in the CLT manual and in the command line usage when you provide the '-h' flag. Have you tried looking at either of those?

If you're concerned about email notification having the full list of files you could modify the notification mechanism to strip out some of the files (if it's programmatically feasible to do so) and thus you could attach the files to the task and use the submittask as-is.
Yes, there are couple of way arounds for this problem and this is always possible but I wanted to do minimum amount of work which is just to add a new external task to attach files.

I have implemented this using external task now...but should be cool if formats are compatible or some flag in the submittask to accept different file format

I'm not sure what would be "cool" about it - the purpose of the two commands (iwsubmit, iwodcmd start) are different; their needs in terms of input are different; while I could certainly see it being convenient if they used the same format, I don't see it as a significant issue that they don't.

Migrateduser

The format of iwsubmit filelist is
----------begin sample iwsubmit filelist--------
/full/vpath/to/file1
comment for file1
/full/vpath/to/file2
comment for file2
...
---------end sample iwsubmit filelist------------

The format for od filelist is
---------begin sample od filelist-------
/relative/path/to/file1
/relative/path/to/file2
--------end sample od filelist--------

OD doesn't require any comments as the target servers usally web server does have comments for the files. In contrast TeamSite understands the submit comments and stores the associated comments with the file in the store.

test.rptdesign

runningdiff.txt

jkm

I could understand this question better if not for the fact that the format of the filelist for iwsubmit is documented in the CLT manual and in the command line usage when you provide the '-h' flag. Have you tried looking at either of those?I'm not sure what would be "cool" about it - the purpose of the two commands (iwsubmit, iwodcmd start) are different; their needs in terms of input are different; while I could certainly see it being convenient if they used the same format, I don't see it as a significant issue that they don't.

Adam, I am not saying this is big issue from development perspective but this is nice to have this feature not *must have*

These two commands are certainly different but these are closely associated at the same time because in most of the cases people like to submit the content to STAGING when it gets deployed.

On the simiar lines, we need to find the DCR while submitting the content, these features should be as flag for submittask.
something similar for unlock files in earlier days of TS when user has to unlock file and the dcr individually which has been changed from 6.0 I believe.

Adam Stoller

Adam, I am not saying this is big issue from development perspective but this is nice to have this feature not *must have*

These two commands are certainly different but these are closely associated at the same time because in most of the cases people like to submit the content to STAGING when it gets deployed.

On the simiar lines, we need to find the DCR while submitting the content, these features should be as flag for submittask.
something similar for unlock files in earlier days of TS when user has to unlock file and the dcr individually which has been changed from 6.0 I believe.

You seem to be drawing an association between the two utilities which is tenuous at best, however if you want to think of them in such terms go ahead. For me, they're separate tools and if/when I need to use them in conjunction with one another I simply write some code to do what I need (which may or may not require filtering out some submitted files from getting deployed or possibly even adding files that weren't submitted to get deployed [rare, but possible]).

With respect to submitting, locking, and unlocking of templated files - I agree it would be nice to have a better built-in mechanism for being able to traverse from DCR or generated file(s) to each other - but creating a custom solution for handling that is part of what I'm paid to do and what I tend to find interesting and often enjoyable about my work - because what works for one environment doesn't always work for another.

Sample.txt

csv_export.rptdesign

Migrateduser

To throw in my $0.02, I tend to prefer that the functionality is separate. First of all, the iwodcmd and iwsubmit commands are associated with two completely separate products entirely: OpenDeploy and TeamSite, respectively. As fish pointed out, what works for one organization may not work for another but more importantly to me, the fact that these are separate tools allows them to be used interoperably, if necessary, without any reverse engineering. I'm not sure that the payload would be that great if Interwoven were to invest the resources to incorporate the iwsubmit functionality into iwodcmd, for instance, knowing that these two commands live wonderful lives distinct from each other and that it's not that much overhead to use these two separately, in different tasks.

Dave