Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
no "next" button on DCT?
plantronics
Hi all,
Im using the CCI URL commands (as they were called in TS 5.x, not sure what they are now called in TS 6.5) to directly launch users into DCT forms. At the bottom of the DCT form there is supossed to be a button called "Next" that will send the user through a workflow we have set up (gives a screen for submit now/new job, tagging, and then goes to our custom "Review and Deploy" workflow.
The issue is that when we use the CCI URLs to directly go to a DCT (either new or existing), that we do not get the "Next" button. In its place it a "Finish" button, and the user is not "corralled" into the workflow. When they click "Finish" the DCT window simply tries to close itself. So you see our problem here is that the next button is not showing up in this case.
If however the user goes in through the front door of Teamsite and uses the interface (Standard or Pro, does not matter) to navigate to an existing DCT or create a new DCT, the "Next" button shows up, and once the user is finished they can click this and be led through the workflow.
Another issue is that available_templates.cfg has been set up to trigger this workflow on the tt_data event (for all authors). Shouldn't a tt_data event be triggered for all "close" button actions (ie, the "Finish" button). If so, it is not working as my case above explains.
Any insights appreciated!
For reference, here is the entry in available_templates.cfg:
<template_file active="yes" path="default/author_review_and_deploy.wft"
name="Review and Deploy Author Work">
<role_list>
<role value='author' include='yes' allusers='no'/>
</role_list>
<command_list>
<command value='new_job' />
<command value='tt_data' include='yes' />
<command value='submit' include='yes' />
<command value='all' include='yes' />
</command_list>
</template_file>
Find more posts tagged with
Comments
Adam Stoller
You didn't indicate what version (and SP-level) of TS you are currently using.
There was an issue with tt_data in CCPro in the initial release of 6.0 (don't remember whether it got fixed in 6.1 or 6.1SP1)
Also - if a DCR is already attached to a workflow - it will not attempt to initiate a new workflow when the DCR is edited and closed (this is consistant with 5.x semantics - not a bug)
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
plantronics
We're on the very latest version (6.5.0 Build 45607 Interwoven 20050208 to be exact)
Ive been reading the UG for customizing the UI in TS 6.5 and it goes over the URL commands in detail. I think the designed behavior is to close the window unless the "donepage" parameter is passed in the URL command itself. This is very limiting! I thought of somehow passing the "newjob" URL command for the donepage which would then kick off the workflow, but the problem with that is, if it is a new DCR or there are new files being generated, I do not know what the file name(s) will be ahead of time in order to attach them as the new job (this needs to be passed in the vpath parameter in the newjob URL command). I thought of one workaround which may work. That is unless you think there is some other way Im not aware of (hope so). It goes something like this:
1) Open the DCT in a new window via the newform URL command.
2) Specify the opener of the page as the donepage parameter
3) As the DCR is saved and output generated, FormAPI events pass the values to the opening page via the window.opener object. Values are stored in javascript variables.
4) The user clicks Finish and is forwarded to the opening page, which now has the vpath values it needs to execute the newjob command. The page then laucnhes the workflow via the newjob URL command
I havent tried this yet, just an idea. It seems like a pretty bad hack for something that I would think would be standard functionality.
Adam Stoller
Not sure where the problem lies - however my general advice is to create DCRs *within* workflows and not the other way around. It allows you to enforce naming conventions, file location conventions, page generation conventions, etc.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com