Discussion

Variable "could not be resolved"

Workflow Forms

Updated February 9, 2021

posted on February 8, 2021

Hi
We are working on a process that reads variables from an external Forms server to start a process on the internal server, we are having a problem, a variable that is in the internal form has the name "No._of_Document", in the process when it is started manually it works perfectly, but when we try to pass the value from the external server it gives us the error that it "could not be resolved".

This is a fairly large and complex process with several sub-processes and the variable in question is the identity document number, it is in all the forms so we want to do everything possible not to have to change it.

Any help is appreciated

Thanks

Ricardo Cairo

0 0

Comments 5
Follow-Ups 0

replied on February 9, 2021

Hi Jason

It seems that when the upgrade from version 9 to version 10 was executed, this error was not detected.

variable error 2.jpg (46.41 KB)

| Download

0 0

replied on February 9, 2021

That would certainly explain the problems you've been having. I'd still recommend going through and updating variable names to conform to the current syntax rules.

0 0

replied on February 8, 2021

Hi Jason

This process was originally prepared in version 9.2, it could come from there, but the variable is currently working, pass the process to another server and the server accepts it as valid.
A screenshot of the field is attached.

variable error.jpg (26.05 KB)

| Download

0 0

replied on February 8, 2021

It sounds like there was a problem when the system was upgraded to 9.2 because that is when the naming syntax changed and variable names imported from older versions were supposed to be updated automatically.

List of Changes for Laserfiche Forms 9.2 - Knowledge Base

The second item under "Fixes and Changes" mentions how period characters were supposed to be replaced by underscore characters, but for whatever reason it doesn't seem like that happened in your environment.

The Set Business Process Variables activity was added in Workflow version 10, so it is most likely following naming syntax rules for Forms 10 and expects that those updates would have been made with version 9.2.

Regardless of whether or not the process still works within Forms, that naming syntax is no longer supported so it is almost certainly the reason Workflow does not recognize it as a valid variable.

0 0

replied on February 8, 2021

Are you sure it isn't just misspelled in the workflow process?

Forms variables do not allow "." characters, so if the workflow side says "No._of_Document" it is likely the actual variable name in Forms is No_of_Document or No__of_Document without the period.

2 0

You are not allowed to follow up in this post.

Discussion

Discussion

Variable "could not be resolved"

Comments 5

Follow-Ups 0

Sign in to reply to this post.