Case Sensitivity on Data Structures

Unknown

Case Sensitivity on Data Structures

Unknown

We have set up a development environment with version 6.8 installed and have migrated some of our workflows from version 5.5.1 for testing. One issue we have noticed is regarding CaseDataStructure.

There are a few data members in this structure but in particular correlationID and relatedEntityID (exactly as written). We have an api that uses the flow execution service Start Flow With Data that passes in these to parameters as GUIDs and kicks off the workflow. This works perfectly fine in version 5.5.1 however in 6.8 these values are passing as null. We have not changed the api or data structure or any supporting flows between versions.

The only thing of note is that the api passes the parameters as CorrelationId and RelatedEntityId, so we are wondering if 6.8 is more strict when it comes to case sensitivity, or is there something we are missing?

Using postman we can successfully hit the decisions endpoint by passing in correlationID and relatedEntityID (exactly as written) but if we change the casing on these parameters the call will fail.

We have not experienced this issue in 5.5.1.

What we need to know is firstly is our assumption correct and why does it not seem to matter in 5.5.1 and secondly is there any suggestions on how to resolve this that would avoid having to change API code or data structures?

If we were to change the data structure to match the api call what would the ramifications be on inflight data or can this even be done?

Unknown

Ive tested this in 6.8 by calling a default behavior Flow to create a Case Entity with two string input parameters mapped into a pair of string parameters in the new Case Entity. Renaming the names of the existing parameters in the Case Entitys type definition did not cause any mapping issues for the parent Flow, create new columns in the types table, or affect an in-flight Assignment following the Create step of the Case Entity.

If your use case for calling the endpoint in question is to create new Case Entities and the flow being called does not contain Assignments with either inputs or outputs with mappings for the Flows input parameters (excluding subflows), it may be simpler to change the spelling of the input parameters of the flow to match that of the calls in your external code. Doing so would require re-mapping of the renamed inputs in only that flow.