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

modifying tt_data event

Renata

has anyone ever needed to modify the behaviour of tt_data trigger?

I understand how it works with DCR close adn that it sets off a WF. The little message box "do you want to submit your file for approval?" is missleading in my case.

My tt_data triggered WF sets the file's EA to values entered on the DCR (such as title). When an author saves/closes a DCR the WF should be triggered and reset the EA if necessary - not ask the user if they want to submit for review.

Can anyone share with me how to disable this little dialog box? I tired looking for a cgi or ipl fiel that would call it out and I can't find any.

thanks you sooooooooo very much!

Find more posts tagged with

Comments

Migrateduser

I don't think you can modify that pop-up window. I think it is part of the Templating UI, not a separate utility or part of workflow.

If you are using TeamSite 5.5.2, you can set EAs on your DCRs without using workflow. FormAPI has an event handler for file save.

Brinko Kobrin
Interwoven Staff Engineer

Renata

Isn't it true that FormAPI is only supported by IE 5.5? This would cause problems here as we cannot guarantee that our users will actually use IE 5.5 (it has been recommended to them)

thanks anyhow

Migrateduser

Yes, you are correct. The current implementation only supports IE 5.5.

Brinko Kobrin
Interwoven Staff Engineer

Renata

would you by any chance know how to ommitt the dialog box asking the user if they want to submit or not? We don't want them to have that option, their files should go through the workflow everytime.

thanks!

duartecordeiro

Think of a workarea as a..... workarea.
If a user is interrupted in the middle of filling a DCR, he just saves it. After that, he can open it again and finish his job, or just submit it.
Also, if you want to let a user to select multiple DCRs for submission, you have to let him answer "no" to that question.

So, just educate your users.. until they submit, the file "doesn't exists". Hope it helps.. there's another thread discussing this topic, but its the same conclusion.

--
Duarte Cordeiro
Neoris Pootugal

Renata

educating the users only goes so far - the purpose of our background workflow triggered by tt_data is not a default submit wf. our customized workflow has very little to do with submit, it runs external task to capture some values off the DCR and writes them into MetaTagger, for example the dcr.title becomes one of the metadata tags and every time a user would change a dcr we need to reflect that change, i.e. don't give the user an option to "cancel".

Eventually we may want to improve the process by adding the submit and approval cycles, for now meta capturing is mean to happen in the background and not be optional to users.

thanks anyhow - we have in fact opted for "educating" as a short term solution, however in the long term I don't think we should rely on users saying "yes"