Triggering a workflow at save of DCR

What is the best way to automatically trigger a workflow when a user saves a Data Record?

Find more posts tagged with

Comments

Use the "tt_data" command value in the available_templates.cfg file.

<command_list>
<command value="tt_data"></command>
<command include="no" value="all"></command>
</command_list>

Hope it helps.

shelbycha

Thanks for the feedback. I already have the above coded into the available_templates.cfg file. Is there possibly an adminstrative setting preventing it from working? Permissions or something? I'm not sure why the workflow will not trigger, but I think it's something external to the available_templates.cfg file. Would love your thoughts...

akshathp

One reason that the workflow might not be getting triggered could be related to user roles. I am not sure if in your tag in available_templates.cf you have included the "role_list" tag or not. The syntax is as follows:
<role_list>
<role value='editor' include='yes' allusers='yes'/>
<role value='all' include='yes' allusers='yes'/>
</role_list>

This tag controls the user role and checks whether a workflow is avaibale to the user in existing session or not. So the case could be that you must be testing the workflow as a role which is not entitled as per your cfg file.

Hope this helps.
Thanks,

Akshat Pramod Sharma
Interwoven Inc.

iwovGraduate

I understand that you are trying to kick off a workflow on DCR *save*. In case you didn't know, the tt_data event is tied to the *close* (not save) button of DCT.

akshathp

Yes, that's correct. tt_data event is tied with "close" and not "save".
But as per the posting, it seems user is using tt_data trigger as a command to activate the workflow. Hence I am assuming that this factor is already considered otherwise why would they be using this trigger at all..
Therefore, I suggested to check for the user roles before testing the workflow.
Thanks,

Akshat Pramod Sharma
Interwoven Inc.

Migrateduser

You can enable debugging of the available templates by setting $DEBUG_MODE=1; in available_templates.ipl . If you do that it will write out some helpful info to /iw-home/tmp/cci/templates.<pid>

Cheers
Rob
rob@bagpipe.com