Talk:CMIS Lookup (Lookup Specification) - Revision history

Dgreenwood at 13:39, 16 October 2025

2025-10-16T13:39:09Z

← Older revision		Revision as of 08:39, 16 October 2025
Line 28:		Line 28:
	=== Dylan 10/16/2025 ===		=== Dylan 10/16/2025 ===
	* Overall, this is a much-improved article (compared to the v2023 one). It's straightforward. The supademos are used well. I agree with Reanna the "How to edit CMISQL Queries" section is a good addition to this article.		* Overall, this is a much-improved article (compared to the v2023 one). It's straightforward. The supademos are used well. I agree with Reanna the "How to edit CMISQL Queries" section is a good addition to this article.
			* I like that the "Lookup Options" are documented here. I wonder if these need more detail (Same note as I had on the [[Lookup Specification]]) article.
	* In the "How fields are populated" section, why are the Hit/Miss/Conflict lines in a pre block?		* In the "How fields are populated" section, why are the Hit/Miss/Conflict lines in a pre block?

Dgreenwood at 13:37, 16 October 2025

2025-10-16T13:37:01Z

← Older revision		Revision as of 08:37, 16 October 2025
Line 25:		Line 25:
	*** Dylan 10/16/2025 - We did standardize this at some point. Put a box around the whole property. Use the phrase "Open the X editor". Enter ''Press the "..." button"'' on the second line. This avoids the bulky wording of "Select the X editor and press the ellipsis button at the end of the property". Instead, just say "Open the X editor". The rectangle clearly highlights the whole property to better distinguish the property name in the property grid. The on screen text ''Press the "..." button'' gives users who don't know how to open a property editor further clarification. See below for an example.		*** Dylan 10/16/2025 - We did standardize this at some point. Put a box around the whole property. Use the phrase "Open the X editor". Enter ''Press the "..." button"'' on the second line. This avoids the bulky wording of "Select the X editor and press the ellipsis button at the end of the property". Instead, just say "Open the X editor". The rectangle clearly highlights the whole property to better distinguish the property name in the property grid. The on screen text ''Press the "..." button'' gives users who don't know how to open a property editor further clarification. See below for an example.
	***: [[File:2025-10-16 08 14 46.png\|800px]]		***: [[File:2025-10-16 08 14 46.png\|800px]]

			=== Dylan 10/16/2025 ===
			* Overall, this is a much-improved article (compared to the v2023 one). It's straightforward. The supademos are used well. I agree with Reanna the "How to edit CMISQL Queries" section is a good addition to this article.
			* In the "How fields are populated" section, why are the Hit/Miss/Conflict lines in a pre block?

Dgreenwood: /* Devon 10/13/2025 */

2025-10-16T13:25:32Z

Devon 10/13/2025

← Older revision		Revision as of 08:25, 16 October 2025
Line 24:		Line 24:
	** '''I personally think having it specifically over where they should press is better. I don't want them to think they can click somewhere on the entire property, but instead, specifically, the ellipsis button of the property.'''		** '''I personally think having it specifically over where they should press is better. I don't want them to think they can click somewhere on the entire property, but instead, specifically, the ellipsis button of the property.'''
	*** Dylan 10/16/2025 - We did standardize this at some point. Put a box around the whole property. Use the phrase "Open the X editor". Enter ''Press the "..." button"'' on the second line. This avoids the bulky wording of "Select the X editor and press the ellipsis button at the end of the property". Instead, just say "Open the X editor". The rectangle clearly highlights the whole property to better distinguish the property name in the property grid. The on screen text ''Press the "..." button'' gives users who don't know how to open a property editor further clarification. See below for an example.		*** Dylan 10/16/2025 - We did standardize this at some point. Put a box around the whole property. Use the phrase "Open the X editor". Enter ''Press the "..." button"'' on the second line. This avoids the bulky wording of "Select the X editor and press the ellipsis button at the end of the property". Instead, just say "Open the X editor". The rectangle clearly highlights the whole property to better distinguish the property name in the property grid. The on screen text ''Press the "..." button'' gives users who don't know how to open a property editor further clarification. See below for an example.
	***: [[File:2025-10-16 08 14 46.png]]		***: [[File:2025-10-16 08 14 46.png\|800px]]

Dgreenwood: /* Devon 10/13/2025 */

2025-10-16T13:23:47Z

Devon 10/13/2025

← Older revision		Revision as of 08:23, 16 October 2025
Line 23:		Line 23:
	* For Slide Two of the Supademo in the "Configure a CMIS Lookup" subsection of "How to Add and Configure a CMIS Lookup": The second Custom Area Box only wraps around the ellipses to the right of the Lookup Specifications property, rather than the property itself. I think it would help, visually, if the box were wrapped around the entire property, and the text tip went something like, "Click '...' at the end of the Lookups property."		* For Slide Two of the Supademo in the "Configure a CMIS Lookup" subsection of "How to Add and Configure a CMIS Lookup": The second Custom Area Box only wraps around the ellipses to the right of the Lookup Specifications property, rather than the property itself. I think it would help, visually, if the box were wrapped around the entire property, and the text tip went something like, "Click '...' at the end of the Lookups property."
	** '''I personally think having it specifically over where they should press is better. I don't want them to think they can click somewhere on the entire property, but instead, specifically, the ellipsis button of the property.'''		** '''I personally think having it specifically over where they should press is better. I don't want them to think they can click somewhere on the entire property, but instead, specifically, the ellipsis button of the property.'''
	*** Dylan 10/16/2025 - We did standardize this at some point. Put a box around the whole property. Use the phrase "Open the X editor". Enter ''Press the "..." button"'' on the second line. This avoids the bulky wording of "Select the X editor and press the ellipsis button at the end of the property". Instead, just say "Open the X editor". The rectangle clearly highlights the whole property to better distinguish the property name in the property grid. The on screen text ''Press the "..." button.'' gives users who don't know how to open a property editor further clarification. See below for an example.		*** Dylan 10/16/2025 - We did standardize this at some point. Put a box around the whole property. Use the phrase "Open the X editor". Enter ''Press the "..." button"'' on the second line. This avoids the bulky wording of "Select the X editor and press the ellipsis button at the end of the property". Instead, just say "Open the X editor". The rectangle clearly highlights the whole property to better distinguish the property name in the property grid. The on screen text ''Press the "..." button'' gives users who don't know how to open a property editor further clarification. See below for an example.
	***: [[File:2025-10-16 08 14 46.png]]		***: [[File:2025-10-16 08 14 46.png]]

Dgreenwood at 13:23, 16 October 2025

2025-10-16T13:23:11Z

← Older revision		Revision as of 08:23, 16 October 2025
Line 23:		Line 23:
	* For Slide Two of the Supademo in the "Configure a CMIS Lookup" subsection of "How to Add and Configure a CMIS Lookup": The second Custom Area Box only wraps around the ellipses to the right of the Lookup Specifications property, rather than the property itself. I think it would help, visually, if the box were wrapped around the entire property, and the text tip went something like, "Click '...' at the end of the Lookups property."		* For Slide Two of the Supademo in the "Configure a CMIS Lookup" subsection of "How to Add and Configure a CMIS Lookup": The second Custom Area Box only wraps around the ellipses to the right of the Lookup Specifications property, rather than the property itself. I think it would help, visually, if the box were wrapped around the entire property, and the text tip went something like, "Click '...' at the end of the Lookups property."
	** '''I personally think having it specifically over where they should press is better. I don't want them to think they can click somewhere on the entire property, but instead, specifically, the ellipsis button of the property.'''		** '''I personally think having it specifically over where they should press is better. I don't want them to think they can click somewhere on the entire property, but instead, specifically, the ellipsis button of the property.'''
			*** Dylan 10/16/2025 - We did standardize this at some point. Put a box around the whole property. Use the phrase "Open the X editor". Enter ''Press the "..." button"'' on the second line. This avoids the bulky wording of "Select the X editor and press the ellipsis button at the end of the property". Instead, just say "Open the X editor". The rectangle clearly highlights the whole property to better distinguish the property name in the property grid. The on screen text ''Press the "..." button.'' gives users who don't know how to open a property editor further clarification. See below for an example.
			***: [[File:2025-10-16 08 14 46.png]]

Randallkinard: /* Devon 10/13/2025 */

2025-10-15T15:47:15Z

Devon 10/13/2025

← Older revision		Revision as of 10:47, 15 October 2025
Line 22:		Line 22:
	=== Devon 10/13/2025 ===		=== Devon 10/13/2025 ===
	* For Slide Two of the Supademo in the "Configure a CMIS Lookup" subsection of "How to Add and Configure a CMIS Lookup": The second Custom Area Box only wraps around the ellipses to the right of the Lookup Specifications property, rather than the property itself. I think it would help, visually, if the box were wrapped around the entire property, and the text tip went something like, "Click '...' at the end of the Lookups property."		* For Slide Two of the Supademo in the "Configure a CMIS Lookup" subsection of "How to Add and Configure a CMIS Lookup": The second Custom Area Box only wraps around the ellipses to the right of the Lookup Specifications property, rather than the property itself. I think it would help, visually, if the box were wrapped around the entire property, and the text tip went something like, "Click '...' at the end of the Lookups property."
			** '''I personally think having it specifically over where they should press is better. I don't want them to think they can click somewhere on the entire property, but instead, specifically, the ellipsis button of the property.'''

Dsmith at 18:59, 13 October 2025

2025-10-13T18:59:14Z

← Older revision		Revision as of 13:59, 13 October 2025
Line 19:		Line 19:
	* I think a space needs to be in between the Words "Population" and "Method" under Field Population.		* I think a space needs to be in between the Words "Population" and "Method" under Field Population.
	** '''"Fixed by removing reference to code object - 10/10/2025'''		** '''"Fixed by removing reference to code object - 10/10/2025'''

			=== Devon 10/13/2025 ===
			* For Slide Two of the Supademo in the "Configure a CMIS Lookup" subsection of "How to Add and Configure a CMIS Lookup": The second Custom Area Box only wraps around the ellipses to the right of the Lookup Specifications property, rather than the property itself. I think it would help, visually, if the box were wrapped around the entire property, and the text tip went something like, "Click '...' at the end of the Lookups property."

Randallkinard: /* Reanna Patton 10/9/2025 */

2025-10-10T19:30:38Z

Reanna Patton 10/9/2025

← Older revision		Revision as of 14:30, 10 October 2025
Line 1:		Line 1:
	===Reanna Patton 10/9/2025===		===Reanna Patton 10/9/2025===
	* In the prerequisites, I would include a link to the CMIS Connection article.		* In the prerequisites, I would include a link to the CMIS Connection article.
	* In the How to add and configure a test CMIS Lookup, in the Configure a CMIS Lookup... I know the AI keeps referring to the Grooper Design Page as the "Grooper Design Studio" but since we no longer have the thick client, do we still want to call it that? It would make more sense to me to call it the Design Page or just reference the Node Tree. Sorry if that's too nit picky on my end.		** '''Link to CMIS Connection added - 10/10/2025'''
	* Number 4 in the Configure a CMIS Lookup there's a typo.		* In the How to add and configure a test CMIS Lookup, in the Configure a CMIS Lookup... I know the AI keeps referring to the Grooper Design Page as the "Grooper Design Studio" but since we no longer have the thick client, do we still want to call it that? It would make more sense to me to call it the Design Page or just reference the Node Tree. Sorry if that's too nit picky on my end.
	* The first Supademo, there's a screenshot that shows one lookup has already been configured, then the next slide, there are no lookups showing in the pop up. Again, might be too nit picky.		** '''Changed wording to "Grooper Design Page" - 10/10/2025'''
			* Number 4 in the Configure a CMIS Lookup there's a typo.
			** '''Typo corrected - 10/10/2025'''
			* The first Supademo, there's a screenshot that shows one lookup has already been configured, then the next slide, there are no lookups showing in the pop up. Again, might be too nit picky.
			** '''Screenshot adjusted - 10/10/2025'''
	* I just want to note that I LOVE the How to Edit the CMISQL Queries section. This is something I struggled with a lot.		* I just want to note that I LOVE the How to Edit the CMISQL Queries section. This is something I struggled with a lot.
	* In the Step by Step query edit, I would include how to get to the Query editor.		* In the Step by Step query edit, I would include how to get to the Query editor.
	* In the instructions for the Step by Step Query edit, #7 has a typo.		** '''Not sure this is necessary as the demo that shows how to add and configure a CMIS Lookup shows this, but added screenshots anyway - 10/10/2025'''
	* I would mention in the AI voiceover in the supademo something about the intellisense that pops up to help you fill in the information. That might be overkill though.		* In the instructions for the Step by Step Query edit, #7 has a typo.
	* In the Lookup Options section the Miss Disposition's and Conflict Disposition's need apostrophes. Also a space in between Miss and Disposition's.		** '''Typo corrected - 10/10/2025'''
			* I would mention in the AI voiceover in the supademo something about the intellisense that pops up to help you fill in the information. That might be overkill though.
			** '''Voiceover modified - 10/10/2025'''
			* In the Lookup Options section the Miss Disposition's and Conflict Disposition's need apostrophes. Also a space in between Miss and Disposition's.
			** '''Fixed by removing reference to code objects - 10/10/2025'''
	* I think a space needs to be in between the Words "Population" and "Method" under Field Population.		* I think a space needs to be in between the Words "Population" and "Method" under Field Population.
			** '''"Fixed by removing reference to code object - 10/10/2025'''

Rpatton at 21:42, 9 October 2025

2025-10-09T21:42:11Z

← Older revision		Revision as of 16:42, 9 October 2025
Line 2:		Line 2:
	* In the prerequisites, I would include a link to the CMIS Connection article.		* In the prerequisites, I would include a link to the CMIS Connection article.
	* In the How to add and configure a test CMIS Lookup, in the Configure a CMIS Lookup... I know the AI keeps referring to the Grooper Design Page as the "Grooper Design Studio" but since we no longer have the thick client, do we still want to call it that? It would make more sense to me to call it the Design Page or just reference the Node Tree. Sorry if that's too nit picky on my end.		* In the How to add and configure a test CMIS Lookup, in the Configure a CMIS Lookup... I know the AI keeps referring to the Grooper Design Page as the "Grooper Design Studio" but since we no longer have the thick client, do we still want to call it that? It would make more sense to me to call it the Design Page or just reference the Node Tree. Sorry if that's too nit picky on my end.
	* Number 4 in the Configure an CMIS Lookup there's a typo.		* Number 4 in the Configure a CMIS Lookup there's a typo.
	* The first Supademo, there's a screenshot that shows one lookup has already been configured, then the next slide, there are no lookups showing in the pop up. Again, might be too nit picky.		* The first Supademo, there's a screenshot that shows one lookup has already been configured, then the next slide, there are no lookups showing in the pop up. Again, might be too nit picky.
	* I just want to note that I LOVE the How to Edit the CMISQL Queries section. This is something I struggled with a lot.		* I just want to note that I LOVE the How to Edit the CMISQL Queries section. This is something I struggled with a lot.

Rpatton: Created page with "===Reanna Patton 10/9/2025=== * In the prerequisites, I would include a link to the CMIS Connection article. * In the How to add and configure a test CMIS Lookup, in the Configure a CMIS Lookup... I know the AI keeps referring to the Grooper Design Page as the "Grooper Design Studio" but since we no longer have the thick client, do we still want to call it that? It would make more sense to me to call it the Design Page or just reference the Node Tree. Sorry if that's too..."

2025-10-09T21:41:52Z

Created page with "===Reanna Patton 10/9/2025=== * In the prerequisites, I would include a link to the CMIS Connection article. * In the How to add and configure a test CMIS Lookup, in the Configure a CMIS Lookup... I know the AI keeps referring to the Grooper Design Page as the "Grooper Design Studio" but since we no longer have the thick client, do we still want to call it that? It would make more sense to me to call it the Design Page or just reference the Node Tree. Sorry if that's too..."

New page

===Reanna Patton 10/9/2025===
* In the prerequisites, I would include a link to the CMIS Connection article.
* In the How to add and configure a test CMIS Lookup, in the Configure a CMIS Lookup... I know the AI keeps referring to the Grooper Design Page as the "Grooper Design Studio" but since we no longer have the thick client, do we still want to call it that? It would make more sense to me to call it the Design Page or just reference the Node Tree. Sorry if that's too nit picky on my end.
* Number 4 in the Configure an CMIS Lookup there's a typo.
* The first Supademo, there's a screenshot that shows one lookup has already been configured, then the next slide, there are no lookups showing in the pop up. Again, might be too nit picky.
* I just want to note that I LOVE the How to Edit the CMISQL Queries section. This is something I struggled with a lot.
* In the Step by Step query edit, I would include how to get to the Query editor.
* In the instructions for the Step by Step Query edit, #7 has a typo.
* I would mention in the AI voiceover in the supademo something about the intellisense that pops up to help you fill in the information. That might be overkill though.
* In the Lookup Options section the Miss Disposition's and Conflict Disposition's need apostrophes. Also a space in between Miss and Disposition's.
* I think a space needs to be in between the Words "Population" and "Method" under Field Population.