Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-1219

Forms - Ability to flush the form state into the model on demand

    XMLWordPrintable

Details

    • 0
    • 0% 0%
    • 2020 Week 07-09 (from Feb 10)

    Description

      Actually the way forms are integrated with Stunner, so with both BPMN and DMN editors as well, is by callbacks - once a field is changed (and valid), the forms API runs a callback which delegates the execution of a command to Stunner.

      Due to new requirements for kogito (channels), there is the need for exposing the ability to flush the foms state via API. So instead of forms calling Stunner, Stunner will use the Forms API to force flushing the state, which will update the underlying model as well, once the user saves the process.

      The root issue which is causing the need for this, is properly explained by pefernan@redhat.com :

      the point is that forms are propagating the property changes into the model when they detect a change event fired by the widget (errai-data-binding world!), on textboxes/text areas this happens when the widget looses the focus. The big issue is that users on vscode can make changes on the properties panel and save the diagram without making the change event to happen.

This flush mechanism is only to force a flush to happen BEFORE the save on vscode is finally executed. So any pending change will be pushed into the model prior to saving the diagram.

So this is only the first change before the final integration in stunner and vscode extension is done.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-420 Text in BPMN doesn't save when there are no changes in the diagram

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-987 VsCode editor - process id not saved/updated

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-279 Stunner - you should to deactivate property to save it's value

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-990 VSCode - BPMN modeler saving data assignments does not save process model

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rh-ee-pefernan Pere Fernandez Perez
              romartin@redhat.com Roger Martinez
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: