Can we avoid the transition screen after setting metadata

TeamSite 6.5 SP1
Solaris 2.9

I have a cgi task in a workflow that calls the Interwoven provided metadata tagging functionality (not metatagger).

The command of the cgi task is /iw-cc/tag

I want to allow the user to enter their values and hit the save and close and move the workflow along without having to choose the transition and enter transition comments.

I have played with the parameters that are passed to the URL and can't seem to find a combination that gives the desired functionality.

cgi_transition=false
do_transition=
transition=0 or "Complete"

Can someone shed some light on this, or do our users just have to deal with the extra clicks?

Find more posts tagged with

Comments

Adam Stoller

TeamSite 6.5 SP1
Solaris 2.9

I have a cgi task in a workflow that calls the Interwoven provided metadata tagging functionality (not metatagger).

The command of the cgi task is /iw-cc/tag

I want to allow the user to enter their values and hit the save and close and move the workflow along without having to choose the transition and enter transition comments.

I have played with the parameters that are passed to the URL and can't seem to find a combination that gives the desired functionality.

cgi_transition=false
do_transition=
transition=0 or "Complete"

Can someone shed some light on this, or do our users just have to deal with the extra clicks?

I haven't tried using the CCI URL for metadata capture (I usually call the iwmetadata.cgi directly or via a wrapper script) - but perhaps if you set the done_page for 'tag' to point to the CCI URI for 'transitiontask' with cgi_transition=true - it might work...

gzevin

I haven't tried using the CCI URL for metadata capture (I usually call the iwmetadata.cgi directly or via a wrapper script) - but perhaps if you set the done_page for 'tag' to point to the CCI URI for 'transitiontask' with cgi_transition=true - it might work...

I did research this recently - it appears that this functionality could not be switched off. At least this is what was given as an answer in some earlier posts..

Will be interesting to hear the answer from IWOV engineers/product managers on that

Bill Klish

Well done Adam, you were pretty close.

I opened up a support case, but in essence the solution is as you describe. You need to override the done_page parameter sent via the Content Center interface with a call to the transitiontask CCI URL, specify the transition name via a transition request parameter, and then add a do_transition request parameter and set it to true.

Now if only you could change the buttons at the bottom to be something like Next >> .........

Hope this helps someone else.

Adam Stoller

Well done Adam, you were pretty close.

I opened up a support case, but in essence the solution is as you describe. You need to override the done_page parameter sent via the Content Center interface with a call to the transitiontask CCI URL, specify the transition name via a transition request parameter, and then add a do_transition request parameter and set it to true.

Now if only you could change the buttons at the bottom to be something like Next >> .........

Hope this helps someone else.

Did you ask them to open up a doc bug/fr to get this more clearly documented in the manuals?

Bill Klish

The current feature request for the problem is #62249. I am following up to make sure the documentation needing an update is included in the FR.

civ3

Hi bk99nd

I wonder how you distinguish which button users click to do transition? For example, if users click "Cancel", the transition shouldn't happen. However at the moment the URL command seems not providing a way to this, mainly I want to present different result when they click different buttons. In this case, they are "Save and Close" and "Cancel".

Best regards,
civ3.

Well done Adam, you were pretty close.

I opened up a support case, but in essence the solution is as you describe. You need to override the done_page parameter sent via the Content Center interface with a call to the transitiontask CCI URL, specify the transition name via a transition request parameter, and then add a do_transition request parameter and set it to true.

Now if only you could change the buttons at the bottom to be something like Next >> .........

Hope this helps someone else.