Hello,
I'm currently working with a scripted approach to identification of transactions that require PII removal per our business rules and I have that all working great to identify and create tasks. However, the performance of the tool is very slow… This is primarily due to heavy customization on our Sales Orders, Item Fulfillment, and Invoice records.
I have a few questions and I'm hoping someone else may have already ran into this and found a solution.
1) Does the PI Removal tasks impact the system and use up governance cycles? i.e. is it going to affect any of our other automations and scheduled scripts and workflows?
I ask because we're going to be running this to clean up one day of transactions at a time that have past the 31 day retention provided it's in a state that meets the business rules… I've done some performance testing in our sandbox which is not ideal since it's not competing with other tasks/scripts/schedules… and it took roughly 6 hours 40 minutes to complete 2500 sales orders with their related item fulfillment and invoice… (7500 total records)… This was a light test as we have sales reaching 10,000 orders/day at times and we expect growth… as such, we'd be looking at 24+ hours in the best case if the PI Tool is not competing for process power…
2) Is there some way to identify when the PI Removal tool is running on a transaction… If I could identify this I would be able to account for this with at least the scripts running on the affected transaction and prevent them from running. I've done this with our "cleanup" script that will be directly editing the transactions then creating the much lighter cleanup of the history (system information) notes… but, since we will have to open periods for this and to be sustainable and automated going forward we need to use the native tool. It appears to be operating in the XEDIT context… but this is not enough to target that the PI tool is what's acting on the transaction.
3) Given the above performance concerns and need to identify this, what are the chances that the Personal Information Removal tool could be made to have a new, unique, context type or at least something that would identify it in the context of scripts allowing us to prevent certain scripts from firing…
Alternatively, if it could be updated to allow, via a configuration option when creating tasks, to -not- trigger events on transactions…
Any help or guidance on how I could make this work for us will be greatly appreciated as this is becoming a larger issue daily for us and we need to get it under control…