francescoingv
francescoingv
In **API.execute_process()**, the (optional) parameter '**outputs**', if present in the request, is not passed on to **BaseManager.execute_process()** (or derived). Even more, the parameter '**outputs**' is not collected: only the parameter...
**The documentation for the output parameter of `BaseProcessor.execute()` is not sufficient** The standard allows for several output types, e.g. `string`, `integer`, `object`, `array`, `binary`, etc, as well as `multiple outputs`....
**Description** Using the `BaseManager` as manager, while it is safe to not define the configuration parameter `output_dir`, it causes an error if it is not defined the configuration parameter `connection`....
**I find it difficult to check if the `processor` returns an output correctly formatted.** Currently only examples with **single output** of type **object** and mimetype **application/json** are available: `HelloWorldProcessor` `echoProcessor`...
# Overview Allows the request parameter `outputs` to be passed on to the Processor. The parameter `outputs` is passed to the Manager, which in turn pass it to the Processor,...
**Description** Issuing a synchronous execution request, specifying the response to be 'document', returns a (JSON) string that is different from what is returned when retrieving the 'job-results' **Steps to Reproduce**...
# Overview BaseProcessor works also without configuration parameter `connection`. Methods `add_job()` and `update_job()` are now called subject to the condition the configuration parameter `connection` is provided. Additional minor changes: -)...
**Is your feature request related to a problem? Please describe.** I would like to store the job data in a PostgreSql DB **Describe the solution you'd like** I developed a...
**Is your feature request related to a problem? Please describe.** Currently the information `outputTransmission` returned by the process description (entry point `processes/[process-id]`) does not account for the information provided by...