Hi there, our users are very trigger happy on the close window button (red cross

Hi there, our users are very trigger happy on the close window button (red cross). I try to solve this by adding a timeout to nearly all my user input tasks that abort the intended process or revert to a valid status. This adds a lot of work to development and does not solve all cases. And a lot of our users do not understand what happens, as they tend to think that the system they are using is some form of a CRUD application on top of a SQL DB instead of a BPM system.

How do you handle these problem?

@Appian PS: What does Appian think of how this SHOULD be solved?...

OriginalPostID-60748

OriginalPostID-60748

  Discussion posts and replies are publicly visible

Parents
  • Obviously, this seems to be a training issue. So the users need to be trained on how to use the solution. Having said that, your approach of having an exception flow to kill the task is a valid one but I also understand that too many of these are not ideal and can be challenging to build and develop.

    You can also use start-forms where possible. Closing start forms will not start the process and thus alleviate the need for exception handling. Another option is to modify your design to use quick tasks for actions. These may be of some help as well (similar to start-forms)
Reply
  • Obviously, this seems to be a training issue. So the users need to be trained on how to use the solution. Having said that, your approach of having an exception flow to kill the task is a valid one but I also understand that too many of these are not ideal and can be challenging to build and develop.

    You can also use start-forms where possible. Closing start forms will not start the process and thus alleviate the need for exception handling. Another option is to modify your design to use quick tasks for actions. These may be of some help as well (similar to start-forms)
Children
No Data