Tempo Related Action - Delete Record

We have functionality where, we create a temporary records, once the purpose is fulfilled the un-used records are to be cleaned out- (Soft Deleted from Database Table)
This is achieved through related action on the record.
After the related action is performed, the default screen is the summary dashboard of the record (that we just deleted). As this database record is no longer exist, we get an error:
An Error Has Occurred*
The record data does not exist, has been deleted, or you do not have sufficient privileges to access it. (APNX-1-4205-006)

As per my research in forum, I found this entry:
forum.appian.com/.../e-141459

As the comments are from 2015, was hoping there some other work around, if any ?

Is there any Submit button image field ?
Is there any process level - redirect link available ?

OriginalPostID-238785

  Discussion posts and replies are publicly visible

Parents
  • Hi
    I have had the same issue and had done something different to what have mentioned in all comments. May not be the best solution but it worked for most cases. Though the implementation is all up to the scenario.

    I have maintained a status for the record in flight and as soon as I invoke the related action to delete the record I update the record with the status. (for ex, cancelled) This status is used to in related action/dashboard visibility conditions. and in process process model I have put a timer about 5 seconds before trigger the delete from DS smart service. So once user click on the submit button on the delete related action user will land on summary page with out error message as record still exists and all related actions/ all other dashboards except summary view will be hidden.(So your is kind of force to navigate back to record list)
    The record will be deleted from DB after 5 seconds. In my scenario this works fine as once users deleted record they normally go back to record dashboard again.

    Might help in your scenario too,

    Regards
    Suresh
  • Hi Suresh, thanks for your comment.
    I like a lot your creative approach, but not sure that i got all the controls you are applying. Can you show an example?
    If I'm understanding correctly, the sequence you suggest is:
    1 User is in the details of a record
    2 Clicks on the delete related action
    3 You show a confirmation (record deleted), but still remain inside the record detail
    4 The record is deleted (delayed delete)

    Not sure if in 3, you are sending the user there or back to the record list. If the former, what prevents the user to click on any action in the record summary after 5 sec and get an error?
    If you are sending the user back to the record list, can you show how you do this from an interface of the related action?
Reply
  • Hi Suresh, thanks for your comment.
    I like a lot your creative approach, but not sure that i got all the controls you are applying. Can you show an example?
    If I'm understanding correctly, the sequence you suggest is:
    1 User is in the details of a record
    2 Clicks on the delete related action
    3 You show a confirmation (record deleted), but still remain inside the record detail
    4 The record is deleted (delayed delete)

    Not sure if in 3, you are sending the user there or back to the record list. If the former, what prevents the user to click on any action in the record summary after 5 sec and get an error?
    If you are sending the user back to the record list, can you show how you do this from an interface of the related action?
Children
  • Hi

    To make it simpler i'll put in point form, I know my explanations can be messy sometimes :(.

    1. user click on a record and move to record summary
    2. Initiate related action to remove the record from DB.
    3. Once user submit the form user will be navigated back to record summary dashboard.
    a. Once user click on last submit button on delete related action record in DB will not be deleted at the same time. Instead will split the flow in to two and one goes to an activity chained process will an end event where a status of the record is updated to either "Cancelled or Mark for Deletion". other path (with our activity chaining) will goto and timer event where it will wait for 5 Seconds before proceed and delete the record.
    b. once you set up the process like this your will be landed back on record summary view because record is still not actually deleted
    from the DB. In the record you can use the status to hide all your related actions and all other dashboards so use doe not have
    any option to take but navigate back to the main record list.

    This has it's own drawbacks. there can be scenarios once user move back to record list before 5 Sec completes he can choose the record again, but due to visibility conditions no actions will be provided for the end user.
    Also if user stays on the record summary for more than 5 Sec and refresh the screen user will get error message as record is now no longer available.

    But as i said it work for my scenario. you can give it a try and see if it works or not.
  • :) Pretty much clear now, thanks for the detail !!

    Your trick then is having the summary completely tailored to show nothing but the path to the user back to the record list once you changed the record status.

    For a moment I thought that you were able to present to the user the record list, option that I haven't found, and that was my initial intention when I initially asked about this.

    All I found is a way to generate the URL for the record list. So, once the delete related action is finished I present a blank screen with only this link. Unfortunately I only can call the record list URL within an external link component, which therefore opens a new window, missing the effect of sending the user back to the record list once the related action is finished.