Is my process name the same as my pool name?

Q&A
1

Quick question - is the name of my process the same as the name of the pool in my diagram for that process?

For context, I’m trying to make a link from my application homepage to start the process with:
/bonita/portal/resource/process/PracticePool/2.0/content/?id="+processDef[0].id
Where PracticePool version 2.0 is my pool. Also, my current process definition looks like:
../API/bpm/process?p=0&c=1&f=name=PracticePool

2

Yes. Pool name and version number correlate to process name and version number.

3

In that case, do you know why my link might be throwing up a “HTTP Status 400 - Bad Request” error?

4

It seems that you are missing a double quote at the beginning of `/bonita/portal/resource/process/PracticePool/2.0/content/?id="+processDef[0].id` 

Can you use the web browser tool (more precisely "network" tab) to get the exact URL called and share it with us? Can you also share the response to `../API/bpm/process?p=0&c=1&f=name=PracticePool` call?

Thank you

5

My URL is 'http://localhost:55033/bonita/apps/newemployee-v2/employee-records/'.

Changing the link to '"/bonita/portal/resource/process/PracticePool/2.0/content/?id="+processDef[0].id' turned up the same error, as did adding '../API/bpm/process?p=0&c=1&f=name=PracticePool' to my URL (is that what I should be doing to make a call?).

 

6

For reference, the full text of the error I get is:
 

HTTP Status 400 – Bad Request

Type Exception Report

Message Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:483)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:808)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.base/java.lang.Thread.run(Unknown Source)

Note The full stack trace of the root cause is available in the server logs.

Apache Tomcat/8.5.40

7

Just to make sure I provide an appropriate answer, can you clarify if you want to:

  1. provide a link from an application page to open the instantiation form of a process
  2. add a button in an application page that call the REST API to create a new instance (i.e. a new case) of a process

Thanks for the clarification.