Release Process - Revision history

Anw: Updated based on version 2.4.4

2018-06-18T16:27:40Z

Updated based on version 2.4.4

← Older revision		Revision as of 18:27, 18 June 2018
Line 243:		Line 243:

	When that is complete, the following SQL can be used to extract the data:		When that is complete, the following SQL can be used to extract the data:
			<pre>
	SELECT		SELECT
	IF(rm.Menu_Flag = 'Y', IF(rm.rule_parent <> 'SY00001', '*', ''), IF(rm.rule_parent <> 'SY00001', '*', '')) AS Point,		IF(rm.Menu_Flag = 'Y', IF(rm.rule_parent <> 'SY00001', '*', ''), IF(rm.rule_parent <> 'SY00001', '*', '')) AS Point,
Line 250:		Line 250:
	Where rm.rule_type = 'SYS' and rm.Rule_Parent <> ''		Where rm.rule_type = 'SYS' and rm.Rule_Parent <> ''
	order by IF(rm.menu_flag = 'Y', rm.rule_name, rm.rule_parent), (rm.menu_flag <> 'Y'), rm.rule_name;		order by IF(rm.menu_flag = 'Y', rm.rule_name, rm.rule_parent), (rm.menu_flag <> 'Y'), rm.rule_name;
			</pre>

	Note that this does not correctly deal with sub-menus, so this will need some slight modification after production.		Note that this does not correctly deal with sub-menus, so this will need some slight modification after production.

Anw: Updated based on version 2.4.4

2018-06-18T16:27:07Z

Updated based on version 2.4.4

← Older revision		Revision as of 18:27, 18 June 2018
Line 246:		Line 246:
	SELECT		SELECT
	IF(rm.Menu_Flag = 'Y', IF(rm.rule_parent <> 'SY00001', '*', ''), IF(rm.rule_parent <> 'SY00001', '*', '')) AS Point,		IF(rm.Menu_Flag = 'Y', IF(rm.rule_parent <> 'SY00001', '*', ''), IF(rm.rule_parent <> 'SY00001', '*', '')) AS Point,
	rm.Rule_Label, ' - ' as delim, rm.Rule_Description		CONCAT('\'\'', rm.Rule_Label, '\'\'') AS Label, ' - ' as delim, rm.Rule_Description
	FROM rules_master rm		FROM rules_master rm
	Where rm.rule_type = 'SYS' and rm.Rule_Parent <> ''		Where rm.rule_type = 'SYS' and rm.Rule_Parent <> ''
Line 254:		Line 254:

	Once complete, this can be pasted into the [[Rules]] screen		Once complete, this can be pasted into the [[Rules]] screen


	=== Self-Documenting Screens ===		=== Self-Documenting Screens ===

Anw: Updated based on version 2.4.4

2018-06-18T16:24:35Z

Updated based on version 2.4.4

← Older revision		Revision as of 18:24, 18 June 2018
Line 265:		Line 265:
	FROM Screens		FROM Screens
	WHERE Screen_Type = 'Summary'		WHERE Screen_Type = 'Summary'
	ORDER BY Screen_Type, Group_Code, ~~Sequence~~;		ORDER BY Screen_Type, Group_Code, Screen_Label;

	Screen_Type can be:		Screen_Type can be:
Line 314:		Line 314:
	\| etc \|\| etc		\| etc \|\| etc
	\|}		\|}

Anw: Updated based on version 2.4.4

2018-06-18T16:21:18Z

Updated based on version 2.4.4

@@ Line 217: / Line 217: @@
 *Start the web server for the Vision application and/or make the system available again (if disabled at the start of the process).
 *Re-enable Data Mining.
 [[Category:Vision Overview]]
 [[Category:Vision Coding and Release Doc|050]]
 [[Category:Vision Coding and Release]]

Anw: Updated instructions from latest install 08/09/2017

2017-09-08T10:40:22Z

Updated instructions from latest install 08/09/2017

← Older revision		Revision as of 12:40, 8 September 2017
Line 198:		Line 198:
	--result-file=VisionDBBackup_YYYYMMDD.sql Productivity1		--result-file=VisionDBBackup_YYYYMMDD.sql Productivity1
	* Move to the {Releases} subfolder. Get the patch and place it in this subfolder - this is usually through FTP, as before.		* Move to the {Releases} subfolder. Get the patch and place it in this subfolder - this is usually through FTP, as before.
	* Extract the patch to a subfolder Releases\{Patch}.		* Extract the patch to a subfolder Releases\{Patch}. {{Note}} Alternatively, if the version of windows allows, explore into the zip file instead of extracting it.
	* Copy the subfolders of {Vision}\Releases\{Patch} to {Vision} - this will copy all of the required programs, scripts and notes into the correct folders. Note: Each program and component may be released separately by manually copying each item, if necessary.		* Copy the subfolders of {Vision}\Releases\{Patch} to {Vision} - this will copy all of the required programs, scripts and notes into the correct folders. Note: Each program and component may be released separately by manually copying each item, if necessary.
	* Move to the {Vision}\Releases folder - the release notes and database update script (if included) will be there.		* Move to the {Vision}\Releases folder - the release notes and database update script (if included) will be there.
Line 205:		Line 205:
	** Click ''File/Open Script...'' and open the script {Vision}\Releases\UPYYMMDD.SQL script file, where YYMMDD is the patch number.		** Click ''File/Open Script...'' and open the script {Vision}\Releases\UPYYMMDD.SQL script file, where YYMMDD is the patch number.
	** Click the '''Continue''' button on the toolbar to make the changes. Note: If there are any problems with the script, the script will pause at the point it failed and display the error. If the error is fixed at this stage and '''Continue''' is pressed again, the script will continue from the point it left off.		** Click the '''Continue''' button on the toolbar to make the changes. Note: If there are any problems with the script, the script will pause at the point it failed and display the error. If the error is fixed at this stage and '''Continue''' is pressed again, the script will continue from the point it left off.
			* Delete the {Vision}\Releases\{Patch} folder - it is no longer required. If space is at a premium, also delete the patch zip file.

	Once the installation steps above have been followed, the patch has been installed.		Once the installation steps above have been followed, the patch has been installed.

Anw at 14:36, 2 August 2013

2013-08-02T14:36:50Z

← Older revision		Revision as of 16:36, 2 August 2013
Line 188:		Line 188:
	Depending on the size and content of the installation, this may take from 15 minutes to an hour.		Depending on the size and content of the installation, this may take from 15 minutes to an hour.

			* Pause any data mining scripts
	Pause any data mining scripts		* Stop the web server for the Vision application.
			* Alternatively, set the system unavailable flag in Global.asa in the Vision folder.
	Stop the web server for the Vision application.		* To install the patch, log on to the Vision server and move to the Vision folder, hereafter referred to as {Vision}.
			* Depending on the complexity of the patch, a backup copy of all the programs and the database should be made, as follows:
	Alternatively, set the system unavailable flag in Global.asa in the Vision folder.		** Backup the {Vision} folder to a safe area in a file called VisionBackup_YYYYMMDD.zip.
			** Backup the current database - Many tools can be used for this, but the best tool would be mysqldump, as follows:
	To install the patch, log on to the Vision server and move to the Vision folder, hereafter referred to as {Vision}.		mysqldump --host={host} --port=5306 --user=root --password={password}
			--result-file=VisionDBBackup_YYYYMMDD.sql Productivity1
	Depending on the complexity of the patch, a backup copy of all the programs and the database should be made, as follows:		* Move to the {Releases} subfolder. Get the patch and place it in this subfolder - this is usually through FTP, as before.
			* Extract the patch to a subfolder Releases\{Patch}.
	~~Copy~~ the {Vision} folder to a safe area.		* Copy the subfolders of {Vision}\Releases\{Patch} to {Vision} - this will copy all of the required programs, scripts and notes into the correct folders. Note: Each program and component may be released separately by manually copying each item, if necessary.
			* Move to the {Vision}\Releases folder - the release notes and database update script (if included) will be there.
	Backup the current database ~~using MySQL Administrator.~~		* To commit the changes to the Vision database:
			** Start the MySQL Query Browser and log on to the Productivity1 database.
			** Click ''File/Open Script...'' and open the script {Vision}\Releases\UPYYMMDD.SQL script file, where YYMMDD is the patch number.
	Move to the {Releases} subfolder. Get the patch and place it in this subfolder - this is usually through FTP, as before.		** Click the '''Continue''' button on the toolbar to make the changes. Note: If there are any problems with the script, the script will pause at the point it failed and display the error. If the error is fixed at this stage and '''Continue''' is pressed again, the script will continue from the point it left off.

	Extract the patch to a subfolder Releases\{Patch}.

	Copy the subfolders of {Vision}\Releases\{Patch} to {Vision} - this will copy all of the required programs, scripts and notes into the correct folders. Note: Each program and component may be released separately by manually copying each item, if necessary.

	Move to the {Vision}\Releases folder - the release notes and database update script (if included) will be there.
	To commit the changes to the Vision database:

	Start the MySQL Query Browser and log on to the Productivity1 database.

	Click "File/Open Script ..." and open the script {Vision}\Releases\UPYYMMDD.SQL script file, where YYMMDD is the patch number.

	Click the Continue button on the toolbar to make the changes. Note: If there are any problems with the script, the script will pause at the point it failed and display the error. If the error is fixed at this stage and Continue is pressed again, the script will continue from the point it left off.

Anw: /* Create Patch */

2011-06-27T10:30:48Z

Create Patch

← Older revision		Revision as of 12:30, 27 June 2011
Line 65:		Line 65:
	SourceSafe will drop this history to the clipboard, ready for pasting.		SourceSafe will drop this history to the clipboard, ready for pasting.

	~~Past~~ this into the release notes. The format will look as follows:		Paste this into the release notes. The format will look as follows:

	<pre>		<pre>

Anw at 11:01, 9 May 2011

2011-05-09T11:01:52Z

← Older revision		Revision as of 13:01, 9 May 2011
Line 1:		Line 1:
	~~<!-- HEADER RIGHT "foo" -->~~

	==Prerequisites==		==Prerequisites==
	Ensure all code is back in SourceSafe and any new files have been added to SourceSafe in the appropriate sub-solders.		Ensure all code is back in SourceSafe and any new files have been added to SourceSafe in the appropriate sub-solders.

Anw at 11:01, 9 May 2011

2011-05-09T11:01:14Z

← Older revision		Revision as of 13:01, 9 May 2011
Line 1:		Line 1:
			<!-- HEADER RIGHT "foo" -->

	==Prerequisites==		==Prerequisites==
	Ensure all code is back in SourceSafe and any new files have been added to SourceSafe in the appropriate sub-solders.		Ensure all code is back in SourceSafe and any new files have been added to SourceSafe in the appropriate sub-solders.

Anw at 07:23, 9 May 2011

2011-05-09T07:23:15Z

← Older revision		Revision as of 09:23, 9 May 2011
Line 232:		Line 232:

	[[Category:Vision Overview]]		[[Category:Vision Overview]]
	[[Category:Vision Coding and Release\|050]]		[[Category:Vision Coding and Release Doc\|050]]
			[[Category:Vision Coding and Release]]