What's the difference between recalling a proposal and data override?

[Jennifer Bliss]

Anyone that has access to create a proposal will also have access to recall that proposal. Currently only SPO staff and Clarisa Avila have "Proposal Create" + "Proposal Aggregator" permissions, so we're the only ones who can recall a proposal. 

The good and the bad about recalling a proposal:

When you recall a proposal you can make ANY changes you want to the record. The drawback is that everyone in that proposal's routing chain gets an FYI and unfortunately we can't configure or turn off this notification. You can avoid the auto-FYI messages if the proposal is rejected (by a signing official including Cindy). When a proposal is returned by an approver it goes back to whoever initiated the proposal for corrections without FYI notifications going to everyone in the route chain.

When you recall a proposal or it's rejected, you must modify the record (by adding anything to it). If you don't modify the record, the [Submit for Review] button won't reappear (so you can't re-submit it into routing). 

 

Another option is called Data Override. SPO can modify certain elements of a proposal while it's en-route but not all. See What fields can SPO modify in a proposal that's en-route (via Data Override)?