Gold SLA

DecisionRules offers different types of SLA. Community Support, Silver SLA, Gold SLA, and in case we are not matching your expectations, there is also the possibility of the Custom SLA

Last updated 7 months ago

SLA

In the table below is described SLA for Large Cloud. Each issue has different severity, this is why there is a difference in response and resolution time. We are here for you in our business hours between 8am and 6pm CET.

Severity

Response

Resolution

Critical (priority 1)

is a failure that results in a complete crash of the application, ie. a malfunction of the application as a whole or its module, which does not allow users to work or communicate with the application.
Examples of Critical failure:
1. The application does not allow the user to log in (except for the incorrect DB function).
2. The solver does not return the required (correct) results.
3. Incorrect CRUD functionality of the space.
4. Incorrect CRUD functionality of the rules.

High (priority 2)

is a fault that results in the malfunction of any of the functions declared in the manual available at Dashboard and causes restrictions on the operation and services of the application, but does not prevent the use of the application as a whole; the failure could affect the accuracy of existing or acquired data and calculations performed.
Example of High failure:
1. Non-functional import and export of rules to XLSX and JSON format.
2. The application does not allow new users to be registered (except for the incorrect DB function).
3. The application cannot create new API keys and API calls only work from existing ones.

Medium (priority 3)

is a failure that results in a violation of any of the functions declared in the manual available at Docs, but does not cause a restriction on the operation and services of the application; the failure could affect the accuracy of existing or acquired data and calculations performed.
Examples of Medium failure:
1. Viewing the history of rules does not respond.
2. Rule duplication does not work.
3. Creating new versions of a rule does not work.
4. Inability to invite new members to the CRUD space.
5. The dashboard cannot preview graphs.

Low (priority 4)

are faults that do not limit the functionality of the application and do not prevent the operation of the application as a whole or any of its parts, but they are not the documented state of the application.
Examples of low failure:
1. Faults exclusively on the front-end = changes and fixes are displayed after the update (refresh).
2. Autocomplete failure in scripting rules.
3. Color separation and autocomplete functions in the decision table do not work.

The list of examples is only for better orientation of what belongs to which category.

SLA

Severity

Response

Resolution

Critical (priority 1)

is a failure that results in a complete crash of the application, ie. a malfunction of the application as a whole or its module, which does not allow users to work or communicate with the application.
Examples of Critical failure:
1. The application does not allow the user to log in (except for the incorrect DB function).
2. The solver does not return the required (correct) results.
3. Incorrect CRUD functionality of the space.
4. Incorrect CRUD functionality of the rules.

High (priority 2)

is a fault that results in the malfunction of any of the functions declared in the manual available at Dashboard and causes restrictions on the operation and services of the application, but does not prevent the use of the application as a whole; the failure could affect the accuracy of existing or acquired data and calculations performed.
Example of High failure:
1. Non-functional import and export of rules to XLSX and JSON format.
2. The application does not allow new users to be registered (except for the incorrect DB function).
3. The application cannot create new API keys and API calls only work from existing ones.

Medium (priority 3)

is a failure that results in a violation of any of the functions declared in the manual available at Docs, but does not cause a restriction on the operation and services of the application; the failure could affect the accuracy of existing or acquired data and calculations performed.
Examples of Medium failure:
1. Viewing the history of rules does not respond.
2. Rule duplication does not work.
3. Creating new versions of a rule does not work.
4. Inability to invite new members to the CRUD space.
5. The dashboard cannot preview graphs.

Low (priority 4)

are faults that do not limit the functionality of the application and do not prevent the operation of the application as a whole or any of its parts, but they are not the documented state of the application.
Examples of low failure:
1. Faults exclusively on the front-end = changes and fixes are displayed after the update (refresh).
2. Autocomplete failure in scripting rules.
3. Color separation and autocomplete functions in the decision table do not work.

The list of examples is only for better orientation of what belongs to which category.