Fields - Revision history

CrmtogetherPortal at 13:32, 3 May 2018

2018-05-03T13:32:11Z

← Older revision		Revision as of 14:32, 3 May 2018
Line 9:		Line 9:


	When a case is created by a non-company primary person the "case_authorised" and "case_authorisedEsc" values are set to "N" (No).		When a case is created by a non-company primary person the "case_authorised" and "case_authorisedEsc" values are set to "N" (No). The primary person must log into the portal and Authorise the case(s).

	If created by a company primary person then the values are set to "Y" (Yes)		If created by a company primary person then the values are set to "Y" (Yes)

2018-05-03T13:30:42Z

← Older revision		Revision as of 14:30, 3 May 2018
Line 17:		Line 17:
	settings		settings

	* option to turn off the need to authorise ~~caseslblLogRegisteredProductsHintTitle~~		* option to turn off the need to authorise cases

	<add key="IgnoreCentralSupport" value="N"/>		<add key="IgnoreCentralSupport" value="N"/>

	* Name of the field to be used for the authorisation		* Name of the field to be used for the authorisation
	case_authorised should be a selection Y/N codes		case_authorised should be a selection Y/N codes
	<add key="CaseAuthorisedFieldName" value="case_authorised"/>		<add key="CaseAuthorisedFieldName" value="case_authorised"/>

	<add key="CaseAuthorisedFieldName" value="case_authorised"/>		<add key="CaseAuthorisedFieldName" value="case_authorised"/>
	<add key="CaseAuthorisedYes" value="Y"/>		<add key="CaseAuthorisedYes" value="Y"/>
	<add key="CaseAuthorisedNo" value="N"/>		<add key="CaseAuthorisedNo" value="N"/>

	* Name of the field to be used for the authorisation escalation		* Name of the field to be used for the authorisation escalation
	<add key="CaseAuthorisedFieldNameEsc" value="case_authorisedEsc"/>		<add key="CaseAuthorisedFieldNameEsc" value="case_authorisedEsc"/>

2018-05-03T13:30:06Z

← Older revision		Revision as of 14:30, 3 May 2018
Line 15:		Line 15:
	The "case_authorisedEsc" field is used to trigger the Escalation where you can control system messages and emails. See the Escalations section for details.		The "case_authorisedEsc" field is used to trigger the Escalation where you can control system messages and emails. See the Escalations section for details.

			settings

			* option to turn off the need to authorise caseslblLogRegisteredProductsHintTitle

			<add key="IgnoreCentralSupport" value="N"/>

			* Name of the field to be used for the authorisation
			case_authorised should be a selection Y/N codes
			<add key="CaseAuthorisedFieldName" value="case_authorised"/>

			<add key="CaseAuthorisedFieldName" value="case_authorised"/>
			<add key="CaseAuthorisedYes" value="Y"/>
			<add key="CaseAuthorisedNo" value="N"/>

			* Name of the field to be used for the authorisation escalation
			<add key="CaseAuthorisedFieldNameEsc" value="case_authorisedEsc"/>

			For more details on Escalations see http://customer365.crmtogether.com/index.php?title=Escalations

	----		----

2014-10-29T15:11:26Z

← Older revision		Revision as of 16:11, 29 October 2014
Line 33:		Line 33:
	<add key="case_priority" value="Normal"/>		<add key="case_priority" value="Normal"/>

			<add key="use_default_case_secterr" value="Y"/>
			<add key="case_secterr" value="-1719701254"/>


	----		----

2014-08-05T16:06:58Z

← Older revision		Revision as of 17:06, 5 August 2014
Line 14:		Line 14:

	The "case_authorisedEsc" field is used to trigger the Escalation where you can control system messages and emails. See the Escalations section for details.		The "case_authorisedEsc" field is used to trigger the Escalation where you can control system messages and emails. See the Escalations section for details.


			----
			Portal case settings

			Within the web.config file you can specify to use the config defaults or not (if they are on the cases screen for example)

			<add key="use_default_case_source" value="Y"/>
			<add key="case_source" value="Web"/>

			<add key="use_default_case_status" value="Y"/>
			<add key="case_status" value="In Progress"/>

			<add key="use_default_case_stage" value="Y"/>
			<add key="case_stage" value="Logged"/>

			<add key="use_default_case_priority" value="Y"/>
			<add key="case_priority" value="Normal"/>



			----

2011-12-22T15:21:09Z

← Older revision		Revision as of 16:21, 22 December 2011
Line 2:		Line 2:


	Field Name Type LookupValue		Field Name Type LookupValue (existing)

	case_authorised - Selection - Yes/No		case_authorised - Selection - Yes/No

2011-12-22T12:10:03Z

← Older revision		Revision as of 13:10, 22 December 2011
Line 3:		Line 3:

	Field Name Type LookupValue		Field Name Type LookupValue

	case_authorised - Selection - Yes/No		case_authorised - Selection - Yes/No

	case_authorisedEsc - Selection - Yes/No		case_authorisedEsc - Selection - Yes/No


			When a case is created by a non-company primary person the "case_authorised" and "case_authorisedEsc" values are set to "N" (No).

			If created by a company primary person then the values are set to "Y" (Yes)

			The "case_authorisedEsc" field is used to trigger the Escalation where you can control system messages and emails. See the Escalations section for details.

2011-12-22T12:07:27Z

← Older revision		Revision as of 13:07, 22 December 2011
Line 1:		Line 1:
			To use case management authorisation you need the following fields within the Cases entity


	Selection		Field Name Type LookupValue
	~~"comp_centralsupport"~~		case_authorised - Selection - Yes/No
	Yes/No		case_authorisedEsc - Selection - Yes/No

2011-12-21T22:11:55Z

Created page with " Selection "comp_centralsupport" Yes/No"

New page

Selection
"comp_centralsupport"
Yes/No