Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timer Event is not recognized in the differ module #15

Open
stocksanjan opened this issue Sep 16, 2022 · 5 comments
Open

Timer Event is not recognized in the differ module #15

stocksanjan opened this issue Sep 16, 2022 · 5 comments
Labels
backlog Queued in backlog bug Something isn't working good first issue Good for newcomers spring cleaning Could be cleaned up one day

Comments

@stocksanjan
Copy link

Describe the Bug

When we compare two models, and there is a difference in the "duration" configuration in the timer event, then bpmn-js-differ neither populate in the "list of changes" section nor show it on the difference on the models.

Steps to Reproduce

  1. create two BPMNs (clone each other) with timer event with default event duration as PT1S
  2. take the second BPMN file and change the above same event's duration to PT15S
  3. upload these two BPMN Files in the https://demo.bpmn.io/diff, to see if the tool can alert the timer difference.
  4. diff tool doesn't alert a difference at the timer event.

Expected Behavior

  1. Diff tool is expected to show the different between two models
  2. Tool may have to high light there is a difference in timer event node.
  3. Tool may have to list this difference in "List of changes" panel.

Environment

  • Host (Browser/Node version: Version 105.0.5195.125 (Official Build) (64-bit)
  • OS: [e.g. Windows 7]: Windows 11
  • Library version: [e.g. 2.0.0]

Sample BPMN Files.zip

@stocksanjan stocksanjan added the bug Something isn't working label Sep 16, 2022
@marstamm
Copy link

Hi, thank you for opening this issue. I can reproduce this. Moving to Backlog for now.

As this is currently not a high priority item for us, I would like to encourage you to provide a PR for this issue. I investigated a bit and maybe you find my findings helpful to get started.

Root Cause

We only track the bpmn attributes as defined in

'bpmn:Participant',
'bpmn:Collaboration',
'bpmn:FlowElement',
'bpmn:SequenceFlow',
'bpmn:MessageFlow',
'bpmn:Participant',
'bpmn:Lane',
'bpmn:DataAssociation'

The Timer is defined in bpmn:TimerEventDefinition, which is not part of the list.

@marstamm marstamm added the backlog Queued in backlog label Sep 21, 2022
@stocksanjan
Copy link
Author

hey @marstamm,

Thank you for the reply, yes I have noticed it is not a part of tracked attributes, I will be modifiying the code to include that, Thanks for the response once again.

@nikku nikku added spring cleaning Could be cleaned up one day good first issue Good for newcomers labels Sep 29, 2022
@stocksanjan
Copy link
Author

@marstamm Thank you for providing this open source, learnt little bit on how things work with BPMN.js, I have modified the local snippet as per my needs, and now the code recognize these events including Camunda ones too. Thanks.

image

@nikku
Copy link
Member

nikku commented Sep 30, 2022

Thank you for providing this open source

And you plan to contribute that back?

@stocksanjan
Copy link
Author

@nikku I need to do some unit test, and will keep you posted as per the output. Thanks.

@bpmn-io-tasks bpmn-io-tasks bot removed the backlog Queued in backlog label Jun 17, 2024
@nikku nikku added the backlog Queued in backlog label Aug 29, 2024 — with bpmn-io-tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Queued in backlog bug Something isn't working good first issue Good for newcomers spring cleaning Could be cleaned up one day
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants