Catalog Item Component Problems/Questions

[Velma]

Has anyone successfully used the catalog item component in UI Builder?

My record producer—which is moderately complicated, with a lot of UI policies, client scripts, and one script include, works fine in whatever that mode is that is linked from Try It on the Record Producer table, works fine in Service Portal, and cannot successfully submit in the catalog item component.

My two multi-line text fields error on blur: “Uncaught TypeError: Cannot read properties of undefined”. For testing, I temporarily deactivated those two fields/variables, and those errors went away. I still get a lot of warnings “Property change event on unknown field” and many info messages “Variable change ignored for record producer”. And either way, if my form has no data entry errors, on submit I still get a blank error box and submit does not succeed.

My other issues are not too important unless someone can tell me how to get this to work. However, in case someone has the ear of the bug-fixers, in descending order of importance:

1\ It is ignoring the reference qualifiers on my reference fields and all the dropdowns are appearing in the wrong orders. (Is there a way to make this work?)

2\ There is a totally out of place “Options” word at the top of my questions, and (unless I have permissions to turn on DOM access and do it, which is a dead-end approach) I can’t hide it or change it.

3\ My intro paragraph is truncated with a Show more, and there is no way I can find to have it show the whole thing and get rid of the Show more.

Assuming I can’t use the catalog item component, would someone make some recommendations for how I access my record producer external to the experience? I can link to whatever version that is from the Record Producer table Try It mode or put it in an iFrame. I can link to the Service Portal mode or put it in an iFrame. I would go with the Service Portal mode—but I cannot get it to redirect back to the experience home page, which the other older-style mode will. Can I get a Service Portal success submission to redirect to my experience somehow? Are there other options?

[Marc Mouries · Accepted solution]

As of the San Diego version, the catalog item component for UI Builder does not support 100% of the platform capabilities. If your catalog item is throwing errors when it is included in a UIB page, use the platform view "http://your-instance/com.glideapp.servicecatalog_cat_item_view.do?sysparm_id=ebbb2414c3013010b83971e54440dd57"

PS: if you see errors in the logs, the best avenue for a resolution if no one responds quickly in the communitiy is to open a support case.

[Velma]

Thanks, Marc. That's what I ended up doing a way back, using the Platform view. Marc also helped me with another piece of the solution--using a styled text link component rather than a button to open the catalog item in the same page (link to destination and navigateto do not appear to support developer choice in terms of where to open a link--internal routes in the same browser tab like it or not, URLs in a different browser tab. A few other things that helped me integrate the Platform view with my UI Builder application: 

--I added optional parameters for submitted and canceled and two styled alerts visible depending on those parameters.

--In the Script that is in the main record producer record/form, a line like this:

producer.redirect = "/x/g/event-support-customer-portal/landing/params/submitted/true";

--In a page load client script, 

cancel_button.setAttribute("onclick","location.assign('x/g/event-support-customer-portal/landing/params/canceled/true');return false;");
back_button_in_header.setAttribute("onclick","location.assign('x/g/event-support-customer-portal/landing');return false;");

I offer these since I tried many different things that came up in search, and these above work--at least in Rome they do. I hope they save someone else a lot of time. The UI Builder component in Rome is not ready for anything that is not extremely simple, if that.

[Marc Mouries]

Thank you for sharing what you've learned.