Changes

Andrew,

As an organization that quarterly is required to update the addresses in its database for NCOA (National Change of Address) reasons, we would like to be able to audit system level changes made to a constituents information and represent it in a way that is understandable by front line staff working with customers directly.

As an organization that keeps audit information staff authorized to make changes to constituent information should be authorized on an account by account basis to roll back changes represented in an audit history.

As a front line user of Tessitura looking at audit history, I should find a representation of the audit history in a clear and easy to understand format that directly reflects the fields and screens I see on the screen.  (Not in a way, that only a programmer or database manager would love.)

As a customer on the website as I change my own information, it should be reflected in the audit history so that the organization that uses Tessitura to manage our relationship knows that it is really me who said that, I’m divorced, even though my old partner is still in denial and trying to change it back all of the time.

As a user of Tessitura I would like to be able to see changes to constituents reflected in Tessitura in the same way I see changes in Adobe Photoshop or other applications.  I want to be able to review and roll back my customers histories on an object by object or entire customer history bases.

--Tom

            Hi all,

Today we are asking about tracking constituent information changes in your business.  If a constituent’s information is changed in any way in the system, what do you need to know about the change?  What are some stories from your business (current and future) where you need to know about additions, removals or changes to constituent information? 

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Andrew,

As an organization that quarterly is required to update the addresses in its database for NCOA (National Change of Address) reasons, we would like to be able to audit system level changes made to a constituents information and represent it in a way that is understandable by front line staff working with customers directly.

As an organization that keeps audit information staff authorized to make changes to constituent information should be authorized on an account by account basis to roll back changes represented in an audit history.

As a front line user of Tessitura looking at audit history, I should find a representation of the audit history in a clear and easy to understand format that directly reflects the fields and screens I see on the screen.  (Not in a way, that only a programmer or database manager would love.)

As a customer on the website as I change my own information, it should be reflected in the audit history so that the organization that uses Tessitura to manage our relationship knows that it is really me who said that, I’m divorced, even though my old partner is still in denial and trying to change it back all of the time.

As a user of Tessitura I would like to be able to see changes to constituents reflected in Tessitura in the same way I see changes in Adobe Photoshop or other applications.  I want to be able to review and roll back my customers histories on an object by object or entire customer history bases.

--Tom

            Hi all,

Today we are asking about tracking constituent information changes in your business.  If a constituent’s information is changed in any way in the system, what do you need to know about the change?  What are some stories from your business (current and future) where you need to know about additions, removals or changes to constituent information? 

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!