How to debug a process without process start form?

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

Parents
  • A way I've handled this in the past is simply by making a "testing only" parent process model that calls the process model I want to test, as a subprocess, and I manually pass in some valid data as test parameters.

    Lately, however, I usually just test such processes by launching them from the context where they'll usually be launched (related action, etc), which in a dev environment should both be easy as well as not detrimental to any important data.  Then after launching the related action, you just find and monitor the newly launched process instance.

Reply
  • A way I've handled this in the past is simply by making a "testing only" parent process model that calls the process model I want to test, as a subprocess, and I manually pass in some valid data as test parameters.

    Lately, however, I usually just test such processes by launching them from the context where they'll usually be launched (related action, etc), which in a dev environment should both be easy as well as not detrimental to any important data.  Then after launching the related action, you just find and monitor the newly launched process instance.

Children

 Discussion posts and replies are publicly visible