Hi, I'm new to Appian and I can't get past this issue. Ex. I have a running process with one instance which is currently at the interface node. When I click ctrl + r, browser refreshes, the process instance is cancelled and a new instance is started. Upon instance cancellation, my data gets messed up in DB. So my questions are:
Thank you for the info.
Also, Peter Lewis, "Tags" section on the question input form is not working, it crashes the form and needs to be reloaded. I don't know how to create a bug for the forum so I tagged you.
Discussion posts and replies are publicly visible
Since ctrl+r is a browser shortcut to refresh browser, not an Appian hotkey, not sure you can prevent the action without diabling the shortcut (i.e. the chrome extension, but for every user...)When I hit ctrl+r, my process is not cancelled - it is just no longer being shown and if I have a task queue I can pick it back up there. Can you monitor the process and see is it really 'jumping to end event' due to the refresh or maybe because of an exception flow?
usually you don't move in the process until you submit a form. Do you have a submit button set up? and if yes, how did you set it up?
Never had that issue, so you could you explain a bit more
1. How do you initiate the process (i.e. via user start form?)
2. How do you submit the tasks
Yeah -- "Tags" has been messed up here for as long as I've even known about the feature (and maybe for as long as it's existed). You have to avoid even clicking on the field or else it erases your entire (unsaved) post. I believe you can direct inquiries to community@appian.com - but I'm not sure there's much they can do about it as (AFAIK) it's running on outside software.
Mike is correct - we are aware of this issue and have reached out to our vendor to help get this resolved, but there is no update at this time.
Hi guys,Is there any update on this so far?
Do you mean the browser refresh issue, or the "Tags" issue?
Hi Stefan,Yes, refresh issue, on refresh a UIT, system initiates a new instance.How can we stop that?
I remember a scenario in which this happens.
A process model WITHOUT a start form, but with an initial user input task is used as a page in a site. Such a setup would lead to the behaviour you see.
That is a problem that you need to solve by using process start forms instead of initial user input tasks.
Does this correlate with your situation? If not, please describe your specific setup in detail.