I have encountered the same issue when following “Getting started tutorial”.
I think there is a problem when Bonita evaluates Target Url of the link widget. It might not support the syntax “{{var}}”.
I make a workaround for it as following:
In the property of the link widget (“Create new travel request” ), I set that property as an expression and point to the above variable newRequestFormURL.
Maybe of topic and should open a question, but when clic on the “Request new travel” button, in the app, nothing happens and a message is thrown on console: “Impossible to retrieve the process definition id value from the URL”
I found the processDef is just empty, so the process id can’t be extracted. Any idea based on your experience? Thanks in advance and sorry for the inconvenience.
1st. I have a button, not a link, or at least I don’t see any a tag. Clicking the button throws the message “Impossible to retrieve the process definition id value from the URL”, that I guess is derived from the following:
2st. I have that same issue. But, if I add a text field in the TravelTool page (in the UI Designer), and in the text property add {{session}}, I get the full session displayed on the app; and of course the field user_id is there. If I add another text field and put in the text property {{myUserId}}…voilá! A great 3 is shown (helen.kelly) So basically the value is ready.
But if I do the same with processDef…nothing is shown. Just and empty space; that value is really empty. So the id is not present, so the error shown is absolutely descriptive (“Impossible to retrieve the process definition id value from the URL”). But why that value is empty…when it shouldn’t…
My guess is myUserId is evaluated at some point when it is still not initialized and then the warning is generated. But the value is ready later on (for example, some GET requests are generate to request the myApprovedRequest and myPendingRequests, and the value userId=3 is there)
Sorry, don’t have an answer for the question you wrote, but it looks I’ll get there soon (hopefuly
1st:
sorry if I did confuse you, when I said inspected(I used Inspect Element function of Chrome over the button to see it’s HTML)
Are we able to use any variable at any moment in the code/output? are there any restrictions?
2nd:
I’ve tried every combinations you mentioned as text output, and they worked, the processDef only works if you try {{processDef[0].id}}, at least for me it worked.
Yes, not really sure if we are alone with this issue
Finally I’m stuck at the same point you are now. I can submit a new travel request, if I start the process clicking on Run in the Bonita Studio. But when I deploy the app, as soon as I click on the submit, a 404 error is thrown on the console.
I’m working on this, so if I find something, I’ll post it here
my shot is that the URL to the process is somehow wrong, and adding spaces to URLs isn’t a best practice which may lead to some errors, and “Travel Request” has a blank space!
A test that should be done(when I have the time I’ll do it) is rename “Travel Request” to “TravelRequest” and “Manager review” to “ManagerReview”, and of course rename all the remaining code in order to comply. This way the URL’s generated in the submit buttons will not have blank spaces and maybe the target page is found instead of 404 error.
I’ll report back when I do it ( can’t promise soon )
I am experiencing the same issue. When I run the process from studio, the submit button works as expected. When using the app through the URL, the submit button does nothing. What gives?
Experiencing same issue. Could it be that the form submitTravelRequest settings are amiss?
What should the value for submit button’s target url be? on creation of the form, it defaulted to /bonita.
Adding a request through Bonita “RUN” operation adds it ok, and I can see the item from Helen.Kelly’s portal session
but when I view the case (selecting from the icons as shown in above image), this is not shown under the applications page as shown below. http://screencast.com/t/C9bjWuNd2p3
Can you use the web browser developer tool to figure out which URL the submit button is trying to call?
Maybe it’s an error in the variable initialization or in the way the variable is bind to the widget in order to define the URL to call.
Bonitasoft empowers development teams with Bonita, the open-source and extensible platform to solve the most demanding process automation use cases. The Bonita platform accelerates delivery of complex applications with clear separation between capabilities for visual programming and for coding. Bonita integrates with existing solutions, orchestrates heterogeneous systems, and provides deep visibility into processes across the organization.
)