Source of the configuration value in IncidentContext

endp · February 15, 2019, 9:36am

I created a service task, which invokes a JavaDelegate. The java delegate creates an incident like so

IncidentContext incidentContext = new IncidentContext();
incidentContext.setActivityId(execution.getCurrentActivityId());
incidentContext.setExecutionId(execution.getProcessInstanceId());
incidentContext.setProcessDefinitionId(execution.getProcessDefinitionId());
incidentContext.setConfiguration(“myConfig”);
IncidentEntity ie = createAndInsertIncidents(FAILED_JOB_HANDLER-TYPE, incidentContext, “”);
incidentEntity.createRecursiveIncidents();

On the cockpit page, an attempt to modify and ‘startBefore’ the serviceTask in error results in an another IncidentContext being created by Camunda. This incident context is populated with a configuration value and a jobDefinitionId. All other attributes of the instance are null.

I was expecting the configuration value in the IncidentContext generated by Camunda to be identical to the value I populated the incidentContext with intially when the incident was created… but it’s not. And that’s a problem because in the DefaultIncidentHandler class this configuration value is used to fetch the lists of incidents that can be deleted, see line 82 @

github.com

camunda/camunda-bpm-platform/blob/master/engine/src/main/java/org/camunda/bpm/engine/impl/incident/DefaultIncidentHandler.java

/*
 * Copyright Camunda Services GmbH and/or licensed to Camunda Services GmbH
 * under one or more contributor license agreements. See the NOTICE file
 * distributed with this work for additional information regarding copyright
 * ownership. Camunda licenses this file to you under the Apache License,
 * Version 2.0; you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.camunda.bpm.engine.impl.incident;

import java.util.List;

This file has been truncated. show original

Can you advise please ? Can you explain how Camunda populates the incident context when the task is modified, specifically in respect to the configuration… and also what am I doing wrong