Distinguish Delete actions for current record and related records
In the new Sky View , in the Activities Section of a Request, make the "delete" from behind the ellipsis into an actual "delete" button instead.
I found myself deleting whole requests, rather than duplicate forms or activities, after checking the box and hitting "delete". The delete action is behind the ellipsis, which is not intuitive and could cause problems down the road.
-
Shannon Brower
- Jan 19 2021
- Shipped
-
Apr 6, 2021
Admin response
Thank you for this helpful feedback! We've updated the "related records" section on all records. From now on, when you're viewing the main page for a record (the one with all of your fields), you'll see all the actions for that record. For example, on a request record, you'll see action buttons to approve it, generate a write-up or an email, etc.
But, when you click on one of the "related records" types in the left-hand sidebar (i.e., if you click "Payments" or "Reviews"), those action buttons will be hidden. You'll only see actions directly linked to those related records. (You can find actions for those records in the context menu next to each record, or by selecting the checkboxes next to them).
This was a pretty small change but it definitely feels like it makes a big difference in clearing up some confusion about which actions affect which records - thank you for helping us to spot that issue!
Related ideas
This should be a TOP priority. I have deleted multiple requests when trying to delete a review. In classic, we can delete assigned reviews from the list. But in SKY, when you click on reviews in the request record, it gives you a list of reviews that have been assigned and if you check the ones you want to delete and hit the "delete" button directly above them, it deletes the entire request. I can not tell you the problems this has caused. There should not be a DELETE button at the the top of a page unless it's function changes to the criteria on the screen.
Yes - I have just deleted a whole request without realising. Surely, there should be some way to retrieve deleted records at the back end of the database?!