Procare Solutions Internal Ideas Portal
Myprocare registrations are stored in 'packages' that can be imported from the Procare client. The relevant packages for an IKN are stored within the databae for that IKN. Currently, once a package is deleted, it is removed from the Procare_IKN database and is irrecoverable. This action is also not recorded anywhere in internal or external logging, so investigation into why a package is removed is not possible.
Ideally, the following enhancements could be made to the Myprocare deletion process:
1. Deleted packages should be able to be restored in case they are deleted in error. Either a "isDeleted" flag on the PP_ModerationPackage table, or a new table to move deleted packages to that could be restored from within the Procare Client.
2. A user deleting a package should be recorded in G_EventLog with the date/time of the action, the ProcareUserID of the user that deleted it (including sys if applicable), and the AccountKey or Child Names of the deleted packages.
3. If possible, deleting a package should generate a log that can be quereied in New Relic. Although this is the lowest priority of the request.
| Product Area | Center Management |
| Are customers at risk of leaving Procare without this item? | No |
| Are customers going to competitors for this item? | No |
|
How does this impact the customer's business?
This request was inspired by a recent event where all registration packages were deleted from the database. This was almost certainly caused by a Procare User removing the packages in bulk manually. However, as we cannot prove or verify this, the center is blaming Procare for this being a bug and due to the unfortunate timing, the deleted packages are irrecoverable. |
|
| Requesting Customer | 965-318-6769 |
Hey Zack, this does not happen often - maybe a few times a year. But the latest instance was a school district that pushed back on us not being able to prove it was user error, so it blew up more than usual as they insisted it was a data integrity issue and we had no way of disproving it.
How common is this issue?
Will review with dev team to evaluate the lift.