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

Workflow default buttons

Ottawa_IWOV

Hi all,

We are doing some validation in workflow and echoing error messages with TAG_INFO directives. We have a situation where a user is being echoed a message because the file they are submitting is already in the workflow system. Is there something I can do with the Submit button? Can I change the behaviour of Submit to simply close the window?

Any thoughts on this would be great!!

Thanks.

Lucas Cochrane
lcochrane@deloitte.ca

Find more posts tagged with

Comments

JonathonG

AFAIK, there's not an easy way to do this. But, you could probably do something with pre_tagtable_html in the CGI_info section. You can define javascript there that might be able to access the Submit button and change what it does. I've done something similar with changing the button behavior on DCTs in 5.5.2, but haven't tried it with workflows.

Jonathon
Independent Interwoven Contractor

Migrateduser

There is no supported way to directly change the behaviour of the Submit button in 5.5.2 (if that is the version you are running.)

Suggested work-arounds:
1. Start a trivial workflow that simply ends, or
2. Prevent the input from the job instantiation form from being accepted under these conditions using input validation.

Brinko Kobrin
Interwoven Staff Engineer

Ottawa_IWOV

I would like some further info on "trivial workflow" that simply ends. Do I need as external task in this workflow. If not, what do I need to kick of the simplist workflow possible?

Thanks.

Lucas Cochrane
lcochrane@deloitte.ca

nipper

You probably need a dummy tast as a Start Task and then the end task.

Andy

jbonifaci

I'm not sure if you can have an end task as the start task, but I'm sure you can have a dummy task as the start task that transitions to the end task.

I would think that a better solution would be to just display an error message if the user cannot submit the file, and if they clicked submit, the workflow would just re-display the error message again and not try to start the workflow.

Adam Stoller

How about a cgitask as the start task with immediate="t".
The cgi script validates the files using whatever mechanism you choose. If everything is fine, it simply sends the javascript commands to close the window and transitions to the next task.
If there is a problem, it displays information in the window, provides a Close button (or similar) and then transitions immediately to the endtask.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com