Couldn’t be able to create new calendar in pega post upgrade of Infinity 24.1.3
Error : Calendar Name—Invalid value specified for Calendar Name. Value doesn't adhere to the Validate: pyXSS_Prevention_Validate
PDN Reference link : https://support.pega.com/support-doc/pega-platform-2423-patch-resolved-issues
|
INC-C23008 |
929811 |
Updated cross-site scripting protections related to calendar creation |
Attempting to create a calendar instance failed with the error "Invalid value specified for Calendar Name. Value doesn't adhere to the Validate: pyXSS_Prevention_Validate". This has been resolved by updating the pyXSS_Prevention_Validate rule logic. |
Error : Calendar Name—Invalid value specified for Calendar Name. Value doesn't adhere to the Validate: pyXSS_Prevention_Validate
PDN Reference link : https://support.pega.com/support-doc/pega-platform-2423-patch-resolved-issues
|
INC-C23008 |
929811 |
Updated cross-site scripting protections related to calendar creation |
Attempting to create a calendar instance failed with the error "Invalid value specified for Calendar Name. Value doesn't adhere to the Validate: pyXSS_Prevention_Validate". This has been resolved by updating the pyXSS_Prevention_Validate rule logic. |
Security Error : Calendar Name—Invalid value specified for Calendar Name. Value doesn't adhere to the Validate: pyXSS_Prevention_Validate
PDN Reference link : https://support.pega.com/support-doc/pega-platform-2423-patch-resolved-issues
|
HCA Healthcare
US
@AshwinY6 This issue happens because in 24.1.3 the security rule pyXSS_Prevention_Validate was changed and it is wrongly blocking valid calendar names, so calendar creation fails with the validation error. This is a known product defect and Pega has fixed it in the Pega Platform 24.2.3 patch by updating the validation rule logic. To solve it, upgrade your environment to 24.2.3 or later, or raise an SR with Pega Support and request the hotfix that includes the changes linked to INC-C23008 / INC-C1804 / INC-C26193. Do not try to bypass or customize
pyXSS_Prevention_Validateyourself, because that reduces security and is not recommended by Pega. After applying the patch or hotfix and clearing caches/restarting, try creating a new calendar again with a simple name (for example,BusinessCalendar) to confirm it saves without the XSS validation error.