Ideas

Person History needs a "Who" for system actions

17

Login To Vote

Person History needs a "Who" for system actions

CRM

When trying to investigate data issues, it can be hard to be sure where or how a person got created or modified if the History entry isn't attributed to a specific person.

I would love for there to be way to see that a History entry is related to a Workflow/API Call/Plugin/etc., even if I can't see the full detail.

For example, we use PushPay as our Giver system and it will create new people if there is no match for them, but looking at the history I have no way to distinguish that from many other ways a person is created. I can only make assumptions, and that isn't confidence inspiring.

Photo of Miles CarmanySubmitted by Miles Carmany, Northside Christian Church  ·   ·  CRM
Remove Votes
Login to add a comment...

Submission Success Tips

Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.

  • Clear Title: Craft a straightforward and descriptive title that instantly conveys the essence of your idea.
  • Concise Description: Provide an idea description that is succinct, ensuring it effectively communicates the concept without unnecessary verbosity.
  • Provide Additional Details: With a concise description complete, now provide any other details that are needed to better understand the requirements.
  • Thorough Ministry Need Review: Provide a comprehensive overview of the ministry need your idea addresses, emphasizing its significance.
  • Cover the WHY: Clearly articulate the rationale behind your idea, explaining why it's essential and how it aligns with the organization's goals and mission. Oftentimes a clear "why" sheds light into other possible options.