Object dependencies - rules

The Object Dependency feature needs significant improvement to be truly useful for admins.

First, the dependency view must allow filtering of dependent rules based on meaningful criteria such as:

• Active / Inactive

• Scheduled / Not Scheduled

• Read vs Write dependencies

Without this, it’s extremely difficult to identify which rules are actually impacting an object versus those that merely reference it.

Second, the Object Dependency feature still shows obsolete rules that no longer exist in the system, including older generation rules that pre-date the Horizon Rules Engine. This creates confusion and reduces trust in the dependency data, especially when we are performing cleanup or impact analysis.

There is also a suggestion in this thread to rely on Analyzer, but unfortunately this is not a reliable alternative. In multiple cases, Analyzer does not surface correct or complete dependency information.

For example:
In our Gainsgiht instance, The “X” field on the Person object is actively used in several rules

Even after repeatedly refreshing the Data Flow Diagram, Analyzer does not show the respective rules at all. This is just one example among many.

Additionally, earlier this week I attempted multiple times to refresh the Data Flow Diagram, but it did not refresh for at least four days, further limiting its usability.

As admins, we need a reliable, accurate, and filterable way to identify dependencies before making changes to objects or fields. Today, neither Object Dependencies nor Analyzer fully meets that need.