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

Starting a workflow on finish

chetansethi

Hi,

I need to instantiate a workflow as soon as the user clicks Finsh on the DCR.
Could someone tell me which event should I use to trigger the workflow. The issue is that the user can choose to click on save and then on finish which means I can't work on the onSaveValid event. I tried putting the code in onClose event, but that event is called even when the user click on cancel button.

Any help is really appreciated.

Cheers,
Chetan
TS: 6.1 sp1 on Solaris

Find more posts tagged with

Comments

Adam Stoller

Hi,

I need to instantiate a workflow as soon as the user clicks Finsh on the DCR.
Could someone tell me which event should I use to trigger the workflow. The issue is that the user can choose to click on save and then on finish which means I can't work on the onSaveValid event. I tried putting the code in onClose event, but that event is called even when the user click on cancel button.

Any help is really appreciated.

Cheers,
Chetan
TS: 6.1 sp1 on Solaris

Have you made sure that there is a workflow defined for command = tt_data in your available_templates.cfg file? If so - clicking Finish should prompt you for initiating that workflow automatically.

ravio

Hi,

I need to instantiate a workflow as soon as the user clicks Finsh on the DCR.
Could someone tell me which event should I use to trigger the workflow. The issue is that the user can choose to click on save and then on finish which means I can't work on the onSaveValid event. I tried putting the code in onClose event, but that event is called even when the user click on cancel button.

TS: 6.1 sp1 on Solaris

The tt_data event that is fired when a new DCR is created and even if user clicks the Finish button there is going to be a Save and Close.

So, if you configure your workflow to use *tt_data* in available_templates.cfg I think you will get what you need

And if you want to specifically want to handle buttons in formapi you need to write a save handler and for this, the form api manual is the right place to look.

Migrateduser

tt_data will get you what you need on "Finish" but you'll also need to educate your users about using your app and about TeamSite, in general. If you tell them that they need to click on FINISH to start a workflow then they're either idiots or negligent for doing anything else. As you might be able to tell, I'm against building something that's 100% idiot-proof, as I believe that the user community needs to take some ownership of the product.

chetansethi

I know about the tt_data but the problem is there are a few workflows which can be triggered through that route on the same branch. I dont want the user to show the list of those available workflows, instead I want one specific workflow to get triggered.

As mentioned previously, i have used onSaveValid and onClose events but both have some issues and the guide doesnt mention any other event which i can use.

Cheers,
Chetan

ravio

I know about the tt_data but the problem is there are a few workflows which can be triggered through that route on the same branch. I dont want the user to show the list of those available workflows, instead I want one specific workflow to get triggered.

As mentioned previously, i have used onSaveValid and onClose events but both have some issues and the guide doesnt mention any other event which i can use.

Cheers,
Chetan

You haven't mentioned what kind of problems you have with the other events.
However, if you are looking at it from the perspective of defining an action for a particular button then all you need to do is handle the buttons.

Here is an extract from the formapi manual:

The onSave event handler is passed an integer that indicates what button triggered the
event. In this way, the save handler can determine how the save was triggered and behave
differently if necessary:
function saveHandler(button) {
switch (button) {
case IWDatacapture.SAVE_BUTTON:
case IWDatacapture.SAVEAS_BUTTON:
case IWDatacapture.SAVECLOSE_BUTTON:
// User clicked 'Save', 'Save As' or 'Finish'
...
break;
case IWDatacapture.PREVIEW_BUTTON:
case IWDatacapture.GENERATE_BUTTON:
// User clicked 'Preview' or 'Generate'
...
break;
}
}
Note: Code references to SAVECLOSE_BUTTON refer to the Finish button in
ContentCenter.

So, when you catch the Finish button you can probably trigger a workflow using a CCI command URL and there has been a recent discussion on this issue too.

I hope this helps

deepakb

If you have workflows specific to certain DCT's, then I guess you can handle that through available_templates.cfg. For each workflow you can specify multiple branch path, and in the branch path you can go on till templatedata/category/datatype. So in you case you can have multiple branch_path (although it will be same branch, but different datatype)

For example: if a particular workflow need to be available for 2 DCT then branch paths can be some thing like this.

/default/main/branchA/WORKAREA/WA1/templatedata/category/datatypeA
/default/main/branchA/WORKAREA/WA1/templatedata/category/datatypeB

Adam Stoller

If you have workflows specific to certain DCT's, then I guess you can handle that through available_templates.cfg. For each workflow you can specify multiple branch path, and in the branch path you can go on till templatedata/category/datatype. So in you case you can have multiple branch_path (although it will be same branch, but different datatype)

For example: if a particular workflow need to be available for 2 DCT then branch paths can be some thing like this.

/default/main/branchA/WORKAREA/WA1/templatedata/category/datatypeA
/default/main/branchA/WORKAREA/WA1/templatedata/category/datatypeB

This is what a lot of folks would like - but what Interwoven has (as far as I know) never provided. For tt_data workflows, the branch_list entries are just that - branch paths - not area paths.

You could have a single tt_data workflow that kicks off with the attached DCR, determines the category and datatype and then kicks off another workflow explicitly (i.e. not defined with tt_data) and ends - as a means of working around this short-coming.

Or - you have to play around a bunch more with the FormAPI code to trap the event you want and determine from that what you want to do.

Personally - I'd probably go with the parent-child workflow approach if I had to, but more than that, I'd rather drive the entire process with a workflow instead of kicking it off after the DCR has been edited.

miletwo

This is easily accomplished without tt_data. I recently did same as so:

- listen for saveDone and send out via callServer to CGI for regen.
- callBack from regen to form for success/fail of regen
- open window for another CGI to handle your workflow (assuming you want to capture comments, etc.) or use callServer if no interaction necessary

The thing that confused me and took so long to figure out was the fact that IW gives us a handy .save() mechanism, but no .generate() or .submit or .newjob() from within the form.

Now that would be sweet.