ServiceNow: Building Powerful Workflows

Relying upon other updates

Some dependencies can be detected. If a UI Policy Action is missing the UI Policy or if an onChange client script is registered against a field that does not exist, then the platform will produce a record of the problem. However, this is not always successful, especially when the dependency is in a script. The following diagram shows this situation:

In this example, both the UI Policy and the Business Rule rely on the new field. Perhaps the UI Policy makes the field mandatory in some circumstances, while the Business Rule script will validate the data.

If only Update Set Y is applied to the target instance and Update ...