In the prerequisites, I would include a link to the CMIS Connection article.
Link to CMIS Connection added - 10/10/2025
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.
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.
In the Step by Step query edit, I would include how to get to the Query editor.
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
In the instructions for the Step by Step Query edit, #7 has a typo.
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.
"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."
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
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?
