Delete Business Process Template bizproc.workflow.template.delete
Scope:
bizprocWho can execute the method: administrator
This method deletes a business process template.
It allows you to remove templates that were created using the method bizproc.workflow.template.add. These templates are tied to the application and can only be deleted in the context of the same application in which they were created.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
ID* |
Identifier of the business process template |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":525,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/bizproc.workflow.template.delete
try
{
const response = await $b24.callMethod(
'bizproc.workflow.template.delete',
{
ID: 525
}
);
const result = response.getData().result;
if(result.error())
alert("Error: " + result.error());
else
console.log(result);
}
catch( error )
{
console.error('Error:', error);
}
try {
$templateId = 123; // Replace with the actual template ID you want to delete
$result = $serviceBuilder
->getBizProcScope()
->template()
->delete($templateId);
if ($result->isSuccess()) {
print("Template with ID {$templateId} deleted successfully.\n");
} else {
print("Failed to delete template with ID {$templateId}.\n");
}
} catch (\Throwable $e) {
print("An error occurred: " . $e->getMessage() . "\n");
}
BX24.callMethod(
'bizproc.workflow.template.delete',
{
ID: 525
},
function(result)
{
if(result.error())
alert("Error: " + result.error());
else
console.log(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'bizproc.workflow.template.delete',
[
'ID' => 525
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": null,
"time": {
"start": 1737536737.1245451,
"finish": 1737536737.3437879,
"duration": 0.21924281120300293,
"processing": 0.18391799926757812,
"date_start": "2025-01-22T12:05:37+02:00",
"date_finish": "2025-01-22T12:05:37+02:00",
"operating_reset_at": 1737537337,
"operating": 0.18389892578125
}
}
Returned Data
|
Name |
Description |
|
result |
Returns |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "ERROR_TEMPLATE_NOT_FOUND",
"error_description": "Workflow template not found."
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Error Message |
Description |
|
|
Application context required |
Access token not from the application |
|
|
Access denied! |
Method was not executed by an administrator |
|
|
Workflow template not found. |
Template with the specified |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Business Process Templates: Overview of Methods
- Add Business Process Template bizproc.workflow.template.add
- Update Business Process Template bizproc.workflow.template.update
- Get the list of templates bizproc.workflow.template.list