You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: This form is for submitting issues about Connections MT documentation, not Connections MT itself.
Description
The "Set up Customizer" section of the "Steps to install or upgrade to Component Pack 8" page does mention the steps "Set up your reverse proxy to forward some traffic to the customizer and "Configuring the Customizer component" but it does not mention the step "Enabling the Connections app registry service for customization", which is mandatory if you want to use Customizer to modify the UI, which is it's main function.
Observed
Desired
Add a line similar to this in order to tie in the mandatory configuration step, so Customizer actually works as expected by customers:
Connections needs to be enabled to make requests to the app registry service to discover the extensions that Customizer provides. By default, Connections applications do not try to make requests to the app registry service to avoid unnecessary requests if the app registry service has not been deployed as part of a Component Pack installation. In order to enable the Customizer integration into Connections, follow the steps outlined in Enabling the Connections app registry service for customization.
Note: This form is for submitting issues about Connections MT documentation, not Connections MT itself.
Description
The "Set up Customizer" section of the "Steps to install or upgrade to Component Pack 8" page does mention the steps "Set up your reverse proxy to forward some traffic to the customizer and "Configuring the Customizer component" but it does not mention the step "Enabling the Connections app registry service for customization", which is mandatory if you want to use Customizer to modify the UI, which is it's main function.
Observed
Desired
Add a line similar to this in order to tie in the mandatory configuration step, so Customizer actually works as expected by customers:
Topics
https://opensource.hcltechsw.com/connections-doc/v8/admin/install/cp_install_services_tasks.html#section_n3c_xhj_dvb
https://opensource.hcltechsw.com/connections-doc/v8/admin/customize/enabling-app-registry.html?scLang=en
The text was updated successfully, but these errors were encountered: