Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.
Difference between revisions of "Data Lock"
Lsilverman (talk | contribs) |
Lsilverman (talk | contribs) |
||
| Line 4: | Line 4: | ||
The main reason to start using the data lock feature is to prevent users from making changes to old or verified records that might have an impact on customer balances after those customers have been billed. Another reason to use data lock is to simply protect the integrity of the long history of data you’ve worked so hard to accumulate. | The main reason to start using the data lock feature is to prevent users from making changes to old or verified records that might have an impact on customer balances after those customers have been billed. Another reason to use data lock is to simply protect the integrity of the long history of data you’ve worked so hard to accumulate. | ||
| − | |||
| − | |||
<jwplayer width="800" height="600" autostart="true">DataLock.flv</jwplayer> | <jwplayer width="800" height="600" autostart="true">DataLock.flv</jwplayer> | ||
Revision as of 18:14, 21 January 2009
This video introduces the concept and feature of Data Lock. Data Lock is a feature that is designed to protect existing records in TrackAbout from unwanted changes. Without a data lock in place, any user with sufficient privileges can edit or make changes to any record in the system, no matter how old.
When you set a data lock, you are setting a date. With a data lock in place, users will no longer be able to make changes to records whose dates are older than the data lock’s date.
The main reason to start using the data lock feature is to prevent users from making changes to old or verified records that might have an impact on customer balances after those customers have been billed. Another reason to use data lock is to simply protect the integrity of the long history of data you’ve worked so hard to accumulate.