Previous Next
Opalis Integration Server > Policy Testing Console > Functionality Differences Between the Client and the Policy Testing Console

Functionality Differences Between the Client and the Policy Testing Console
The Policy Testing Console enables you to simulate most functions that the Client performs. However, some functionality is not the same in, or is absent from, the Policy Testing Console.
The following is a list of items that function differently in the Policy Testing Console.
Trigger Policy object – this object does not trigger another Policy when it is run in the Policy Testing Console. If the Trigger Policy is set with Wait for completion, then the Trigger Policy object will fail in the test console.
Custom Start object – if this object requires parameters, you must specify those parameters manually to run the Policy in the Policy Testing Console.
Satellite licenses – the Policy Testing Console does not verify Satellite license usage. The Policy may succeed in the Policy Testing Console, however, it may fail in the Client if the Client finds that all Satellite licenses have been used by other Policies.
Log entries for Policies that use Wait objects – the order of execution that appears in the log of the Policy Testing Console may not appear in the same order as the objects in the Policy.
Long Published Data items – if a Published Data item is too long, the full text may not be visible in the log of the Policy Testing Console. Even though the full text may not appear in the log, the Policy Testing Console has not trimmed the text.
Counters – when you run a Policy that uses Counters in the Policy Testing Console, the Policy Testing Console uses the current counter values that appear in the Client. When the Policy has finished running in the Policy Testing Console, the Counter values are not saved into the Datastore and the original Counters are unaffected by the simulation. The Resource Browser pane of the Policy Testing Console displays the default Counter value and not the value based on running the Policy.
Send Platform Event object – the object will execute in the Policy Testing Console, but it will not write an event in the event log.
Schedules – the Policy Testing Console does not display Schedule details.
The following Client functionality is not available in the Policy Testing Console:
Monitor Counter objects you cannot run Policies that use the Monitor Counter object in the Policy Testing Console. Instead, test the Policy using a Get Counter Value object.
Multiple monitor objects you cannot run Policies that start with multiple monitor objects in the Policy Testing Console. Instead, run the Policy with only one monitor by disabling one of the monitors.
Link properties – you cannot view or configure Link properties when a Policy is loaded in the Policy Testing Console.
Expand option for text fields – you cannot expand text fields when a Policy is loaded in the Policy Testing Console.
Security Credentials tab – the Security Credentials tab does not appear for any object when a Policy is loaded in the Policy Testing Console.
Alternate object icon – if an object used an alternate icon in the Client, that icon will not appear when the Policy is loaded in the Policy Testing Console. Instead, the default icon appears.
Policy Properties – the Policy Testing Console ignores any scheduling or Published Data logging options that you have select on the Policy’s Properties dialog.
Computer Groups – Computer Groups are not supported in the Policy Testing Console. Instead, test the Policy using static IP addresses. The Policy Testing Console does not display the contents of a Computer Group.

Previous Next