Resource Allocation

During run-time recipes can be executed by a BPMS which leades to a optimized resource allocation. Rembrandt allows two ways of starting the allocation:

  • Calling the corresponding API route.

  • Clicking the button in the recipe detail view.

The GET request to start the allocation can be called from an arbitrary BPMS at any time. If Rembrandt is used locally with the standard port, the request looks like this:



Started executions can be seen in the frontend within the "Executions" page in the optimization component. In the detail view of a specific execution ingredients and their current state are displayed, which enables better monitoring and debugging of the resource allocation process. If an execution is no longer relevant, it can be deleted to maintain clarity. This, however, does not stop the allocation process in the backend, but only deletes the visible front end records.