Skip to content

feat(diagram-converter): variableName filter not supported#1045

Merged
venetrius merged 6 commits intomainfrom
1040-remove-variableNamesFilter
Feb 27, 2026
Merged

feat(diagram-converter): variableName filter not supported#1045
venetrius merged 6 commits intomainfrom
1040-remove-variableNamesFilter

Conversation

@venetrius
Copy link
Member

@venetrius venetrius commented Feb 26, 2026

Related to: #1045

Pull Request Template

Description

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Test-only changes (no production code changes)

Testing Checklist

Black-Box Testing Requirements

  • Tests follow black-box testing approach: verify behavior through observable outputs (logs, C8 API queries, real-world skip scenarios)
  • Tests DO NOT access implementation details (DbClient, IdKeyMapper, ..impl.. packages except logging constants)
  • Architecture tests pass (ArchitectureTest validates these rules)

Test Coverage

  • Added tests for new functionality
  • Updated tests for modified functionality
  • All tests pass locally

Architecture Compliance

Run architecture tests to ensure compliance:

mvn test -Dtest=ArchitectureTest

If architecture tests fail, refactor your tests to use:

  • LogCapturer for log assertions
  • camundaClient.new*SearchRequest() for C8 queries
  • Real-World skip scenarios (e.g., migrate children without parents)

Documentation

  • Updated TESTING_GUIDELINES.md if adding new test patterns
  • Added Javadoc comments for public APIs
  • Updated README if user-facing changes

Checklist

  • Code follows project style guidelines
  • Self-reviewed the code
  • Added comments for complex logic
  • No new compiler warnings
  • Dependent changes have been merged

Related Issues

@venetrius venetrius force-pushed the 1040-remove-variableNamesFilter branch from dd50eaa to 66ca925 Compare February 26, 2026 07:39
delete-variable-event-not-supported.message=Variable event 'delete' is not supported in conditional event filter on '{{ elementId }}'. C8 only supports 'create' and 'update'. IMPORTANT: The condition will no longer trigger when variables are deleted. Please redesign if your process relies on delete events (e.g., set variables to null instead of deleting them).
delete-variable-event-not-supported.severity=TASK
delete-variable-event-not-supported.link=https://docs.camunda.io/docs/components/modeler/bpmn/events/
delete-variable-event-not-supported.link=https://docs.camunda.io/docs/components/modeler/bpmn/conditional-events/#variable-filters
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated links for conditional event in this PR as docs page only have been added last week.
Opening the links now returns 404 unless editing docs/components/ -> docs/next/components/ as the docs are only part of the next release.

I think this is acceptable. Other options would be to use staging doc link here and update it after next alfa or just before the minor release.

@venetrius venetrius marked this pull request as ready for review February 26, 2026 08:58
@venetrius venetrius changed the title chore(diagram-converter): variableName filter not supported feat(diagram-converter): variableName filter not supported Feb 26, 2026
Copy link
Contributor

@joaquinfelici joaquinfelici left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 👍
Added a couple of minor comments, but I'm approving.
Any doc update needed for this?

context.addMessage(MessageFactory.variableNameFilterOnConditionalEvent(elementId));
}

if (StringUtils.isBlank(variableEvents)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Should this be an else if? Or can both be true?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are checking different fields variableName vs variableEvents both values are optional so both checks can be true.

venetrius and others added 2 commits February 27, 2026 10:28
Co-authored-by: Joaquín <165814090+joaquinfelici@users.noreply.github.com>
@venetrius venetrius merged commit e5e8fc4 into main Feb 27, 2026
26 checks passed
@venetrius venetrius deleted the 1040-remove-variableNamesFilter branch February 27, 2026 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants