Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 6.4.4
Affects Version/s: 6.4.2
Component/s: Business Central
Labels:
- support

Fix Build:
CR1
Workaround:

Workaround Exists
Workaround Description:

Hide

use other endpoints such as the rest query API:

http://localhost:8080/business-central/rest/query/runtime/process?var_v=v%20with%20space

Show
use other endpoints such as the rest query API: http://localhost:8080/business-central/rest/query/runtime/process?var_v=v%20with%20space
Steps to Reproduce:
Hide

create a process with a single variable (v)

create an instance give the variable value with space (v with space) and another one which variable value has no space (nospace)

try to use the endpoint for each variable value

This works: http://localhost:8080/business-central/rest/history/variable/v/value/nospace
This returns 404: http://localhost:8080/business-central/rest/history/variable/v/value/v%20with%20space
Show
create a process with a single variable (v) create an instance give the variable value with space (v with space) and another one which variable value has no space (nospace) try to use the endpoint for each variable value This works: http://localhost:8080/business-central/rest/history/variable/v/value/nospace This returns 404: http://localhost:8080/business-central/rest/history/variable/v/value/v%20with%20space

Sprint:
jBPM sprint 3

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The endpoint /history/variable/

{varId}

/value/

{value}

always return 404 when querying variable that contains spaces in the value.

The problem is the regex in path variable specification ins the JAX-RS endpoint. It does not allow spaces:

    @GET
    @Path("/variable/{varId: [a-zA-Z0-9-:\\._]+}/value/{value: [a-zA-Z0-9-:\\._]+}")
    @RolesAllowed({REST_ROLE, REST_PROCESS_RO_ROLE, REST_PROCESS_ROLE})
    public Response getVariableInstanceLogsByVariableIdByVariableValue(@PathParam("varId") String variableId, @PathParam("value") String value) {

causes

RHBPMS-4794 History REST endpoints not behaving correctly on WAS

Verified

Assignee:: Mark Coble (Inactive)

Reporter:: William Siqueira

Tester:: Dominik Hanak

QA Contact:: Dominik Hanak

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2017/04/12 7:40 PM

Updated:: 2021/10/24 5:20 AM

Resolved:: 2017/05/26 2:51 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates