Getting Started

Confluence Extension Points

NB - needs review

The Escalation Service allows you to define a process for modifying content after a certain amount of time has elapsed.

You can configure a job to run in the same way you can configure Scheduled Jobs.

The minimum interval between code executions is 1 hour. The scheduler is triggered every hour and gathers all the tasks to be executed within that hour. The task executions are queued and workers will consume them in no predefined order. That means that the execution time of the task can not be guaranteed to be the same every hour. As an example: if you configure a job to be run every hour, it might be run at 01:02 and then 02:24 and then 03:00 and then at 04:46 etc depending on how busy our systems are.

Each defined job must have a CQL query that will be run in order to find the content that you wish to modify. The code you provide as part of the job configuration will be run against each piece of content individually, and in parallel. Each content will be injected into your code as part of the Script Context.

The maximum amount of content you can modify in any execution of an Escalation Service job is 50.

In other words, we limit the amount of content returned by each CQL query to 50 items.

The schedule editor dialog lets you choose between running your script on several days during the week (e.g. Monday, Wednesday, Friday), or running your script on particular days of the month (e.g. the last day of the month, the 2nd Tuesday of the month). Additionally you can select an hour interval during which your script will be run.

Each Escalation Service job can execute for the same length of time as Script Listeners, Post Functions and in the Script Console as documented here.

There is a possibility to test your script using "Run Now" button that will execute the CQL and perform the script. The results of the run and logs are displayed per each content.