Hi everyone,
Once I start the debugging process for testing, when I type the information on the form, the information disappears before I finish typing and submitting it. Does anyone have had this situation before?
is it a configuration issue on the object that triggers the form?
Can you pls support.
Regards,
Discussion posts and replies are publicly visible
Make sure you are assigning the rule input values to process variables use above screenshot for reference.
Thanks a lot for your reply,
Yes, I tried what you had suggested, the input text is ok now, but when I refresh to check if the information went through the process I get stuck again.
These are my variable in the start form:
I noticed, in the screenshot you shared, the value for the rule input vehicle only reads vehicle.
when I use the expression editor to write = pv!vehicle. this is what I get.
this is the error I get when I refresh to update the process flow
This is the rule input as type AA_veichle and array check is not selected.
Similarly, in the below screenshot the type of PV vehicle is AA_veichle and multiple is NO.
Configure these variables you will be able to select.
Hi!
thanks a lot for your kind support, and for taking the time to review. Unfortunately, I have the same as you sent me in the screenshot, but still, vehicle is not available to select on the process start form.
I would suggest you to try to use a new variable but create it by clicking on the plus simbol beside the column value this new variable will have the same data type that your interface needs it could work
It didn´t work.
I got stuck on my learning path, seems I have everything the tutorial is telling me, already checked on the different possibilities. is there any error in the study material ? pls help! I don´t know how to fix the error.
An error occurred while trying to write to the entity "AX_Vehicle" [id=6d5c5950-65a2-4395-b56c-146a8b22e9f5@4749, type=AX_Vehicle (id=3542)] (data store: AX Data Store). Details: java.lang.IllegalArgumentException: The record to be saved must not be null: TypedValue[it=3542,v=<null>] Data: TypedValue[it=3542,v=<null>]
Try to clear the interface from start form and then replug it again when you will select the interface after that a dialogue box will appear select true and if your process variables are correct they will automatically match with your rule inputs.
unfortunally, it didn´t work. thanks a lot
I don´t find the error.
Hi Monica, I had mentioned this in my previous response as well. You can see that the column with header "Parameter?" has response as "No" for vehicle pv. This should be yes. Please update that and the variable would start showing up to be added to start form.
You can see that you are able to give the "cancel" variable to the form but not the other two. This parameterized property is needed to get data when a process needs some input before initializing. It is also important for all your inputs on a start form. Not required for a regular user input task.
Hello!!
Thank you so much!! yes !!!! , that made it through. thanks for the teaching. for the other pv approvalDecision, does the parameter has to be YES also?
If it is not passed to the start form, then no. A variable only needs to be parameterized when you need to populated data in it before the process even starts. Examples:
1. When you use start form. Process instance is only triggered after the start form is submitted.
2. When a process starts from another process or interface and needs some data from the main process or interface.
Thank you so much for your input and interest. I really appreciate it!!
valuable teaching. . Regards.