-
15. Re: 256 character limitation in REST API response
Carlos, could you please specify what REST resources you use for your cases and what is the actual result of the call and what is expected. If it's not a history resources they should not be truncated. So if that's the case it's certainly a bug.
HTH
-
16. Re: 256 character limitation in REST API response
I took a look at RuntimeResource.java in package org.kie.services.remote.rest and found the section for the "WithVars methods" and they use VariableInstanceLog instances. Also the call "/process/instance/{procInstId: [0-9]+}/variables" uses the same getVariables
method. I could not find a REST call to get the complete variable contents.
Thanks for your help.
-
17. Re: 256 character limitation in REST API response
you're right, currently all access to process variables is done via history log so it all will suffer from the same limitation. I opened jira to provide access to actual instances of process variables, as long as process instance is active.
HTH
-
18. Re: 256 character limitation in REST API response
Maciej Swiderski wrote:
... we plan to make it configurable where you can decide yourself if the data base that you use allows to store bigger content and you have configured database properly.
I could not find an issue for this in JIRA? Is there one, or should I create it?
-
19. Re: 256 character limitation in REST API response
jira is already there: https://issues.jboss.org/i#browse/JBPM-4221