Troubleshooting ScripTouch for Epic - Revision history

John Powers: /* Installation */

2021-09-17T15:02:47Z

Installation

← Older revision		Revision as of 11:02, 17 September 2021
Line 24:		Line 24:
	\| ScriptelDevice.3		\| ScriptelDevice.3
	\|-		\|-
	\| 2017		\| 2017'''*'''
	\| ScriptelDevice.3~~(*)~~		\| ScriptelDevice.3
	\|-		\|-
	\| Post-2017		\| Post-2017'''*'''
	\| ScriptelDevice.5~~(*)~~		\| ScriptelDevice.5
	\|}		\|}

	(*~~)Typically automatically~~ configured in this version of Epic		'''*''' Automatically configured in this version of Epic

	==Debugging Remote Connections==		==Debugging Remote Connections==

Jeremy Vasta: /* Creating Debug Logs */

2020-08-25T18:36:54Z

Creating Debug Logs

← Older revision		Revision as of 14:36, 25 August 2020
Line 124:		Line 124:

	==Creating Debug Logs==		==Creating Debug Logs==
	The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on ~~forwarding~~ by doing the following on your Hyperspace server:		The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on logging by doing the following on your Hyperspace server:
	*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].		*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
	*Under 'System variables' click the 'New...' button.		*Under 'System variables' click the 'New...' button.

Michael Powers: /* Installation */

2018-01-23T17:38:32Z

Installation

← Older revision		Revision as of 13:38, 23 January 2018
Line 25:		Line 25:
	\|-		\|-
	\| 2017		\| 2017
	\| ScriptelDevice.3~~<br />~~(~~not required~~)		\| ScriptelDevice.3(*)
	\|-		\|-
	\| Post-2017		\| Post-2017
	\| ScriptelDevice.5~~<br />~~(~~not required~~)		\| ScriptelDevice.5(*)
	\|}		\|}

			(*)Typically automatically configured in this version of Epic

	==Debugging Remote Connections==		==Debugging Remote Connections==

Michael Powers: /* Installation */

2018-01-23T17:35:37Z

Installation

← Older revision		Revision as of 13:35, 23 January 2018
Line 27:		Line 27:
	\| ScriptelDevice.3<br />(not required)		\| ScriptelDevice.3<br />(not required)
	\|-		\|-
	\| ~~2018~~		\| Post-2017
	\| ScriptelDevice.4<br />(not required)		\| ScriptelDevice.5<br />(not required)
	\|}		\|}

Michael Powers: /* Beta Features */

2017-12-13T19:09:28Z

Beta Features

← Older revision		Revision as of 15:09, 13 December 2017
Line 155:		Line 155:
	Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].		Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

	==~~Beta Features~~==		==Pad is Disabled After Signing==
	~~===Annotation and Timestamp===~~		A new feature added in ScripTouch for Epic 3.2.47 and higher automatically disables the signature pad, to disable the behavior see [[Prevent Epic from Locking Signature Pad\|here]].
	~~This~~ feature ~~has been~~ added ~~as of Version~~ 3.1.~~66 (September 23rd, 2016). When activated, it will bake the annotation~~ and ~~timestamp into~~ the signature.

	~~To activate this feature~~, ~~please do~~ the ~~following:~~
	*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corporation\Epic'
	**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corporation\Epic'
	*Change the value 'useAnnotations' from ~~'0' to '1'~~
	~~To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.~~

	~~Do note that this feature will NOT add annotations and timestamps to pre-existing signatures~~.

John Powers: /* Installation */

2017-11-10T14:56:21Z

Installation

← Older revision		Revision as of 10:56, 10 November 2017
Line 3:		Line 3:

	==Installation==		==Installation==
	Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId ~~for ScripTouch for Epic~~ prior to engaging Epic.		Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server. [https://www.microsoft.com/en-us/download/details.aspx?id=21 Microsoft .NET 3.5] is required and must be installed separately. For Hyperspace versions prior to 2017 you'll need to know the correct ProgId prior to engaging Epic. Hyperspace 2017 and up no longer require the ProgId to be manually entered.

			[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace Download Epic Hyperspace plugin]

	The ProgIds for ScripTouch for Epic are as follows:		The ProgIds for ScripTouch for Epic are as follows:
Line 10:		Line 12:
	! ProgId		! ProgId
	\|-		\|-
	\| ~~[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-~~2012 ~~2012]~~		\| 2012
	\| ScriptelDevice.0		\| ScriptelDevice.0
	\|-		\|-
	\| ~~[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-~~2014 ~~2014]~~		\| 2014
	\| ScriptelDevice.1		\| ScriptelDevice.1
	\|-		\|-
	\| ~~[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-~~2015 ~~2015]~~		\| 2015
	\| ScriptelDevice.2		\| ScriptelDevice.2
	\|-		\|-
	\| ~~[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-~~2016 ~~2016/2017]~~		\| 2016
	\| ScriptelDevice.3		\| ScriptelDevice.3
	\|-		\|-
	\| ~~[https://services~~.~~scriptel.com~~/~~releases/scriptouch~~-~~epic/scriptel-hyperspace-2018~~ 2018]		\| 2017
	\| ScriptelDevice.4		\| ScriptelDevice.3<br />(not required)
			\|-
			\| 2018
			\| ScriptelDevice.4<br />(not required)
	\|}		\|}

William Powell at 18:48, 25 July 2017

2017-07-25T18:48:19Z

← Older revision		Revision as of 14:48, 25 July 2017
Line 152:		Line 152:
	==Beta Features==		==Beta Features==
	===Annotation and Timestamp===		===Annotation and Timestamp===
	This feature has been ~~add~~ as of Version 3.1.66 (September 23rd, 2016). When activated, it will bake the annotation and timestamp into the signature.		This feature has been added as of Version 3.1.66 (September 23rd, 2016). When activated, it will bake the annotation and timestamp into the signature.

	To activate this feature, please do the following:		To activate this feature, please do the following:

Samuel Lovetro at 17:34, 27 April 2017

2017-04-27T17:34:02Z

← Older revision		Revision as of 13:34, 27 April 2017
Line 155:		Line 155:

	To activate this feature, please do the following:		To activate this feature, please do the following:
	*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel ~~Corperation~~\Epic'		*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corporation\Epic'
	**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel ~~Corperation~~\Epic'		**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corporation\Epic'
	*Change the value 'useAnnotations' from '0' to '1'		*Change the value 'useAnnotations' from '0' to '1'
	To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.		To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

	Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.		Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.

Michael Powers at 12:17, 22 March 2017

2017-03-22T12:17:28Z

← Older revision		Revision as of 08:17, 22 March 2017
Line 19:		Line 19:
	\| ScriptelDevice.2		\| ScriptelDevice.2
	\|-		\|-
	\| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]		\| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016/2017]
	\| ScriptelDevice.3		\| ScriptelDevice.3
	\|-		\|-

Michael Powers: /* VMware Horizon View */

2017-03-21T19:55:08Z

VMware Horizon View

← Older revision		Revision as of 15:55, 21 March 2017
Line 109:		Line 109:

	===VMware Horizon View===		===VMware Horizon View===
	VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 ~~Citrix~~ Guide] to troubleshoot Horizon View USB redirection issues.		VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 VMware Guide] to set up and troubleshoot Horizon View USB redirection issues.

			VMware Horizon View 5.0+ supports USB redirection.

	===Wyse TCX===		===Wyse TCX===