Overview
The custom page dropdown in the ticket creation space (for Case Portal integration) appears blank, although options are present.
This issue is due to a server-side configuration error in the Khoros Classic community, where dropdown options are populated with technical values but lack visible labels.
Note:
Modifying or making code changes to custom quilts, custom components, and any other custom-built functionality fall outside the scope of Customer Support (CS). If the customization was originally developed by our Professional Services (PS) team, we can submit a PS ticket for further assistance. Otherwise, it is the responsibility of the customer’s development team to maintain and update their in-house customizations.
Solution
Follow these steps to resolve the issue with the Case Portal integration dropdown in your custom page:
-
Access Khoros Classic Admin:
- Log in to the Khoros Classic admin panel.
- Navigate to Studio / Page Management and select the custom quilt being used for your CRM page.
-
Adjust Configuration:
- Locate the component that renders the field (e.g.,
lia-form-jira-application-entry/custom-jira-applications-select). - Review the Case Portal / Jira integration configuration.
- Ensure each option has a proper display label as well as a value (e.g.,
<option value="option_1">Option 1 Label</option>).
- Locate the component that renders the field (e.g.,
-
Deploy Changes:
- Save any changes made to the configuration.
- Clear the community cache if applicable.
-
Verify Resolution:
- Retest the form to ensure the dropdown options are now visible with proper labels.
Note: This change must be implemented by the community admin with access to the Studio/Page Management.
Frequently Asked Questions
- Q1. How do I know if this issue applies to my situation?
- A1. If the field dropdown in the ticket creation space appears blank, but options are selectable, this issue likely applies to you.
Q2. What should I do if the dropdown still appears blank after making changes?- A2. Ensure that the configuration changes were saved correctly and that the community cache was cleared. If the issue persists, verify that each option has a proper display label in the configuration.
Ciprian Nastase
Comments