Jenefer-Monroe
commented
1 year ago Oh yes you're right we don't clean up that property for apps / flows that dont meet the criteria . Adding this to the requirements list for the rewrite of the feature area.
Does this bug already exist in our backlog?
Describe the issue
So for example,
We changed the amount of time when an app or flow is considered to be inactive. From 90 days to 360 days however, the app still shows in the Clean up Objects App even though it doesn't meet the criteria anymore. Also, I noticed if someone modifies or launches the app as well it still also shows in the Clean up Objects app for something that is requested even though there is no record anymore in the App and Flow Inactivity Notifications app.
Is it possible that something needs to be resolved in one of the flows so that this Clean Up Objects app shows what should be there. I think the ignored since date seems to be stuck once it has been requested even if the process has changed against who should get an inactivity notification.
Expected Behavior
No response
What solution are you experiencing the issue with?
Governance
What solution version are you using?
3.11
What app or flow are you having the issue with?
Admin | Inactivity notifications v2 (Start Approval for Apps) and Flows and possibly the Admin | Inactivity notifications v2 (Clean Up and Delete)
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
you can just modify an app that has been requested to approve or reject inactivity. or you can change the inactivity this variable: InactivityNotifications-PastTime-Interval from 3 months to 6 months. Have an app that was edited at leat less then 6 months
The apps will still show in the Clean up Objects App and if you try to clean it up using the app it just removes your approval or rejection but the ignored date still shows.
Anything else?
No response
AB#1578