Summary Screens - Revision history

Sagecrmw at 15:44, 10 August 2026

2026-08-10T15:44:21Z

← Older revision		Revision as of 16:44, 10 August 2026
Line 159:		Line 159:

	== Valid componentType values ==		== Valid componentType values ==

	Based on the canonical map in <code>src/components/FormElements/formElementAsyncComponents.js</code>, used by <code>MyForm.vue</code>'s <code>:is="componentType"</code>. Cross-checked against every <code>componentType</code> value actually present in the metadata/data files in the repo.

	{\| class="wikitable"		{\| class="wikitable"
Line 217:		Line 215:

	'''Notes:'''		'''Notes:'''
	* <code>MyFormUrl</code> (lowercase "rl") is an alias that resolves to the same component as <code>MyFormURL</code> — both are valid~~, but data in the repo (e.g. <code>sage300_defaultmetadata.json</code>) is inconsistent about which casing is used, so both spellings should be documented as acceptable.~~		* <code>MyFormUrl</code> (lowercase "rl") is an alias that resolves to the same component as <code>MyFormURL</code> — both are valid.
	* <code>DisplayComponentType</code> (the property name used in <code>createscript</code>, e.g. <code>DisplayComponentType="MyFormUrl";</code>) does not appear anywhere in the frontend codebase — only <code>componentType</code> (from the JSON payload) is actually consumed by <code>MyForm.vue</code> and <code>EntityViewX.vue</code>. Whatever server-side logic sets <code>DisplayComponentType</code> should use exactly the values listed above.

Sagecrmw at 15:43, 10 August 2026

2026-08-10T15:43:00Z

← Older revision		Revision as of 16:43, 10 August 2026
Line 146:		Line 146:

	[[File:opposummary.png]]		[[File:opposummary.png]]

			All items

			* ValueStyle
			* CaptionStyle
			* DisplayValue
			* Hidden
			* Caption
			* Value
			* Values('fieldname') -coming in Sept 2026
			* DisplayComponentType

			== Valid componentType values ==

			Based on the canonical map in <code>src/components/FormElements/formElementAsyncComponents.js</code>, used by <code>MyForm.vue</code>'s <code>:is="componentType"</code>. Cross-checked against every <code>componentType</code> value actually present in the metadata/data files in the repo.

			{\| class="wikitable"
			! componentType !! Renders as
			\|-
			\| <code>MyFormInput</code> \|\| Single-line text input
			\|-
			\| <code>MyFormInputPlain</code> \|\| Plain text input (no extra chrome)
			\|-
			\| <code>MyFormSelect</code> \|\| Dropdown/select
			\|-
			\| <code>MyFormSelectMultiple</code> \|\| Multi-select dropdown
			\|-
			\| <code>MyFormAutocomplete</code> \|\| Autocomplete input
			\|-
			\| <code>MyFormAutoCompleteCreatio</code> \|\| Creatio-specific autocomplete
			\|-
			\| <code>MyFormRemoteLookup</code> \|\| Remote/server-backed lookup field
			\|-
			\| <code>MyFormCheckbox</code> \|\| Checkbox
			\|-
			\| <code>MyFormSwitch</code> \|\| Toggle switch
			\|-
			\| <code>MyFormRadioGroup</code> \|\| Radio button group
			\|-
			\| <code>MyFormDate</code> \|\| Date picker
			\|-
			\| <code>MyFormDateTime</code> \|\| Date + time picker
			\|-
			\| <code>MyFormTime</code> \|\| Time picker
			\|-
			\| <code>MyFormNumber</code> \|\| Numeric input
			\|-
			\| <code>MyFormCurrency</code> \|\| Currency-formatted input
			\|-
			\| <code>MyFormURL</code> (alias <code>MyFormUrl</code>) \|\| Link/URL
			\|-
			\| <code>MyFormPhone</code> \|\| Phone number (click-to-call)
			\|-
			\| <code>MyFormEmail</code> \|\| Email (click-to-compose)
			\|-
			\| <code>MyFormTextArea</code> \|\| Multi-line text area
			\|-
			\| <code>MyFormPassword</code> \|\| Password input
			\|-
			\| <code>MyFormUserName</code> \|\| Username field
			\|-
			\| <code>MyFormSignature</code> \|\| Signature capture
			\|-
			\| <code>MyFormLabelOnly</code> \|\| Read-only label, no input
			\|-
			\| <code>MyFormDivider</code> \|\| Visual section divider
			\|-
			\| <code>MyFormHTMLViewer</code> \|\| Rendered HTML block
			\|}

			'''Notes:'''
			* <code>MyFormUrl</code> (lowercase "rl") is an alias that resolves to the same component as <code>MyFormURL</code> — both are valid, but data in the repo (e.g. <code>sage300_defaultmetadata.json</code>) is inconsistent about which casing is used, so both spellings should be documented as acceptable.
			* <code>DisplayComponentType</code> (the property name used in <code>createscript</code>, e.g. <code>DisplayComponentType="MyFormUrl";</code>) does not appear anywhere in the frontend codebase — only <code>componentType</code> (from the JSON payload) is actually consumed by <code>MyForm.vue</code> and <code>EntityViewX.vue</code>. Whatever server-side logic sets <code>DisplayComponentType</code> should use exactly the values listed above.

Sagecrmw at 16:10, 26 June 2026

2026-06-26T16:10:10Z

← Older revision		Revision as of 17:10, 26 June 2026
Line 5:		Line 5:
	* Note: Empty fields will not display on the screen.		* Note: Empty fields will not display on the screen.

			Company and person summary for example shows the title plus the communications count in the last year and the open opportunities and cases.

			[[File:summary1.jpg]]

	~~[[File:Screenshot_2026-06-26_152142.png]]~~
	The entity icon is on the left of the screen.		The entity icon is on the left of the screen.

			The information is in the center and on the right of the screen we have the option to toggle the bookmark.

	Below this area we have the tabs.		Below this area we have the tabs.

	[[File:~~Screenshot_2026-06-26_152238~~.~~png~~]]		[[File:summary2.jpg]]

	Hover your mouse over the icon to see the caption.		Hover your mouse over the icon to see the caption. If the tabs are too many you will see the <> icons to navigate across.

	[[File:~~Screenshot_2026-06-26_152456~~.~~png~~]]		[[File:summary3.jpg]]

	Screens are made up of sections.		Screens are made up of sections.
Line 30:		Line 33:
	Links		Links

	~~You can~~ open a ~~record directly~~ in ~~your crm by clicking on the button below~~ the ~~summary~~ section		Text links (usually in green) will open full CRM in a new tab.

			Images usually navigate within the task pane. The exception is the "External" link icon which can be seen in the section header.

	Note that "external" links replace the Sage CRM webservice SID with the one that is active in the live CRM. Users need to log into Sage CRM in their default browser. This is required to work with the Sage CRM security settings (IP address checking and Browser sessionsecurity)		Note that "external" links replace the Sage CRM webservice SID with the one that is active in the live CRM. Users need to log into Sage CRM in their default browser. This is required to work with the Sage CRM security settings (IP address checking and Browser sessionsecurity)
Line 71:		Line 76:
	and this is how it would look		and this is how it would look

	[[File:~~Screenshot_2026-06-26_154658~~.~~png~~]]		[[File:summary5.jpg]]

	C.		C.
Line 88:		Line 93:
	[[File:companyofficeint99.png]]		[[File:companyofficeint99.png]]

			Screens in Accelerator

			[[File:companyofficeint100.png]]

	D. Custom Content support		D. Custom Content support
Line 138:		Line 145:
	Example of how the screen would look		Example of how the screen would look

	[[File:~~Screenshot_2026-06-26_161325~~.png]]		[[File:opposummary.png]]

Sagecrmw at 15:14, 26 June 2026

2026-06-26T15:14:16Z

← Older revision		Revision as of 16:14, 26 June 2026
Line 88:		Line 88:
	[[File:companyofficeint99.png]]		[[File:companyofficeint99.png]]

	~~Screens in Accelerator~~

	~~[[File:companyofficeint100.png]]~~

	D. Custom Content support		D. Custom Content support
Line 140:		Line 138:
	Example of how the screen would look		Example of how the screen would look

	[[File:~~opposummary~~.png]]		[[File:Screenshot_2026-06-26_161325.png]]

Sagecrmw at 14:48, 26 June 2026

2026-06-26T14:48:08Z

← Older revision		Revision as of 15:48, 26 June 2026
Line 71:		Line 71:
	and this is how it would look		and this is how it would look

	[[File:~~summary5~~.~~jpg~~]]		[[File:Screenshot_2026-06-26_154658.png]]

	C.		C.

Sagecrmw at 14:41, 26 June 2026

2026-06-26T14:41:18Z

← Older revision		Revision as of 15:41, 26 June 2026
Line 5:		Line 5:
	* Note: Empty fields will not display on the screen.		* Note: Empty fields will not display on the screen.

	~~Company and person summary for example shows the title plus the communications count in the last year and the open opportunities and cases.~~

	~~[[File:summary1.jpg]]~~

			[[File:Screenshot_2026-06-26_152142.png]]
	The entity icon is on the left of the screen.		The entity icon is on the left of the screen.

	~~The information is in the center and on the right of the screen we have the option to toggle the bookmark.~~

	Below this area we have the tabs.		Below this area we have the tabs.

	[[File:~~summary2~~.~~jpg~~]]		[[File:Screenshot_2026-06-26_152238.png]]

	Hover your mouse over the icon to see the caption~~. If the tabs are too many you will see the <> icons to navigate across~~.		Hover your mouse over the icon to see the caption.

	[[File:~~summary3~~.~~jpg~~]]		[[File:Screenshot_2026-06-26_152456.png]]

	Screens are made up of sections.		Screens are made up of sections.
Line 33:		Line 30:
	Links		Links

	~~Text links (usually in green) will~~ open ~~full CRM~~ in ~~a new tab.~~		You can open a record directly in your crm by clicking on the button below the summary section

	~~Images usually navigate within~~ the ~~task pane. The exception is the "External" link icon which can be seen in~~ the section ~~header.~~

	Note that "external" links replace the Sage CRM webservice SID with the one that is active in the live CRM. Users need to log into Sage CRM in their default browser. This is required to work with the Sage CRM security settings (IP address checking and Browser sessionsecurity)		Note that "external" links replace the Sage CRM webservice SID with the one that is active in the live CRM. Users need to log into Sage CRM in their default browser. This is required to work with the Sage CRM security settings (IP address checking and Browser sessionsecurity)

Sagecrmw at 15:07, 21 April 2022

2022-04-21T15:07:54Z

← Older revision		Revision as of 16:07, 21 April 2022
Line 116:		Line 116:
	window.sayHi= sayHi;		window.sayHi= sayHi;
	</script>		</script>
	<button onclick="sayHi('frank')">~~Mail Merge~~</button>		<button onclick="sayHi('frank')">push me</button>
	</code>		</code>

Sagecrmw at 15:07, 21 April 2022

2022-04-21T15:07:29Z

← Older revision		Revision as of 16:07, 21 April 2022
Line 108:		Line 108:

	EG		EG
	<~~syntaxhighlight lang="js"~~>		<code>
	<script>		<script>
	function sayHi(sender) {		function sayHi(sender) {
Line 117:		Line 117:
	</script>		</script>
	<button onclick="sayHi('frank')">Mail Merge</button>		<button onclick="sayHi('frank')">Mail Merge</button>
	</~~syntaxhighlight~~>		</code>

	E. Create Scripts		E. Create Scripts

Sagecrmw at 15:07, 21 April 2022

2022-04-21T15:07:04Z

← Older revision		Revision as of 16:07, 21 April 2022
Line 108:		Line 108:

	EG		EG
	<~~code~~>		<syntaxhighlight lang="js">
	<script>		<script>
	function sayHi(sender) {		function sayHi(sender) {
Line 117:		Line 117:
	</script>		</script>
	<button onclick="sayHi('frank')">Mail Merge</button>		<button onclick="sayHi('frank')">Mail Merge</button>
	</~~code~~>		</syntaxhighlight>

	E. Create Scripts		E. Create Scripts

Sagecrmw at 15:05, 21 April 2022

2022-04-21T15:05:50Z

← Older revision		Revision as of 16:05, 21 April 2022
Line 113:		Line 113:
	alert('Hello '+sender);		alert('Hello '+sender);
	}		}

	setTimeout(sayHi, 1000, 'bob');		setTimeout(sayHi, 1000, 'bob');
	window.sayHi= sayHi;		window.sayHi= sayHi;