Check that properties are saved before closing request
Tom Marshall
When a request is "won" (or lost, I suppose) there needs to be a check that the properties are saved. One of our employees edited a bunch of properties to reflect their sale details, then clicked on our "contract signed" stage and was surprised to find that all of the properties they had added didn't make it into the project. I did a quick test and verified this can happen as well.
RECOMMENATION: When closing a request, check if properties have been edited that are unchanged. If yes, popup a box pointing out the unsaved properties and give the user a chance to save them.
Max Kazakov
Tom, I'm sorry to hear that happened. Can you please confirm whether this is when you're bulk editing properties from the properties tab inside a request/project? What's the location where this is happening?
Tom Marshall
Max Kazakov Yes, bulk editing inside properties tab on a request. After the request is marked as contract sold you can still save the properties but since the project is already created they don't carry over.
Actually now that I'm thinking about it further, this can happen at any time. If I edit the properties of a project but then navigate somewhere else before I save them the changes are all lost. So I guess I would want a "are you sure" check before navigating away from unsaved properties.