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

Validation message require

System

Hi,

I have a workflow template that needs to perform some validation message that, after submit the workflow some files may be overwritten.How can I display an Validation message from the workflow template Perl code to the user and let them know ?

Thanks,
-Rishi

Find more posts tagged with

Comments

kaalraa

Rishi,

Could you please elaborate as what exactly your requirement is? As far as i can think of in the defined statements of yours, you want to report the conflict of files at the time of submission.

If yes, then you have to use a CGItask which checks the validity and in turn callback as per the result. Still if you can provide more details.. it would be helpful.

Migrateduser

kaalraa

i need something like javascript alert function so when user press the workflow submit button, a popup message says "the files will be updated".

can you just suggest me how to do that?

Migrateduser

can i use javascript function alert("blaw blaw ") in tag_info{} or i need something like javascript alert function so when user press the workflow submit button, a popup message says "the files will be updated. are you sure you want to continue?" (Followed by Yes or No options)

Adam Stoller

Do you need this message to appear during instantiation?
If not - you could easily have a cgitask as your start task (with immediate="t")- which would give you a lot more (and easier) control over the UI semantics.

Assume the cgitask has [at least] two successors - one which proceeds to the submit operation (perhaps through a review cycle) and one which simply ends the job without doing anything.

The cgitask script can then present a list of the files associated with the workflow, indicate to the user that these are the files which are set to be updated and provide two (or more) buttons for what to do ("Proceed", "Cancel") which would be tied to the callback values for the cgitask.