Generic Global Coercion Rules

Two sets of server coercion rules exist that the system applies to all acquired objects, whether the device is registered or not.

These rules include:

First set - The preceding inbound coercion rules and is applied before any device-specific rules are applied
Second set - The trailing inbound coercion rules, applied after the device-specific rules
First set - The preceding outbound coercion rules and is applied before any device-specific rules are applied
Second set - The trailing outbound coercion rules, applied after the device-specific rules

The generic coercion commands are identical to the device-specific commands. They are configured in the Preceding Global Coercion Rules and Trailing Global Coercion Rules sections of the Devices page. To inform administrators that these generic rules exist, they appear in uneditable tables before and after device-specific coercion rules on the Edit Device page.

Viewer Coercion Rules

Viewer coercion rules modify data loaded into a viewer session when it initializes. The coercion rule set is the same as that which is used for server coercion rules. The rules are server-specific and get downloaded or re-downloaded to the viewer each time the user logs onto the server. The rules are applied to the data when the viewer loads it, whether from cache or on-demand. The primary difference between server and viewer coercion is viewer coercion does not affect the original data stored on the server. The modified data exists in the viewer session only. When the viewer session terminates, the modified data ceases to exist.

To define viewer coercion rules:

Select Admin/Devices
In the Viewer Global Data Coercion Rules section, enter the coercion rules
Click the Save icon

See: Coercion Rules