-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.1.0, 4.22.6
-
1
-
Severity 3 - Minor
-
Issue Summary
This is reproducible on Data Center: Yes
Having more than 25 items/options rendered in an 'Checkbox/Radio' Insight custom field on customer portal does not render the CF as 'Select'.
Steps to Reproduce
- Go to 'Manage apps' > Insight > 'Insight Configuration' page
- Change 'Default number of objects fetched in custom fields' (under 'User Interaction' section) to a number greater than 25 (e.g. to 50)
- Create an Insight custom field and set its 'Type of interaction' to 'Checkbox/radio'
- Configure the custom field to be rendered as a field for a request type in customer portal
- Create more than 25 objects/assets that'll be rendered for the Insight custom field
- Go to the 'Create request' page of that request type on customer portal
Expected Results
The custom field should be rendered as 'Select'.
Actual Results
The custom field is still rendered as 'Checkbox/radio'
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- links to
[JSDSERVER-11896] Having more than 25 items/options rendered in an 'Checkbox/Radio' Insight custom field on customer portal does not render the CF as select
| Labels | New: ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 955630 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
This is reproducible on Data Center: Yes Having more than 25 items/options rendered in an 'Checkbox/Radio' Insight custom field on customer portal *does not* render the CF as 'Select'. h3. Steps to Reproduce # Go to 'Manage apps' > Insight > 'Insight Configuration' page # Change 'Default number of objects fetched in custom fields' (under 'User Interaction' section) to a number greater than 25 (e.g. to 50) # Create an Insight custom field and set its 'Type of interaction' to 'Checkbox/radio' # Configure the custom field to be rendered as a field for a request type in customer portal # Create more than 25 objects/assets that'll be rendered for the Insight custom field # Go to the 'Create request' page of that request type on customer portal h3. Expected Results The custom field should be rendered as 'Select'. h3. Actual Results The custom field is still rendered as 'Checkbox/radio' h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
This is reproducible on Data Center: Yes Having more than 25 items/options rendered in an 'Checkbox/Radio' Insight custom field on customer portal *does not* render the CF as 'Select'. h3. Steps to Reproduce # Go to 'Manage apps' > Insight > 'Insight Configuration' page # Change 'Default number of objects fetched in custom fields' (under 'User Interaction' section) to a number greater than 25 (e.g. to 50) !insight-custom-field-fetch-limit-global-setting.png|thumbnail! # Create an Insight custom field and set its 'Type of interaction' to 'Checkbox/radio' !insight-custom-field-type-of-interaction-setting.png|thumbnail! # Configure the custom field to be rendered as a field for a request type in customer portal # Create more than 25 objects/assets that'll be rendered for the Insight custom field # Go to the 'Create request' page of that request type on customer portal h3. Expected Results The custom field should be rendered as 'Select'. h3. Actual Results The custom field is still rendered as 'Checkbox/radio' h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Attachment | New: insight-custom-field-type-of-interaction-setting.png [ 424455 ] |
| Attachment | New: insight-custom-field-fetch-limit-global-setting.png [ 424454 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |