delete workflow

Hi Guys,

I need to create a workflow for deletions.
Now the folk here aren’t keen on using File/Delete | List Modified | Submit.

They want it to be the same process as hitting the submit button and selecting the appropriate workflow.

So I’m investigating whether I can do something without too much mess.

You cannot trigger a submit workflow unless the file is modified, which may not be the case.

So what options do I have to trigger a workflow in the webdesk (author) interface besides the submit button.

I’m looking at the custom menu item option based on this article

Just want to know if people have faced a similar situation. Is this the way to go, or do I have other options up my sleeve?

Thanks

John Cuiuli
Consultant
Sydney, Australia

Find more posts tagged with

Comments

Adam Stoller

Consider masking out the OOTB Delete menu option and putting in your own custom Delete menu option that would:
(a) record the list of files pre-selected in the GUI
(b) Initiate a workflow
(c) in the workflow make sure the files are associated
(d) delete the files
(e) perform the submission.

Getting the workflow instantiated and the files associated with it are probably the tricky parts - I can think of ways of doing this, but most involve using iwjobc which requires 'master' priveleges so you'd end up having to have some aspect of the custom menu script be setuid 'master-user'.

One possibility that might avoid that is if you instantiate the workflow through the CGI from your CGI, it *might* still pickup the selected files from the TS GUI (or you might be able to coerce it into doing so).

Don't have time / bandwidth right now to try this out - sorry. But once you're past that step, the rest should be simple.

--fish
(Interwoven Senior Technical Consultant)

Johnny

Thanks for the tips fish.

Replacing the delete option with my own is how im planning to do this.

Im on Windows this time, so Id have to investigate how to impersonate a user, could be tricky as its an unknown for me. ---> anybody have an answer???

Also running iwjobc would mean i need a pre-generated WF xml spec, but there would need to be some interaction from the user.

iwwft_instantiator.cgi seems like the easiest hook even though I dont like using unspupported features. Though I dont see a large risk.

Ill let you know how I go.

Cheers

John Cuiuli
Consultant
Sydney, Australia

Johnny

I don't do it often, but a complaint is coming.

I think it's really ridiculous that I need to write a custom menu item to start a workflow as an author.

I cant understand why the File / New Job option isn't there.
It was there in the 4.x days and now its been taken out.

I'm sure there's a decent answer someone can give me to say why it is so.

And it better not be about licensing.

John Cuiuli
Consultant
Sydney, Australia

Adam Stoller

The fact that it showed up in the TODO List in prior releases was always a *bug* (it *never* showed up when in the workarea view) and it was finally fixed. Yes, it had to do with licensing. This **might** change in a future release - but until then, the only officially supported means for an Author to initiate a job are through the Submit button and the closing of a DCR being edited.

Feel free to log a case with Interwoven Support if you'd like.

--fish
(Interwoven Senior Technical Consultant)

Johnny

well what do you know... a useful 'bug' Smiley Happy

I wouldnt call that a bug Smiley Happy

Well I hope that doesnt mean I would be infringing on the license model then.

John Cuiuli
Consultant
Sydney, Australia

rpjoseph

Hi Johnny. We are also looking for a solution to delete files and submit those deletes. We are not quite sure why we have to have a custom solution for what we think should be a pretty common requirement. It sounds so much more difficult than I thought it would be.

What do you mean you will need a 'pre-generated WF xml spec' to run iwjobc? Are you thinking of calling iwwft_instantiator from your custom delete menu item and workflowing the deleted from there?

All of our workflows our built in .NET. We have tried implementing impersonation to resolve a problem with 'Modified By' showing up as 'SYSTEM' . We can fire most any command line via our API as an impersonated user EXCEPT iwjobc.exe. We do not know why. We placed a call with support 10 days ago or so and haven't heard anything. We posted to DevNet - no responses.

btw - I posted a similar note to this in a different forum (I think 'templates') yesterday. You might keep your eye on that post as well.

Johnny

Hi Joseph,

There is an OOTB solution for deletions.
As user would have to do the following.....

1. File / Delete
2. View / Modified Files
3. Submit the deleted file with a normal submit workflow.

Unfortunately our users dont want to get to know TeamSite well enough to think of these things. They have a Notes background which is quite easy to use.

iwjobc does not run a .wft file. IE no perl/template script tags.
You need to pass a true wf xml spec that has all the details filled out.

Yes I want to use iwwft_instantiator to call a wf directly, though it isnt on my plate just yet to complete.

The rename feature is interesting. Im pretty sure it leaves the original file as *deleted* in the workarea. End users would never think about having to submit the deleted file along with the new file.
Its another issue we have ---> I may just rip out the rename feature.

It would be nice to be able to have the option to tie these things up. Especially with DCR's and generated pages aswell. There would be plenty of issues to deal with though.

John Cuiuli
Consultant
Sydney, Australia

johnjamesmarsh

TS 5.5.2, Solaris 8
Hi all,

I am doing this already (ignoring the rights and wrongs of having to reverse-engineer what should be a simple function). I have custom menu items that call the iwwft_instantiator.cgi like so:

http://tsserver/iw-bin/iwwft_instantiator.cgi?iw_user=$user_name&iw_template_file=default/AACreateBaseline.wft&iw_workarea=/default/main/AA/Release/WORKAREA/Release$strURL

$strURL just contains the parameters passed into the custom menu item by Teamsite. It seems to work for us but we end up having a wrapper script for every single workflow.

Was someone suggesting above that we can change the default delete to run a custom script? That would be useful. I know I can add my own but.....

Also wouldn't it be great if we could add our own buttons to the GUI. Don't tell me, fixed in the next version.

Regards

John

Adam Stoller

>Also wouldn't it be great if we could add our own buttons to the GUI. Don't tell me, fixed in the next version.

Okay - we won't tell you :-)

--fish
(Interwoven Senior Technical Consultant)