Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog (opens in a new tab), and this project adheres to Semantic Versioning (opens in a new tab).
Known Issues
- When importing a model xml file, the summary will be overwritten
- The BPMN diagram does not show up for unpublished models at Jira issues
- AP.jira.openIssueDialog does not work as expected see bug report (opens in a new tab)
[2.5.2] - next up
FIX
: Remove Issue Hierarchy feature
[2.5.1] - 2024-02-16
FIX
: Remove double link at GeneralPageFIX
: Remove issueGlance from connect-configFEAT
: Open Swim-lane Filter when click on the laneFEAT
: Auto-create next issues also in agile modeFEAT
: Create comment to pi if a decision cannot be madeFIX
: Unselect Issue Type does not work properly in BPMN editorFIX
: Auto starting a PI from issue type mapping creates the PI but not the first activityFIX
: Activities should be subtasks of the pi (does not work)
[2.5.0] - 2024-01-05
FEAT
: disable version control in settingFEAT
: add reporting pageFEAT
: move process instance list to Jira filterFEAT
: extend Flower REST API: createProcessInstance and create certain (or all) activitiesFEAT
: add BPMNView page to better visualize large modelsFEAT
: split build to improve loading performanceFEAT
: launch successor task automatically even in agile modeFIX
: switch to strict mode and back was not workingDEPS
: dependency updatesTEST
: extend unit tests to rest api
[2.4.0] - 2023-11-30
FIX
: unpublished models cannot be startedFEAT
: DMN Decisions on Select FieldsFEAT
: remove the Description Text (replace it with something like {Flower Auto Text} see user manual)FEAT
: Flower REST API
[2.3.4] - 2023-10-20
FIX
: AMS Ticket (opens in a new tab)FIX
: Naming of Jira tasks is too large: remove PI nameFEAT
: application scope added: ACCESS_EMAIL_ADDRESSESFIX
: move bpmn.io logo into view boxFEAT
: customer onboarding messaging optimized
[2.3.3] - 2023-10-06
DEPS
: dependency updates (09627dc) (opens in a new tab)FEAT
: entity Property flowerLane addedFEAT
: processOwners added to Flower settings(9592826)FIX
: model export broken (SUPPORT-192) (opens in a new tab)FIX
: order model list by created DESC (4ae4d8b) (opens in a new tab)FIX
: minor bugfixes
[2.3.2] - 2023-08-26
FEAT
: map jira issue type with Flower process model (c5f5c26) (opens in a new tab)FIX
: BPMNView cannot display collapsed subprocesses due to overlay issues
[2.3.1] - 2023-07-08
FEAT
: introduce strict mode (a61e6c6) (opens in a new tab)
[2.3.0] - 2023-06-08 DMN
FEAT
: DMN modeler integrated (2af39d9) (opens in a new tab)FEAT
: DMN evaluation implementedFEAT
: export dmn modelFEAT
: link bpmn gateway with dmn decision tableFEAT
: decision Control for Issues based on DMN decisions
[2.2.1] - 2023-05-1
FEAT
: cacheable app iframe (9685f74) (opens in a new tab)
[2.2.0] - 2023-04-06
FEAT
: create client record based for each installFEAT
: PI View in portal - rework marginsFEAT
: start unpublished modelsFEAT
: test with company/team managed projectsFEAT
: better highlite current nodeFEAT
: create hirachyal issues like Epic-Story based on sub-processes in bpmn
[2.1.2] - 2023-03-19
FEAT
: expanded Sub-ProcessesFEAT
: issue Hierarchies
- add Parent Field to Activities in Modeler
- make Sub Activities (from collapsed Subprocesses) launchable
- process Instance View as Tree Table
- make Initiative ticket root level
FIX
: createIssueView format errorsFEAT
: set Hierarchy InitiativeFIX
: createIssueView Filter only not started nodesFEAT
: modeler remove parent select box
[2.1.1] - 2023-02-17
FEAT
: exporting an unsaved model produces an error message.FEAT
: apply Jira issue hierarchy when creating a Flower entity to persist structures like Epic -> Story and Task -> Sub-taskFEAT
: create new Model function uses wrong template
[2.1.0] - 2023-02-06
FEAT
: added mandatory field validation when creating an epicFEAT
: added Model Version Navigator to navigate through previous versionsFEAT
: made Jira process/type editable when launching a process instanceFEAT
: implemented WorkflowCondition to allow transition only if all linked issues are resolvedFEAT
: implemented WorkflowValidator to allow transition only if all linked issues are resolvedFIX
: BPMNWrapper now only works with one lane-pool. Models with multiple pools have no bpmn control in the start workflow screenFIX
: ProcessInstanceView page now refreshes after a popup has closedFIX
: Optimized Build das not work with bpmn-jsDEPS
: library updatesFEAT
: added functionality to createJiraTask:
- Jira field description is now set to bpmn element documentation
- Added Blocked By link when creating a new task
- Added previous nodes field to flower properties
- Added next nodes field to flower properties
FEAT
: BPMN Templates updatedFEAT
: User manual updated
[2.0.2] - 2022-11-09
- Activate license support
- Set mandatory fields when creating Jira issue (DC only)
- After the Settings modal, properties are not updated on repository page
- Help Modal update links
- Disable Reporting Button in Repository
- Settings Page: repository link: history object not there because no routing
- Redirect /flower/page => /page
- Set Project/IssueType in Edit Mode Page Properties Panel
- Migrate unpublished models
- Make existing instances visible (existing tasks should be visible at the pi)
- Disable start-workflow-button while starting PI to avoid creating multiple pis
- IssueView: make current activity visible
- Make the Flower icon red Cloud
[2.0.1] - 2022-11-03
- RepositoryPage: bpmn pictures are not rendered correctly in cards
- RepositoryPage DC: onboarding no scrolling available
- ReactGA4
- Remove Axios from client libs
- PanelLeft DC: page padding-bottom is by far too large
- PanelLeft Cloud: the model has no status
- CreateProcessInstance produces undefined in summary
- StartWorkflowModal "Click to enter the value" instead of instance summary
- adjust token-simulator look and feel/CSS
[2.0.0] - 2022-11-01
- Flower Data Center version added
- Remove Redis
- Remove middleware
- Remove form-io and forms at all
- Remove the unsupported nodes button
- Rework http Error handling to be in sync with dc
- Token Simulation added to EditModelPage
- Save bpmn at instance (Flower)
- Clean up issue properties. merge all in one
- Show issue status in bpmn-view
- Add flower templates as a label in the repository list (remove template button)
- Update bpmn-js-properties-panel
- Repository
- Remove label filter for dc
- Rework templates
- Create a plain model as a template
- Check Onboarding
- CheckSettingsModal
- ProcessInstancePage
- Remove edit header
- Hide non-task-activities
- Beautify table rows for started tasks
- Edit summary
- BPMNView fitUpperLeft
- Deal with issue-create errors (permissions) (eventuelly save errors at pi)
- Show priority in table view
- Make table toggable
- Fix create all button
- Rework Onboarding
- ProcessListPage
- Rework onboarding
- ProcessInstanceListPage
- Check Onboarding
- PI-Status Column
- Make Summary editable and make labels savable at the EditModelPage Properties Panel- IssueView web-panel integration (opens in a new tab) Settings page- Rework Onboarding
[1.2.1] - 2022-07-01
- HTTP and Jira Mock have been changed to work with the Jira AP api
- MQ Engine to be running without Redis. switch on/off in flower/conf
- Decision Handler moved to MQ in one method
- This changelog added
- Added Flower-core/spec/mock test spec for mock
- nNw localhost:3000/demo/ endpoint to run with mock backend
- Added Puppeteer tests added
- Added test event added to test HTTP functions in graalvm
- Added Flower core build script to create a graalvm runtime
[1.2.0] - 2022-01-22
- Added Test Coverage with Jest
- Changed Build with parcel.io
- Removed web pack
[1.1.6] - 2021-12-06
- Diagram ausrichtung in der jira issue ansicht adjusten
- Formular verschwindet manchmal
- Add process instance name to the Flower task summary
- Add the model name to the process instance summary
- At the repositories tab select box, some values cannot be selected
- Add the Jira task status to the BPMN diagram
[1.1.5] 2021-11-20
- Tested user interface in chrome
- Indicate at the Jira ticket at which Flower type we are (model, instance, or task)
- Hardening the user interface
[1.1.0] - 2019-12-01 - 2022-01-22
- We had many Flower releases which are not documented in this file## [1.0.0] - 2019-12-01
- Initial Flower release