Jenefer-Monroe
commented
5 months ago Thank you for the suggestion. I believe we did already have this in the plans for the rewrite of that feature but will keep this one anyway thanks to all your detailed notes.
ClaudioRWS
Does this question already exist in our backlog?
What is your question?
Hello!
I want to leave here my suggestion about the flow of orphans.
I have unique DEV/QA/UAT/PROD environments, with QA/UAT/PROD all components, flows and applications are taken over by the service account used in ALM.
The DEV environment, like other companies, hires temporary developers to work on creating the solution, and it is normal for everyone to be orphaned in the future. The support team is responsible for handling any future issues.
Therefore, it does not make sense to operate these environments to send the environment owner the decision to take control of the components, reassign them, or delete them.
I'll leave the changes I made here
Admin View
Request Orphaned Objects Reassigned (Parent)
and
Request Orphaned Objects Reassigned (Child)
I hope you like the suggestion, it is not a complex update.
obrigado pela atenção!
What solution are you experiencing the issue with?
Governance
What solution version are you using?
3.15
What app or flow are you having the issue with?
Request Orphaned Objects Reassigned (Parent)
What method are you using to get inventory and telemetry?
Cloud flows
AB#2337