We continue to recommend to run the Gateway-level revert by clicking "install previous revision" from the "Policy Installation History". This makes the Security Management Server silently log into that previous Management revision, collect all the data from it - including rules, objects, gateway settings, topology etc., and install that policy on the Gateway. This is a one-click revert on the gateway side. It then buys the administrator time to understand the root cause of his Management state and fix it manually.
We have an individual rollback button for IPS.
The "Revert" button, as seen at the Layer History page, only reverts rule add/remove/picking/unpicking objects in rules, and not the object operations themselves, therefore it is only recommended if the administrator is OK with these limitations. Since in most cases a rule change also consists of an object property change, it is reasonable not to use that option so frequently. The "Install previous revision" from "Policy Installation History" might be better in these cases.
At Check Point we are committed to preserving the integrity of our customer's data. This is why R80 added cross-object validations, protection of Check Point content, server-side auto-save, and granular permission profiles.
We are taking the time to introduce more features for revision rollback and will introduce them after they get the proper internal certifications. As long as they are not yet added to the release, we recommend our customers to rely on the Install Previous Revision, in addition to enjoying the operational efficiency and reliability features that we added to R80 and above.