Currently supported features
More detailed description of required functionality:
- InputValueSetModel defines three types of parameters:
- properties (e.g. atomic values)
- objects
- lists of objects
All those values are identified "by name".
URL requirements
According to my current understanding parameter transfer should be handled like this:
- for properties, the (name, value) pair will be transferred using an HTTP GET parameter
- for objects, the (name, primary key) pair will be transferred using an HTTP GET parameter
- for lists, a series of (name_index, primary key) pairs will be transferred using HTTP GET parameters (probably also transferring the length of the series in an additional parameter)
Additionally we need to use some kind of CRC in order to prevent client side manipulation of the parameters.
Transfer requirements
Currently there is a call
processParameterizationService.handleProcessStartStateParameterValues(requestContext, transitionModel);
in TransitionServiceImpl}. The current {{ProcessParameterizationServiceImpl only retrieves parameters from the session context (and immediately deletes them). The current code block
String sessionKey = getSessionKey(startStateModel);
Map<String, Object> values = (Map<String, Object>) requestContext.getSessionContext().getProperty(sessionKey);
if (values == null)
{
throw new RequestContextProcessingException("Failed to locate the input parameter values for process start state '" + startStateModel.getId() + "'.");
}
requestContext.getSessionContext().setProperty(sessionKey, null);
should be expanded to alternatively retrieve the parameters from the HttpServletRequest if none are contained in the session and only then throw an exception if the request parameters also are not correctly defined (by either not being defined at all or by having an incorrect CRC).
New Feature
Closed
Major
Currently supported features
More detailed description of required functionality:
All those values are identified "by name".
URL requirements
According to my current understanding parameter transfer should be handled like this:
Additionally we need to use some kind of CRC in order to prevent client side manipulation of the parameters.
Transfer requirements
Currently there is a call
in TransitionServiceImpl}. The current {{ProcessParameterizationServiceImpl only retrieves parameters from the session context (and immediately deletes them). The current code block
should be expanded to alternatively retrieve the parameters from the HttpServletRequest if none are contained in the session and only then throw an exception if the request parameters also are not correctly defined (by either not being defined at all or by having an incorrect CRC).
Currently supported features
More detailed description of required functionality:- InputValueSetModel defines three types of parameters:
- properties (e.g. atomic values)
- objects
- lists of objects
All those values are identified "by name".URL requirements
According to my current understanding parameter transfer should be handled like this:Transfer requirements
Currently there is a call