Hi! I am facing a problem in my process model. The fact is that, when I run the process for the first time, the fields introduced by the user (interface from start form) are saved correctly. But when I finish the process and I try it a second time, the values of the process variable are not overwritten ( they are correctly written in my record, but it is like they are not saved in the process model, so all my logic runs according to the first time introduced fields). I have some captures of the problem:
Fields introduced for second time
But when you search in process variable, the recordFact fields are not updated
The most confusing thing is that, even though it seems they are not saved correctly, the updates appear in my records
Any help would be useful
Thanks a lot
Discussion posts and replies are publicly visible
Some questions:
Which field is your primary key?
What do you do in the form before submit?
Can you share a screenshot of the process model?
My primary key is idFactura
In the process model, I start with an invoice interface, in which the user enters the field values. After that, I compare some of the values with conditions (XOR logics) to define an status for the invoice:
-First interface
- Process Model
Additionally, I have this configuration in my connections between nodes:
It seems like you allow the user to enter the primary key value. Is there a specific reason to do so?
Is there a specific reason to "Keep process variables synced"? Are you aware what this is doing?
Yes, I want to allow the user to enter it. On the other hand, I realised that the problem was to have checked the "keep process variables synced" (that was why my process variable was not updating).
After changing this, my logic is not working in the XOR nodes, when I try to compare values linked by relationship. I don´t know why the relationship is not working there. I also tried to return the value of the related record in my actual record (as a new custom record field), but it doesn´t work too.
I dont know if I have to pass the relationship in another way. But in the first "Write record node" inputs, inside the RecordFact, the relationship appears (just before the XOR node)