50
Hi Team,
This idea has 2 major origins.
1. For auditing purposes we need to know who has done what and when on our environments.
This list is part of one of our auditors requests.
2. We are now live since July 2019 and have suffered a lot (we have opened more than 50 Critsits tickets since go-live.) and we want to see how many times we were forced to kill things (End-SQL-PID function).
To show our partners - Integrator and client how many time we have spent in babysitting the machine the past months.
I already opened an SR 120020521001407 around this topic.
I think this should not be a big change and could easily give clients the ability to do some analysis around the activities they spend around the D365FO platforms they have.
This idea has 2 major origins.
1. For auditing purposes we need to know who has done what and when on our environments.
This list is part of one of our auditors requests.
2. We are now live since July 2019 and have suffered a lot (we have opened more than 50 Critsits tickets since go-live.) and we want to see how many times we were forced to kill things (End-SQL-PID function).
To show our partners - Integrator and client how many time we have spent in babysitting the machine the past months.
I already opened an SR 120020521001407 around this topic.
I think this should not be a big change and could easily give clients the ability to do some analysis around the activities they spend around the D365FO platforms they have.
STATUS DETAILS
Needs Votes