After upgrading our test instance from Washington to Yokohama, we encountered several issues in Workflows located within a custom application Scope. All of the issues apper to stem from a malfunction in comparisons string-type fields values.
1. The trigger fires regardless of the value in SAP active field, it activates even when the field is empty.
2. The trigger fires correctly when the Name field is updated, but then flow fails to detect changes in individual fields.
3. The subflow retrieves transaction IDs from an external application and compares them against existing entries in the sc_req_item table to avoid creating duplicate RITMs.
However, new RITMs are not being created because the flow incorrectly identifies every incoming ID as already present in the table- even when it's not.
It appears that in all three cases comparation between two string values are not functioning correctly: the flow treats them as equal, even when they are clearly different.
Has anyone experienced similar issues, and if so, how did you resolve them?
p.s. Everything was working correctly befor the upgrade (and continues to work as expected in the prod instance, which is still running the Washington release).
we have issue in Yokohama testing on string comparison when a choice field is involved.
As example - checking if a request is approved using the sc_request.approval field.
- Xanadu check is approved = approved (and evaluates as true)
- Yokohama check is Approved = approved (and evaluates as false)
Confirmed choice list entries for sc_request.approval is the same between versions (Label = "Approved", Value = "approved"
Will be logging a case for this and will report back. Can update this flow with script, but worried about other flows where not detected
