We're pleased to announce that we've added Autotask as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

Autotask External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

We're pleased to announce that we've added HaloPSA as an external ticketing system for your CheckCentral notifications! To get started with it, login to your CheckCentral dashboard, then click Notifications > External Ticketing Systems. From there you can add it as a new channel and detailed instructions are in the configuration window.

HaloPSA External Ticketing Configuration

As always, if you have any questions, please feel free to contact us for assistance!

CheckCentral is happy to announce that scheduled reporting is here! You can find this new feature under your Notifications menu then the Reports menu item.

What is Scheduled Reporting?

Scheduled reporting is an exciting new feature that allows you to create automated reports for any of your CheckCentral data. Schedule different types of reports to send the data you need to the people that need it, even people outside of your organization.

Navigating to the Daily Digest.

You can now manage your Daily Digest report and create new reports that your organization needs in this new reports area.

New CheckCentral reports area.

As always, if you run into any trouble at all, please don't hesitate to contact us.

The CheckCentral API provides an endpoint for adding reports programmatically. All of the configuration options are available through the API, detailed below. To add a new report through the API, you will require an API token for your organization with Read/Write access. Organization administrators can create tokens through the API portal on your dashboard.

The endpoint is located at https://api.checkcentral.cc/createReport/?apiToken=APITOKEN where the APITOKEN placeholder is replaced with your valid token. The request must be made with the Content-Type header set to application/json. The body of the request should contain the properties below to configure the new report's settings. Any properties not passed will be set to their default value.

For example, to add a new report you could send the following json in the body of the request:

{
  "name": "Some Report",
  "email": "person@myorg.realdomain",
  "accessLevel": "User",
  "sendWelcomeEmail": true,
  "userGroups": [
    "userGroupID"
  ],
  "notifications": [
    { 
        "type": "failures",
        "services": [
            "sms",
            "push"
        ]
    }
  ]
}

The report data must include a name property as well as any data required to generate the report such as check group IDs or dashboard IDs.

The complete list of possible properties for report creation are as follows:

Report Structure

• Failure or Warning statuses will create new tickets.
• Subsequent Failures or Warnings will update the ticket.
• A return to the Success status will close the ticket.

We're pleased to announce that we've added a number formatting setting. This allows you to change the way numbers are presented in your organization (i.e 10,000.12 or 10 000.12 or 10.000,12 or 10000.12).

Organization Settings

Mattermost Number Formatting Menu

As always, if you have any questions, please feel free to contact us for assistance!