flowable / flowable/flowable-engine

Checking the activity id is not null in the history manager

Open
#2,519 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
7h 8m
Merged PRs (30d)
2

Description

In both implementation of HistoryManager interface (DefaultHistoryManager and AsyncHistoryManager) from the ProcessEngineConfigurationImpl when you are recording to the history a new activity instance you are saying that: _"Historic activity instance could have been created (but only in cache, never persisted), for example when submitting form properties"_

Because I've my own implementation of an HistoryManager to sync with an external source (ActiveMQ) I think your validation of activityId is not null it could be wrong.

![image](https://user-images.githubusercontent.com/30126925/88291339-f9e4e880-ccef-11ea-8189-5f245af745f5.png)

I think you wanted to validate the activity entity id, the primary key if persisted, and not whether this activity has an identifier or not.
So instead of activityInstance.getActivityId() != null maybe you want to check if activityInstance.getId() != null

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.