Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Tracing active link, filter, or escalation activity
You can create a log file of active links, filters, or escalation activity for each operation, including what activity or workflow was run and whether the event was successful. Filters and escalations are run on the server. For more information, see Setting-log-files-options and Analyzing-logs.
Errors encountered during the escalation activities are recorded in the arerror.log on the AR System server. If an escalation terminates in error consistently, a message is written to the log every time the escalation is run and fails. If the escalation qualification does not select any requests and the alternate actions, if any, are run, a message is written to the escalation log on the server (by default, aresc.log).
Additionally, you can use the AR System Log: Escalation form to record the log entries for escalation.
