About Delete Fakes

#Enterprise This feature will allow you to delete any participant, entity, or POS element with the name of “Fake.”

Updated over a week ago

This feature will allow you to delete any Participant, entity, or POS element with the name of “Fake.” This is a helpful way to delete any “Fake” or “Test” data which may have been used during Implementation/Training or testing. 

To be considered a "Fake" in ETO software:

  • Participants may have the first or last name Fake.

  • Entities must begin with the word Fake - if it is an individual then the first name of the entity must be Fake.

  • POS elements must begin with the word Fake.

Important Notes: 

  • The word the software looks for is “Fake” and only “Fake” – names such as “Fakest,” “Faker,” etc. will not be recognized by this feature as a security measure to ensure that you aren't deleting any real data where "fake" may be included as part of the name.

  • All data associated with the fake Participants, entities, and POS elements will be deleted. This includes any efforts, assessments, TouchPoint responses, workflows, etc. that have been attached to the Participants or entities. 

  • This feature is site specific, so it will need to be performed for each site and cannot be scoped down to program level. 

  • To allow deletion of an entry, you can go to View/Edit Participant, View/Edit Entity, or Manage Point of Service to write over the existing name with the word "Fake" if it was not initially added as a fake entry.

Performance:

Depending on how many Fakes are in the database and how many records (TouchPoint responses, program enrollments, referrals, etc.) are associated with them, Delete Fakes can be a very resource-demanding feature to execute. When deleting more than a few Participants at a time with many dependent records, Bonterra recommends using this feature on off-peak-hours so the process does not slow down your users’ experience in other areas of the software.

Did this answer your question?