Pipelines Connections strings appears only for File Operations
Summary:
Pipelines Connections strings appears only for File Operations and not for other jobs (Example: Metadata exports of remote PODs)
Content (please ensure you mask any confidential information):
We are using pipelines to export multiple PODs Metadata into single POD (epm inbox) to email to users as logging into multiple PODs from Users standpoint is challenging. These jobs work as expected but, in the log, it does not have the connection id strings similar to File Operations and it is being challenging to identify which POD it is sourcing the Metadata from in the job logs. Is there a way to populate connection id strings in these jobs same as File Operations jobs?