Default filter in record

Question

Hello everyone, 
 I have a use case that a user should only be able to see records where he/she is assigned a task. I have implemented this using record default filter to only fetch the records where task is assigned to the logged in user. This is working fine and the record is visible to the users as soon as some task is assigned to them. Thing is they have to trigger the related action to complete their task. Hence whenever they finishes the related action(task), they are navigated to the record dashboard again and this time they are shown an error message stating the record is either deleted or they are not in the access group. The reason is as they don't have any active task in the record now, they are removed from record security due to default filter condition. 
 Is there a way I can handle this (as the error message looks bad) like adding default filter without actually using default filter attribute of record type? I still want them not to have access to record dashboard but without showing any error message. Any other alternatives are also appreciated. 
 Thanks 
 Shailender

aloks0189 · Answer

Hi shailenders as per my understanding, it's an expected behaviour of Appian. When you are having a related Action for a record, which deletes (soft / hard) the data from db, and you have configured chaining for immediate effect, in such case, Appian will try to load the record which doesn't exist anymore, and hence you will get an error message saying, "record is either deleted or they are not in the access". 
 
So as per my understanding, you have 2 ways to deal with it, 
 
1. Disable chaining, this will let you to come back to the summary view of deleted record, where data will be shown via the cache (due to lazy loading mechanism of JPA). 
 
2. Let the configuration to be as it is, and upon error navigate to record view (Grid / Feed) manually. 
 
Hope this will help

Ashvin Kapur · Answer

I would suggest chaining the related action to another "Confirmation/Navigation" form (a quick task) which provides a link to the user's homepage or other nav page. Don't include a "Submit" button on this form, so the user must click the link or navigate away from the page. Then set a ~5min timer exception on the quick task so the process ends after a few minutes. That should mitigate the issue of the error message.