Global Name:Request - Revision history

Admin at 01:16, 21 January 2023

2023-01-21T01:16:08Z

@@ Line 310: / Line 310: @@
 |class="genderTablePink"|F
 |class="genderTablePink"|F
 |}

Admin at 17:42, 12 August 2022

2022-08-12T17:42:08Z

← Older revision		Revision as of 17:42, 12 August 2022
Line 424:		Line 424:

	::For example:		::For example:
	::<pre>opt=LegacySalutation:~~true~~</pre>		::<pre>opt=LegacySalutation:On</pre>
	::Will return 'Mr. John Smith' when the input was 'John Smith'		::Will return 'Mr. John Smith' when the input was 'John Smith'

Admin at 23:47, 11 August 2022

2022-08-11T23:47:19Z

← Older revision		Revision as of 23:47, 11 August 2022
Line 418:		Line 418:
	!Option Name!!Parameter!!Definition		!Option Name!!Parameter!!Definition
	\|-		\|-
	\|rowspan="2"\|'''LegacySalutation'''\|\|<code>~~true~~</code>\|\|Creates a formal salutation.		\|rowspan="2"\|'''LegacySalutation'''\|\|<code>On</code>\|\|Creates a formal salutation.
	\|-		\|-
	\|<code>~~false~~</code>\|\|Will not create a formal salutation.		\|<code>Off</code>\|\|'''''Default.''''' Will not create a formal salutation.
	\|}		\|}

Admin at 00:38, 11 August 2022

2022-08-11T00:38:40Z

@@ Line 343: / Line 343: @@
 :<h4 style="border-bottom:1px solid black;">SalutationOrder</h4>
-::''Optional''. This option creates a pipe delimited list of preferred salutation formats and precedence to use when generating salutations. There are four possible formats to use for creating salutations. The options in default order are:
+::''Optional''. This option creates a pipe delimited list of preferred salutation formats and precedence to use when generating salutations. There are five possible formats to use for creating salutations. The options in default order are:
@@ Line 349: / Line 349: @@
 !Option Name!!Parameter Name!!Definition!!Example
 |-
-|rowspan="4"|'''Salutation'''||<code>Formal</code>||Contains name prefix and lastname and suffix||<code>Mr. Smith MD</code>
+|rowspan="5"|'''Salutation'''||<code>Formal</code>||Contains name prefix and lastname and suffix||<code>Mr. Smith MD</code>
 |-
 |<code>Informal</code>||Contains firstname.||<code>John</code>
 |-
 |<code>FirstLast</code>||Contains firstname and lastname.||<code>John Smith</code>
 |-
 |<code>Blank</code>||<code><return blank></code>||<code><blank></code>
@@ Line 360: / Line 362: @@
 ::For example, if the request is configured as:
 ::<pre>opt=Salutation:Formal|FirstLast|Blank|Informal</pre>
-::this requests a formal salutation to be built where possible but would rather have a blank salutation than an informal salutation (this could replace a blank with a proprietary slug like ‘Valued Customer:’).
+::This requests a formal salutation to be built where possible but would rather have a blank salutation than an informal salutation (this could replace a blank with a proprietary slug like ‘Valued Customer:’).

Admin at 16:07, 12 May 2022

2022-05-12T16:07:27Z

← Older revision		Revision as of 16:07, 12 May 2022
Line 372:		Line 372:
	\|-		\|-
	\|REST\|\|<code>&format = '''''string'''''</code>		\|REST\|\|<code>&format = '''''string'''''</code>
	\|-
	~~\|JSON (HTTP Header)\|\|<code>Accept: application/json</code>~~
	\|-
	~~\|SOAP/XML (HTTP Header)\|\|<code>Accept: application/xml</code>~~
	\|}		\|}

Admin at 23:36, 3 May 2022

2022-05-03T23:36:14Z

← Older revision		Revision as of 23:36, 3 May 2022
Line 366:		Line 366:
	:''Optional.''		:''Optional.''

	:The desired format of the response.		:The desired format of the response. Possible values for this option are "json" or "xml". The default value is "xml".

	:{\| class="alternate01"		:{\| class="alternate01"

Admin at 19:01, 24 March 2021

2021-03-24T19:01:47Z

← Older revision		Revision as of 19:01, 24 March 2021
Line 13:		Line 13:
	==URL==		==URL==
	{{URL-GlobalName}}		{{URL-GlobalName}}


			==Header==
			HTTP headers need to match the protocols and formats being used.

			Global Name requires the values of <code>Content-Type</code> and <code>Accept</code>.

			===Example JSON Request Header===
			<pre>{
			"Content-Type": "application/json; charset=utf-8",
			"Accept": "application/json"
			}</pre>

Admin at 18:59, 8 March 2021

2021-03-08T18:59:27Z

← Older revision		Revision as of 18:59, 8 March 2021
Line 29:		Line 29:
	\|Format\|\|format\|\|Format		\|Format\|\|format\|\|Format
	\|-		\|-
	\|Record ID\|\|rowspan="3" valign="center"\|Record\|\| \|\|RecordID		\|Record ID\|\|rowspan="4" valign="center"\|Record\|\| \|\|RecordID
	\|-		\|-
	\|Company\|\|comp\|\|Company		\|Company\|\|comp\|\|Company
	\|-		\|-
	\|Full Name\|\|full\|\|FullName		\|Full Name\|\|full\|\|FullName
			\|-
			\|Country\|\|ctry\|\|Country
	\|}		\|}

Line 131:		Line 133:
	\|rowspan="9"\|'''NameHint'''\|\|<code>1</code>\|\|<code>DefinitelyFull</code>\|\|Name will always be treated as normal name order regardless of formatting or punctuation.		\|rowspan="9"\|'''NameHint'''\|\|<code>1</code>\|\|<code>DefinitelyFull</code>\|\|Name will always be treated as normal name order regardless of formatting or punctuation.
	\|-		\|-
	\|<code>2</code>\|\|<code>VeryLikelyFull</code>\|\|Name will be treated as normal name order unless inverse order is clearly indicated by formatting or punctuation.		\|<code>2</code>\|\|<code>VeryLikelyFull</code>\|\|'''<span style="color:red">Deprecated. Will resolve to <code>Varying</code> (Name Hint:4).</span>''' Name will be treated as normal name order unless inverse order is clearly indicated by formatting or punctuation.
	\|-		\|-
	\|<code>3</code>\|\|<code>ProbablyFull</code>\|\|If necessary, statistical logic will be employed to determine name order, with a bias towards normal name order.		\|<code>3</code>\|\|<code>ProbablyFull</code>\|\|'''<span style="color:red">Deprecated. Will resolve to <code>Varying</code> (Name Hint:4).</span>''' If necessary, statistical logic will be employed to determine name order, with a bias towards normal name order.
	\|-		\|-
	\|<code>4</code>\|\|<code>Varying</code>\|\|'''''Default.''''' If necessary, statistical logic will be employed to determine name order, with no bias toward either name order.		\|<code>4</code>\|\|<code>Varying</code>\|\|'''''Default.''''' If necessary, statistical logic will be employed to determine name order, with no bias toward either name order.
	\|-		\|-
	\|<code>5</code>\|\|<code>ProbablyInverse</code>\|\|If necessary, statistical logic will be employed to determine name order, with a bias toward inverse name order.		\|<code>5</code>\|\|<code>ProbablyInverse</code>\|\|'''<span style="color:red">Deprecated. Will resolve to <code>Varying</code> (Name Hint:4).</span>''' If necessary, statistical logic will be employed to determine name order, with a bias toward inverse name order.
	\|-		\|-
	\|<code>6</code>\|\|<code>VeryLikelyInverse</code>\|\|Name will be treated as inverse name order unless normal order is clearly indicated by formatting or punctuation.		\|<code>6</code>\|\|<code>VeryLikelyInverse</code>\|\|'''<span style="color:red">Deprecated. Will resolve to <code>Varying</code> (Name Hint:4).</span>''' Name will be treated as inverse name order unless normal order is clearly indicated by formatting or punctuation.
	\|-		\|-
	\|<code>7</code>\|\|<code>DefinitelyInverse</code>\|\|Name will always be treated as inverse name order, regardless of formatting or punctuation.		\|<code>7</code>\|\|<code>DefinitelyInverse</code>\|\|Name will always be treated as inverse name order, regardless of formatting or punctuation.
	\|-		\|-
	\|<code>8</code>\|\|<code>MixedFirstName</code>\|\|Name element is expected to only contain first names.		\|<code>8</code>\|\|<code>MixedFirstName</code>\|\|'''<span style="color:red">Obsolete. Will resolve to <code>Varying</code> (Name Hint:4).</span>''' Name element is expected to only contain first names.
	\|-		\|-
	\|<code>9</code>\|\|<code>MixedLastName</code>\|\|Name element is expected to only contain last names.		\|<code>9</code>\|\|<code>MixedLastName</code>\|\|'''<span style="color:red">Obsolete. Will resolve to <code>Varying</code> (Name Hint:4).</span>''' Name element is expected to only contain last names.
	\|}		\|}

Line 300:		Line 302:

	:<h4 style="border-bottom:1px solid black;">MiddleNameLogic</h4>		:<h4 style="border-bottom:1px solid black;">MiddleNameLogic</h4>
			::'''<span style="color:red">Deprecated. Middle name logic will be determined by the supplied Country, enabling simultaneous processing of records from different countries.</span>'''

	::This option controls how middle names are handled.		::This option controls how middle names are handled.

Line 324:		Line 328:

	::When a hyphen is present, the hyphenated word is always treated as the last name, regardless of content.		::When a hyphen is present, the hyphenated word is always treated as the last name, regardless of content.


			:<h4 style="border-bottom:1px solid black;">SalutationOrder</h4>
			::''Optional''. This option creates a pipe delimited list of preferred salutation formats and precedence to use when generating salutations. There are four possible formats to use for creating salutations. The options in default order are:


			::{\|class="alternate01" cellspacing="0"
			!Option Name!!Parameter Name!!Definition!!Example
			\|-
			\|rowspan="4"\|'''Salutation'''\|\|<code>Formal</code>\|\|Contains name prefix and lastname and suffix\|\|<code>Mr. Smith MD</code>
			\|-
			\|<code>Informal</code>\|\|Contains firstname.\|\|<code>John</code>
			\|-
			\|<code>FirstLast</code>\|\|Contains firstname and lastname.\|\|<code>John Smith</code>
			\|-
			\|<code>Blank</code>\|\|<code><return blank></code>\|\|<code><blank></code>
			\|}

			::For example, if the request is configured as:
			::<pre>opt=Salutation:Formal\|FirstLast\|Blank\|Informal</pre>
			::this requests a formal salutation to be built where possible but would rather have a blank salutation than an informal salutation (this could replace a blank with a proprietary slug like ‘Valued Customer:’).


Line 401:		Line 426:
	\|-		\|-
	\|SOAP/XML\|\|<code><FullName>'''''string'''''</FullName></code>		\|SOAP/XML\|\|<code><FullName>'''''string'''''</FullName></code>
			\|}


			<h3 style="background-color:rgb(240,240,240);">Country</h3>
			:''Optional.'' '''(Default is <code>US</code> if not specified).'''

			:The country name, abbreviation, or ISO code of the input name.

			:{\| class="alternate01"
			!Protocol !! Syntax
			\|-
			\|JSON\|\|<code>"Country":"'''''string'''''"</code>
			\|-
			\|REST\|\|<code>&ctry = '''''string'''''</code>
			\|-
			\|XML\|\|<code><Country>'''''string'''''</Country></code>
	\|}		\|}

Admin at 16:31, 26 January 2021

2021-01-26T16:31:31Z

← Older revision		Revision as of 16:31, 26 January 2021
Line 348:		Line 348:
	!Protocol !! Definition		!Protocol !! Definition
	\|-		\|-
	\|JSON\|\|Each ~~email~~ will be contained within [{}] under the Records element.		\|JSON\|\|Each name will be contained within [{}] under the Records element.
	\|-		\|-
	\|REST\|\|The REST interface only allows a single record per request.		\|REST\|\|The REST interface only allows a single record per request.

Admin at 19:13, 7 December 2018

2018-12-07T19:13:45Z

← Older revision		Revision as of 19:13, 7 December 2018
Line 9:		Line 9:

	Global Name supports JSON, JSONP, REST, SOAP, and XML protocols.		Global Name supports JSON, JSONP, REST, SOAP, and XML protocols.


			==URL==
			{{URL-GlobalName}}