Reporting Server Restrictions
A Universal Controller configured as a Reporting Server has certain restrictions in place. The main purpose of these restrictions is to prevent the modification of replicated records, so that the integrity of the data from the source Controller is preserved. There are also some limits on the functionality of the Reporting Server for some actions which are not relevant for replication. This document explains all such restrictions.
Some restrictions apply to the Controller acting as the Reporting Server, and others apply to the Controller being replicated. To help differentiate between the two types of Controllers, we will refer to the Controller storing replicated data as the "Reporting Server" and the Controller being replicated as the "source Controller".
Replicated Items
Record types that can be replicated include Activity, Agents, Audits, and History.
For information on how to configure replication, see Replication Settings.
Any record that can be replicated has a Replicated field (visible in the Metadata section of the record details), which is automatically set to true when the item is replicated. Although the Replicated field is visible in both the Reporting Server and source Controller, it will only be set to true on records in the Reporting Server.
Updating or deleting replicated items is prohibited on a Reporting Server.
OMS Servers
An OMS Server cannot be defined on a Reporting Server.
Any action that requires communication with an active Agent via OMS therefore cannot be performed.
Commands
Many commands on a Reporting Server are prohibited. If you try to run a command that is not supported, an error message will be logged to the console. For example:
The Universal Controller Node has a reporting license and cannot run command Enable Webhook.
Some commands are supported, but with certain constraints, which are explained in the sections below. For example, launching a task on a Reporting Server is supported, but only if launching a supported Task type.
Tasks
Any Task type can be defined on a Reporting Server, but the Launch command is only supported for Email Tasks.
In effect, you can only run Email Tasks on a Reporting Server, which can be useful for emailing Reports. However, the Reporting Server does not stop you from defining other Task types, so it is still possible to Bundle and Promote Tasks of any type to a Reporting Server.
Task Instances
Since Task Instances can be replicated, there can be instances of any Task type on a Reporting Server. However, you can only update, delete, or run commands on non-replicated Task Instances.
Because Email Tasks are the only Task type you can launch on a Reporting Server, there can only be non-replicated Email Task Instances.
See Manually Running and Controlling Tasks for a list of available Task Instance commands.
Triggers
Any Trigger type can be defined on a Reporting Server. However, the Enable and Trigger Now commands are only supported for the following Trigger types:
Additionally, a supported Trigger type can only launch Tasks of a supported type (Email Tasks). You cannot update an enabled Trigger on a Reporting Server if the update includes adding an unsupported Task type to the Task(s) launched by the Trigger.
Web Services API
Web Service APIs are supported on a Reporting Server if the invoked command is supported. All the restrictions described in the previous sections of this document apply.
For example, you can use the API to create a Task, but not to create an OMS Server.
Data Backup / Purge
If a Reporting Server is configured, and replication is enabled for the type of record being purged (Audit, Activity, or History), the purge operation will not be permitted on the source Controller if the qualifying purge data/time is after the replication Synchronization Watermark date/time.
This restriction only applies to running a purge operation on the source Controller. There are no purge restrictions on the Reporting Server itself.
This constraint can be disabled by setting the Purge Replication Required system property to false.