Hi,

Very close, but it should be ...shipment_id={shipment_id}… 

This way {shipment_id} will be replaced by the process variable value 

Like this:

{shipment_id={shipment_id}} or (shipment_id={shipment_id})

?

Like (shipment_id={shipment_id}) I think

It didn't work. I even tried with fixed parameter value.
 

Below is the task that precedes the HTTP Connector

Hi,

Are you sending this request to Indicium or Indicium Basic? I'm also not sure if using "[local-host]” in the HTTP connector works. You can double check by opening the Process flow monitor if you are using the Windows GUI, otherwise you may need to inspect the Indicium log to find out why the request failed.

Besides that, if you are trying to run this Report from a row, the value inside the ( ) should be the PK value of the row you would like to start the Report on: (docs)

Lastly, we added a new process action called Generate report in 2022.1, can that process action help out?

Sending requests to Indicium from within HTTP connectors is not feasible in the long run as Indicium may be renamed, may be placed elsewhere, report may be renamed, and your gui_appl_id changing over time.

The user running the process flow (ie the pooluser of indicium) should be active in the SF for the runtime config for application 984.
Like Mark said, this is not a desired solution for the long run, for testing purposes its fine.

Furthermore; are there any errors in the error_log of indicium? 
(You can find the error_log by logging in on indicium as an admin)

Hi Mark,

I tried to use the generate report process action previously. It runs the process action but returns null in the report data output.

 

The following task has to receive the report data:

 

But it fails because content is null.

From which GUI are you trying that process action?

The generate report process action only works on indicum, so coming from Universal GUI or as a system flow it works, coming from Windows / Web GUI it will fail.

Hi Robbert,

I'm using Windows GUI. In that case what's the best approach? HTTP connector?

Yes, a HTTP connector would be a good way to go. For an example see this topic:

Another way could be → Task → Queue table
    system flow → Check queue table → generate report

Depending if the user should see the document imidiatly or if it could be done asynchronous.

Hi Robbert,

I'm getting -4 status with the HTTP Connector. See below:
 

You have invalid headers.

https://docs.thinkwisesoftware.com/docs/sf/process_flows_connectors#http-connector

Your header should be something in line with this:

> { "Key": "Header1", "Value": "Value1" }, { "Key": "Header2", "Value": "Value2" } ]