Hi,
I have a process model where I do not have a process start form. The reason for this is that the process should be triggered when a button is pressed in a certain record. The user should press the buton and the process is supposed to be triggered. This works fine.
The problem I encounter is that I am not able to debug this process model. When I start the debugging process I get the error that 'the record to be saved must not be null'. The reason this error occurs, in my estimation, is that the process model does not have any context. The model normally reads data from a CDT and performs actions based on that data. When debugging it does not know what data it should get, so gives the null error.
My question is as follows: how can I debug this process model? The interface layout has a similar situation, and as solution has the option to fill in 'Test inputs'. Is there a similar option in the process model debugging interface? Or do I misinterpretet this entirely and is there something else ongoing?
Kind regards,
Bart
Discussion posts and replies are publicly visible
Hi Bart
Your node is obviously expecting a populated datatype. You can add a rule to the pv! that you're using to create/populate this value. This should be removed before you finally publish the model (best practice suggests that you not assign default values to pv!s directly as it's not always obvious to the next developer how the value is getting set)
To add to Stewart's answer, you can do this by adding a value in your process properties - see the example below: