I have a group of processes running frequently, and it bloats the process execution table. Is there a way to set default filters to exclude these processes? Or maybe configure the process to just not show altogether?
As far as I know, In process reporting we cannot hide the execution entries. Adam Arrowsmith and other Boomi team could better confoirm this. But I believe there is no way we coulde stop hiding those. We could only filter those using some parameters.
And, could you please try this option?
Link for above is: Purging of Atom,Molecule, or Atom Cloud logs and data
Hi Jonathan Hart,
I believe you're asking about hiding the execution results in process reporting, not the detailed logs mentioned by Michael, correct?
If those frequently running processes are polling for data but not finding anything, you can filter by "Hide Successes with 0 Inbound Documents" and you can certainly filter by including certain processes--although it sounds like in your scenario you to exclude certain processes. I don't think that suggestion has come before but it's an interesting one.
It may not apply to your scenario but listener processes configured to execute in Low Latency mode do not show in the results. Interesting suggestion about explicitly configuring a process to NOT show in Process Reporting, unless it has data and/or an error I imagine?
I am mitigating a functional gap in the Boomi Package/Deployments UI. I have to manage staying in sync with a complex C.I. architecture. Prod gets pulled down to sandbox for hotfixing, Beta is a second STG environment for a different department.
I have well over 100 processes which have to follow along with app versions being promoted through the CI chain. It becomes very difficult to track packages across all these environments. So I ate a bag of coffee beans and plowed through the night, developing a system of processes and databases to track packages and deployed components through all the environments, and explicitly issue a command to deploy a package version on one environment to another environment.
We have applications which integrate with Boomi Web Services to send data to partners, so process reporting starts filling up as other departments start using these apps. I am in no way a fan of including integrations into the UX behind the scenes, but, in this case it is required. So yeah, mouse clicks in a web app will fire off various processes, and we've got tons of them.
Between PROD users, two rooms of testers, QA, and me, process reporting stays filled up, and some of these executions I just don't care about - they're for me and my world.
Being able to save default filters / favorite filters would be huge.
As Adam already suggested, we use low latency for any web service or listener process. Regarding the last, you can run these in low latency mode too. You then see only scheduled processes on the process management page. In our case, I think that saves 90% of all the processes execution logs we run for our avg customer.
Btw: you said
I am mitigating a functional gap in the Boomi Package/Deployments UI. I have to manage staying in sync with a complex C.I. architecture.
Are you referring to the new deployment workflow, which currently is in beta? If so, check out this idea: Improvements for deployment workflow
Retrieving data ...