Data Lock - Revision history

Jgreco: Initial proofread pass - docs

2021-11-29T18:51:50Z

Initial proofread pass - docs

Lstrydom at 04:33, 16 December 2020

2020-12-16T04:33:52Z

Tdames at 14:35, 18 October 2018

2018-10-18T14:35:39Z

Eschurdak at 14:29, 28 April 2017

2017-04-28T14:29:12Z

Jwolbert at 14:37, 21 June 2016

2016-06-21T14:37:05Z

Admin: Reverted edits by Admin (Talk) to last revision by Lsilverman

2009-08-20T17:29:29Z

Reverted edits by Admin (Talk) to last revision by Lsilverman

Admin at 17:27, 20 August 2009

2009-08-20T17:27:56Z

Lsilverman at 22:14, 21 January 2009

2009-01-21T22:14:29Z

Lsilverman at 22:14, 21 January 2009

2009-01-21T22:14:08Z

Lsilverman at 22:06, 21 January 2009

2009-01-21T22:06:03Z

@@ Line 1: / Line 1: @@
 {{TrackAbout Feature
 |Parent Module=Core Tracking
-|Feature Description=Data Lock is a feature that is designed to protect existing records in TrackAbout from unwanted changes.
+|Feature Description=Data Lock is designed to protect existing records in TrackAbout from unwanted changes.
 }}
-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.
+Data Lock 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.
+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.
+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.

← Older revision		Revision as of 04:33, 16 December 2020
Line 8:		Line 8:

	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.
		+
		+	Herewith the link to the AWS page for setting.
		+
		+	https://www.trackabout.com/clt/recordadmin/setDataLock.aspx

@@ Line 3: / Line 3: @@
 |Feature Description=Data Lock is a feature that is designed to protect existing records in TrackAbout from unwanted changes.
 }}
-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.
+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.

@@ Line 1: / Line 1: @@
 {{TrackAbout Feature
 |Feature Description=Data Lock is a feature that is designed to protect existing records in TrackAbout from unwanted changes.
 }}

← Older revision		Revision as of 14:37, 21 June 2016
Line 1:		Line 1:
		+	{{TrackAbout Feature
		+	\|Feature Description=Data Lock is a feature that is designed to protect existing records in TrackAbout from unwanted changes.
		+	}}
	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.		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.

← Older revision		Revision as of 17:29, 20 August 2009
Line 1:		Line 1:
−	This video ~~demonstrates recent changes made to~~ the ~~following aspects~~ of ~~the~~ TrackAbout ~~web site~~ user ~~interface:~~	+	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.
−	* My Preferences settings
−	* Quick Search menu block
−	* Hot Keys for accessing Quick Search items
−	* The new Jump To Page feature
−	* The new left navigation style

−	<jwplayer>~~NavigationDemo~~.flv</jwplayer>	+	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.
		+
		+	<jwplayer width="800" height="600">DataLock.flv</jwplayer>

← Older revision		Revision as of 17:27, 20 August 2009
Line 1:		Line 1:
−	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.~~	+	This video demonstrates recent changes made to the following aspects of the TrackAbout web site user interface:
		+	* My Preferences settings
		+	* Quick Search menu block
		+	* Hot Keys for accessing Quick Search items
		+	* The new Jump To Page feature
		+	* The new left navigation style

−	~~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.~~	+	<jwplayer>NavigationDemo.flv</jwplayer>
−
−	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"~~>~~DataLock~~.flv</jwplayer>

← Older revision		Revision as of 22:14, 21 January 2009
Line 5:		Line 5:
	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">DataLock.flv</jwplayer>

← Older revision		Revision as of 22:14, 21 January 2009
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.
−
−	~~Test~~

	<jwplayer width="800" height="600" autostart="true">DataLock.flv</jwplayer>		<jwplayer width="800" height="600" autostart="true">DataLock.flv</jwplayer>

← Older revision		Revision as of 22:06, 21 January 2009
Line 5:		Line 5:
	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.

		+	Test

	<jwplayer width="800" height="600" autostart="true">DataLock.flv</jwplayer>		<jwplayer width="800" height="600" autostart="true">DataLock.flv</jwplayer>