I have record A with some filters and record B without any filter conditions. Wh

Hi Kalpana, to best of my knowledge this is not feasible to route to next screen, in order to avoid there is one possible scenario,where we can try activity chaining of the nodes in the process model. break the activity chaining so that the flow will stop and the user will be required to navigate back.

kindly read another record* in above comment.

I have tried breaking the activity chaining as well as route to other UI screen after that, but still the error message is displayed.

It is Appian's default behavior to take user back to the origin when you perform any action. So, when you are in Record and initiated an action from the record, after completion of the action, user will be redirected back to the action of that record.

If you are performing deletion then after completion of the action, the original record might not be present. Hence you get the error.

On thing you can do is have a User Input Task which contains the link of Record B. Place this task before the process ends in the process model. That way, you can force user to click on that link in order to proceed. Also, add a timer exception on that User Input Task so that unnecessary accumulation of processes can be avoided.

I hope this helps.

Another idea: Offload the delete action to a sub process and delay it for a minute or so. The the user is routed back to the record without any error. If your record has a status or a isDeleted flag you can show this to the user. This way the user knows that the record is delete but does not have to click any links etc. Related actions should only be shown for not-deleted records.

This has been discussed before - probably the best option is to present the user a confirmation screen that contains no buttons but does have a dynamic link back to the record list view. Within the process, the user input task that shows the confirmation screen can be skipped using a rule that triggers immediately - that way the process completes, the user can see the screen and has a navigation path back to the record (but they won't ever see an error), and the process can complete successfully.

Thanks all. I have kept the UI task with link. The move to record B is successful, but when the user clicks the link, but when tries to click summary/news/related actions instead of the link the error message is populated again.

Hi Kalpana, the options you mentioned are visible OOTB under records and we do not have any control on them.