Hello,
First of all, we’re running on-prem version of Orchestrator.
We have built a tool for creating reports for our processes once a month. The tool works as expected but we have a problem with scope. We can only see the logs for Processes in the workspace where the tool is run.
We are using the api-method “odata/RobotLogs” with different filters.
We want to publish it in the “Shared” folder and have it reach logs for all Processes.
How is this possible?
Your bot will require View permission on Logs in the folder context to have access to logs generated in that folder.
My admin says I already have that, where can I check this?
I assume you are using the ‘Orchestrator HTTP Request activity’ which will always use the ambient folder if left blank in any requests and resulting in the limits you say.
You either need to loop over each folder and join the logs together or reference the SQL database directly.
Thank you, I just confirmed that this is a case.
Easy to fix as we have a json “jobconfig” for each process that there should be created a report for, I’ll just introduce the foldername of the process in that config.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.