Unsupported value type 'json'

Camunda 7 Topics Discussion & Questions
1

I post JSON variable task data over REST API and the response is:
{“type”:“InvalidRequestException”,“message”:“Cannot complete task 115: Unsupported value type ‘json’”}

I have use JSON variable type now already half year but now I get this error first time.

Camunda 7.6.0

ValueTypeResolverImpl defined types:
public ValueTypeResolverImpl() {
addType(BOOLEAN);
addType(BYTES);
addType(DATE);
addType(DOUBLE);
addType(INTEGER);
addType(LONG);
addType(NULL);
addType(SHORT);
addType(STRING);
addType(OBJECT);
addType(NUMBER);
addType(FILE);
}

So, it looks really, json type disappeared!? Or which type i should use instead of json?

Data itself what i post looks:
{“variables”:{“json”:{“value”:“{"wzegx9tugx":"kkkk","reviewerselection":"filevalidated","whichseasonyoupreferforvacation":"Sommer","golfregistration":true,"bf96wosxd52":"xx","fileuploadmocuprequirement":[{"storage":"url","name":"4editregis-d8737b95-33c2-4a86-8737-6aef8247d2a6.png","size":39432,"type":"image/png"}]}”,“type”:“json”}}}

Thanks!

2

I found the problem. Problem was in our spring configuration where we tried to configure different database datasource and instead using Camunda configuration factory we created new instances (which was mistake).

So, case is closed :slight_smile:

The oldschool spring configuration itself with elastic search integration and history event handler looks:

<beans xmlns="http://www.springframework.org/schema/beans"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:context="http://www.springframework.org/schema/context"
	xsi:schemaLocation="http://www.springframework.org/schema/beans
                         http://www.springframework.org/schema/beans/spring-beans.xsd
                         http://www.springframework.org/schema/context
                         http://www.springframework.org/schema/context/spring-context-2.5.xsd">

	<!-- bind the process engine service as Spring Bean -->
	<bean name="processEngineService" class="org.camunda.bpm.BpmPlatform"
		factory-method="getProcessEngineService" />
	<bean name="processEngine" factory-bean="processEngineService"
		factory-method="getDefaultProcessEngine" />
	<bean id="repositoryService" factory-bean="processEngine"
		factory-method="getRepositoryService" />
	<bean id="runtimeService" factory-bean="processEngine"
		factory-method="getRuntimeService" />
	<bean id="taskService" factory-bean="processEngine"
		factory-method="getTaskService" />
	<bean id="historyService" factory-bean="processEngine"
		factory-method="getHistoryService" />
	<bean id="managementService" factory-bean="processEngine"
		factory-method="getManagementService" />

	<!-- bootstrap the process application -->
	<bean id="processApplication"
		class="org.camunda.bpm.engine.spring.application.SpringServletProcessApplication" />

	<context:annotation-config />

	<bean class="org.mmmmmm.camunda.Starter" />
	<bean class="org.mmmmmm.camunda.SpringApplicationContext" />

	<bean id="userTaskHistoryEventHandler"
		class="org.mmmmmm.camunda.handler.UserTaskHistoryEventHandler" />
	<bean id="elasticHEH"
		class="org.mmmmmm.camunda.handler.HistoryEventHandlerElastic" />

	<bean id="processEngineConfiguration" factory-bean="processEngine"
		factory-method="getProcessEngineConfiguration">
		<property name="processEngineName" value="default" />
		<property name="dataSource" ref="dataSource" />
		<property name="databaseSchemaUpdate" value="true" />
		<property name="jobExecutorActivate" value="false" />
		<property name="historyEventHandler" ref="elasticHEH" />
	</bean>

	<bean id="dataSource"
		class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy">
		<property name="targetDataSource">
			<bean class="org.springframework.jdbc.datasource.SimpleDriverDataSource">
				<property name="driverClass" value="org.postgresql.Driver" />
				<property name="url"
					value="jdbc:postgresql://postgres_host:5432/camunda" />
				<property name="username" value="***" />
				<property name="password" value="***" />
			</bean>
		</property>

	</bean>

</beans>
3

@Erki_Kriks can you provide implementation for the class UserTaskHistoryEventHandler

4