Possible to delay submission of a form via Portal?

[Shane J]

Is there a way I can put what equates to a delay after submission of specific forms in the Portal?

I have delay of 1 second in my main REQ workflow in order to color code RITMs with the same parent REQ (without the delay it doesn't work).  So right now the customer's list of tickets loads immediately after submission but without the color (if they gave it another second and reloaded it would be fine).

If it's a matter of delaying every submitted form by a second, I think I could live with that.

[Chuck Tomasi]

I've always been told that making a user (and system) wait using sleep()/delay(), or whatever functions are bad. They tie up resources for no reason.

While the colors sound like a great idea, are they REALLY necessary to cause a user experience delay or system resource allocation? What's the value of those colors and the cost of this customization? That's the better question.

[Brad Tilton]

I agree with Chuck, tying up the user's session for even a second or too seems bad. I would instead consider something like adding an automatic page reload to the tickets list or a button that allows them to reload the page and get the color codes. Another alternative would be to direct them to a different page on submission that tells them they'll be redirected them to the tickets list after a second.

[Shane J]

I'm getting piled on by the heavy hitters of the Community.  😉

I don't want to make the customer do anything but submit, so the alternate page to act as the delay may work.

[Shane J]

It comes down to not having a better way to show a customer that a set of RITMs have the same parent REQ when an Order Guide is used.  I originally thought about just showing an additional column, but there are two issues with that:

• We use the Task table to show customer's their 'tickets', so to have a column specific to RITMs could cause confusion.
• We have done everything we can to hide the multiple layers involved in the REQ process from our customers.  Sure it's as simple as showing the parent REQ if there is one, but that will cause more confusion and questions than we want.

So I came up with the coloring option.  It should readily show 'related' RITMs when a customer is reviewing their tickets, while leaving the other non-REQ and non-Order Guide tickets alone.

If you have a better idea, I'm all ears.