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

importfiletotask setting target directory?

Adam Stoller

Environment

get automatically added to the task.I'm not sure if the task will automatically transition, but as long as I can cycle back to my original CGI script via the done_page=... parameter, I should be able to take care of that myself.So - has anyone successfully used importfiletotask?More to the point, has anyone figured out how to pre-set the desired target directory for the import operation so that the user doesn't get prompted?

Find more posts tagged with

Comments

Adam Stoller

I'm still working on this - and have determined a certain level of progress.

It seems that importfiletotask does note the vpath passed in - but still requires the user to click on a Next button to accept it (instead of just using it as given)

Unfortunately, I still need to get the cgitask to transition after the file has been imported and added to the task, and if I try to call back to my original cgitask script using the done_page parameter, I find that I'm severely lacking a lot of state information (in terms of form variables) - and that I only seem to be able to associate a single form variable with the done_page url - i.e.:

....&done_page=/iw-bin/myscript.ipl?task_id=$taskid

will ensure that the form variable task_id is set when myscript.ipl is called. However:

...&done_page=/iw-bin/myscript.ipl?task_id=$taskid&foo=bar

passes foo=bar to the initial CCI URL command and not to the done_page (myscript.ipl) URL.

I have a feeling that what I'm trying to do should not be that difficult, but I cannot seem to hone in on the resolution.

I'm trying really hard not to role my own file import code - but I'm starting to wonder if that's reasonable.

As a list of requirements for what I'm trying to do (in case it isn't clear):

ISCBorisB

I did something close to what you need once, only with 'import' instead of 'importfiletotask'. What I did was as follows:

1. Code *Call Back* import_completed() Function in the original CGI. Do what you need from there, (like Form post, etc)
self-close if needed.

2. Code another CGI and use it as the init's done_page Parameter. This CGI only purpose in life is to call back to
the original one and immediately self - terminate. Please note that both import(s) are Java Applets, they *do not count* in the
opener's chain, so it's opener.function() and not something like opener.opener.function() [html]
...
<script type="text/javascript">
function call_back() {
opener.import_completed();
self.close();
}
</script>
...

...
[/html]Btw, unlike 'importfiletotask', import honors vpath the way you want it (use as given, no *Next* Screen/Button), you'd have to attach Files yourself though.
Problem is, you would also have to segregate imported Files for various WFs, perhaps by .../target/Job_ID folder, etc...

Adam Stoller

I decided to change my approach and have my cgitask script be a "main console" with three buttons:

This doesn't solve the problem of having to go through two steps on the import - but it does at least "work".I have a case open with support to see if there's any way to get a pre-set vpath to be used without the extra prompt.Thanks anyway,

Tanuj

Where can I fing more information on importfilestotask for workflow modeller?

Thanks

Adam Stoller

Where can I fing more information on importfilestotask for workflow modeller?

Thanks

I'm not sure where one can fing anything.
As for finding things about this - I'd suggest looking at the UICG.
As for what's relevant anymore - I don't know - the previous post in this thread was from over 2 years ago.