Brief summary of the bug. What is it ? Where is it ?

If a default tenant is specified for a connected engine, the import pipelines save the default tenant on the process instance document but don't use this value when storing the tenant ID on the nested document, instead writing a null value. This means that report evaluations using these properties will fail when specifying the default tenant. In 3.5 and earlier, we didn't store this value on the nested document, so this is a new regression.

This affects Branch Analysis reports, user task reports, and flow node reports. We may also have this issue with incident reports too, as those nested documents store the tenant ID too.

Steps to reproduce:

Specify a default tenant for a connected engine. After an import round, note the default tenant set for the process instance document, but not for the nested documents within that process instance. In Optimize, observe any of the above reports contain no data, despite having the correct instance count

Clearly mention the steps one by one to reproduce the bug. Don’t make generic statements, please be specific in the steps to follow.

1. Specify a default tenant for a connected engine
2. Import data from that connected engine
3. Create a flow node report for the default tenant
4. Observe no data presented in the report

Actual result :

No data shown in the report

Expected result:

Instances with the default tenant are included