I’m facing an issue with the standard pyState property (defined at the base class level), which is configured with a Field Value table type.
When I receive a state value from an external response (for example, "OR") and set it in a Data Transform, the value gets automatically converted to lowercase ("or").
Because this property is referenced in multiple places (including When conditions and @IsInPageList() checks), the case change is impacting comparisons due to case sensitivity.
Can you please check if there is another field value present in the application hierarchy or not?
Hi This is been sorted after checking with pega gcs engineers.
we’ve identified the root cause: The pyState field value has been overridden in the PegaAppCA ruleset where the value for Oregon state code is configured as “or” instead of “OR”.
To resolve this issue,
Additionally a user story has already been created to address this issue at the product level, which will include a cleanup of pyState field values.
pyState generic enough for global use (across different countries and administrative levels),
In my opinion, we should move away from a “hard-coded” US-centric design states.
