On trying to order the Policy Exception catalog item, the "Valid to" (valid_to) field remains mandatory even though it is filled in (red asterisk) - Support and Troubleshooting

On trying to order the Policy Exception catalog item, the "Valid to" (valid_to) field remains mandatory even though it is filled in (red asterisk) .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Behavior: On trying to order the Policy Exception catalog item, the "Valid to" (valid_to) field remains mandatory even though it is filled in (red asterisk).

Root cause: The valid_to validation is not working because g_scratchpad is not available in "Try It" mode.

This feature is working fine on SP, ESC and Compliance Workspace.

Suggested workaround: Replace g_scratchpad.variable with local variable and update using AJAX calls in all four catalog client scripts (pre-populate policy exception, Validate valid_to, Validate valid_from and Validate on submit):