Page History

Cancel all started tasks

Description

By calling this endpoint, all the started tasks across all nodes will be reopen. Automatic tasks will also be executed.

Setting the property blueriq.processengine.cancel-started-tasks to true when running in a multi-node environment might cause problems because while the cancellation of started tasks triggered on one node is running, a specific task could be still in progress on another node and it might be reopen.

Cancel all started tasks endpoint was created in order to avoid these types of situations.

Usage

The following steps should be followed for using this endpoint:

1. Make sure that there exists a runtime user with a role that has the permission SCHEDULER_MANAGER.
2. Check that blueriq.oauth2.client-id and blueriq.oauth2.secret are defined in application.properties file. If they are missing, please define them.

3. Access Runtime Swagger Interface: 

   Info
   icon false
   http://<server>:<port>/<runtime>/api/v1/docs/index.html

4. Fill the username and the password and press Generate Token in order to obtain a new token.
5. Expand scheduler.
6. Expand PUT /scheduler/maintenance/tasks/cancelStarted.
7. Press Try it out!

Update Application Name And Version

Description

By calling this endpointone of these endpoints, the application name, application version or both application name and version id will be updated for the cases and jobs matching the specified criteria.

Steps:

1. Find all cases where

1. application id

1. contains the old application name. If old application version is specified in the

1. url, find all cases where application id matches with the name and version.
2. Update application id for these cases with the new data sent in the request body.
   
   

Request examples:

1. Update application name.

   1.1 Update application name on every version of your old application.
   All cases where application name is "export-TestOldProject" are updated to "export-TestNewProject". 

   Info
   icon false
   PUT http://<server>:<port>/<runtime_name>/api/v1/scheduler/maintenance/applications/export-TestOldProject { "name" : "export-TestNewProject" }

   Note
   title Note
   If you do not specify the old application version in the url, this endpoint will update the application name for every version of the specified old application. If you would like to update the application name only for a specific version, you should use the endpoints below.

   1.2. Update application name for a specific version

1. Update application name.
   All cases where application name is "export-TestOldProject" , is and version is "0.0-Trunk" are updated to "export-TestNewProject". Version remains the same. 

   Info
   icon false
   PUT http://<server>:<port>/<runtime_name>/api/v1/scheduler/maintenance/applications/export-TestOldProject/0.0-Trunk { "name" : "export-TestNewProject" }

2. Update application version.
   All cases where application name is "export-TestOldProject" and version is "0.0-Trunk", version is updated to "0.1-Trunk". Application name remains the same.

   Info
   icon false
   PUT http://<server>:<port>/<runtime_name>/api/v1/scheduler/maintenance/applications/export-TestOldProject/0.0-Trunk { "version" : "0.1-Trunk" }

3. Update application id (both name and version)
   All cases where application name is "export-TestOldProject" and version is "0.0-Trunk", application name is updated to "export-TestNewProject" and version is updated to "0.1-Trunk".

   Info
   icon false
   PUT http://<server>:<port>/<runtime_name>/api/v1/scheduler/maintenance/applications/export-TestOldProject/0.0-Trunk { "name" : "export-TestNewProject", "version" : "0.1-Trunk" }

Usage

The following steps should be followed for using this endpoint:

1. Make sure that there exists a runtime user with a role that has the permission SCHEDULER_MANAGER.
2. Check that blueriq.oauth2.client-id and blueriq.oauth2.secret are defined in application.properties file. If they are missing, please define them.

3. Access Runtime Swagger Interface: 

   Info
   icon false
   http://<server>:<port>/<runtime>/api/v1/docs/index.html

4. Fill the username and the password and press Generate Token in order to obtain a new token.
5. Expand scheduler.
6. Expand PUT /scheduler/maintenance/applications/{oldApplicationName} or PUT /scheduler/maintenance/applications/{oldApplicationName}/{oldApplicationVersion}.
7. Specify the old application name you would like to update. Optionally specify the application version.
8. Specify the body of the request with the new application name, or new application version or both.
9. Press Try it out!

Update

Application Name and Version for a Case

Description

By calling this endpoint, the jobs for a specific case only one case and it's jobs will be updated with the new process engine idinformation.

StepsThis functionality does the following:

1. Finds the task case with the specified task case id. Takes the case from the task. 
2. Update the application id for the case found.  Application id is updated with the new application name sent in the request body. Optionally, if specified in the body, application version will be updated as well.
3. Calls the scheduler to find all jobs for that specific the case from step 1.
4. Updates all the jobs with the new process engine id, taken from the case model (found in step 2)application id.

Usage

The following steps should be followed for using this endpoint:

1. Make sure that there exists a runtime user with a role that has the permission SCHEDULER_MANAGER.
2. Check that blueriq.oauth2.client-id and blueriq.oauth2.secret are defined in application.properties file. If they are missing, please define them.

3. Access Runtime Swagger Interface: 

   Info
   icon false
   http://<server>:<port>/<runtime>/api/v1/docs/index.html

4. Fill the username and the password and press Generate Token in order to obtain a new token.
5. Expand scheduler.
6. Expand PUT /scheduler/maintenance/applications/jobscases/{taskIdcaseId}.
7. Specify the task case id.
8. Press Try it out!