Tuesday, 18. April 2017

Jakobshorn Sprint 25: Animated Case Map

In this sprint we focus on the animation of the Case Map, so that we meet the slogan “see how it works”, as we know it from the process designer.

Additionally, we enhance the Case Map functionality with several features, e.g. we introduce a model validation, an API to get sidesteps of a running Case Map and an easy way to access current business case data.

List of planned stories:
XIVY-1719 Animated Case Map
XIVY-1823 CaseMap Model Validation
XIVY-1683 Provide API to get available sidesteps for a certain business case and session
XIVY-1821 Configure Name, Description, Activator of Tasks started from the Case Map using Business Data
XIVY-1847 Automatically provide Case Map variables with the name declared on the @BusinessCaseData annotation
XIVY-1734 Nice Process Selection UI in Case Map
XIVY-1724 Handling Errors in the execution of a Case Map
XIVY-1842 Leave Mars - Q&A
XIVY-1860 Refactor Workflow and Case Map Engine to reduce dependencies and complexity (Part 2).


Tuesday, 28. March 2017

Jakobshorn Sprint 24: Business Data featuring Case Map

In this sprint we enhance the Case Map with Business Data. First we introduce an easy API to manage business data in the context of a business case - so the key of a business data has no longer to be managed manually - the Business Data entry is automatically linked to the current Business Case. Furthermore this allows to define pre-conditions in the Case Map which depend on the business data.

Additionally, we enhance the Case Map UI/UX and go again a step further with the easy to use REST Client Inscription Mask.

List of planned stories:
XIVY-1802 Reuse HTTP Session and login (WebService, REST, Mobile Engine Side)
XIVY-1818 SOAP Request & Response Body not displayed in RuntimeLog
XIVY-1664 REST API to get startable process starts
XIVY-1714 Enhance RestClientCall Inscription 2
XIVY-1819 Case Map Precondition UI
XIVY-1427 Provide business data for business case
XIVY-1815 Implement UI/UX Specification of Case Map Editor
XIVY-1821 Configure Name, Description, Activator of Tasks started from the Case Map using Business Data
XIVY-1461 SSO Tomcat Valve for WAF / IAM Environments
XIVY-1820 Refactor Workflow and Case Map Engine to reduce dependencies and complexity.


Monday, 6. March 2017

Jakobshorn Sprint 23: Case Map Conditions

In sprint 23 we continue with the implementation of the Case Map.

After it is now possible to configure and run a simple Case Map, we enhance it with pre-conditions and sidesteps.
Pre-conditions allows a conditional execution of a following process. Sidesteps are processes which can be executed independent of the current case map state.

Additionally, we finalize the Case Map UI/UX and go again a step further with the easy to use REST Client Inscription Mask.

List of planned stories:
XIVY-1639 Complete UI/UX Specification for Business Case Map Editor
XIVY-1689 Case Map Editor in Material Design and with CRUD support for Stages, Processes and Sidesteps
XIVY-1716 Pre-condition
XIVY-1717 Sidesteps in Stages
XIVY-1691 Use OSGI engine in project-build-plugin
XIVY-1714 Enhance RestClientCall Inscription
XIVY-1715 Bundled ElasticSearch server cant start on whitespace paths
XIVY-1727 Error while starting Engine in maven project build plugin


Monday, 13. February 2017

Jakobshorn Sprint 22: Play the Case Map

In sprint 22 we continue with the implementation of the Case Map.

The goal is to create, configure and run a Case Map, with a limited (but already powerful) featureset. This includes a simple UI to track an executed Case Map, with its created Cases and Tasks. This allows users to ‘play with the Case Map’, implement first use cases and give us feedback. Additionally we go a step further with the easy to use REST Client Inscription Mask.

List of planned stories:
XIVY-1686 Enhance Case Map Engine to support follow up auto starts, stage switches, milestones, pre-conditions and post-actions
XIVY-1639 Write UI/UX Specification for Business Case Map Editor
XIVY-1689 Case Map Editor in Material Design and with CRUD support for Stages, Processes and Sidesteps
XIVY-1682 Analyze and specify Case Map deployment, versioning, lifecycle
XIVY-1684 Provide localizable Stage Values on Business Cases and Case Map
XIVY-1690 Minimal CaseMap Support on Designer Workflow UI

XIVY-1688 Enhance RestClientCall Inscription Mask

XIVY-1687 Finish OSGI engine product II
XIVY-620 Deploy full application ZIP


Monday, 23. January 2017

Jakobshorn Sprint 21: Case Map

In sprint 21 we will focus on a first implementation of the Case Map and improving the Rest Activity Inscription Mask.

XIVY-1569 Introduce Business Case Map Project Resource
XIVY-1570 Introduce Business Case Map Runtime Engine
XIVY-1637 Simple Business Case Map Editor
XIVY-1123 Improve Inscription Mask of REST Activity process element to ease the configuration of most common REST Service Kind(s)
XIVY-1638 Integrate Business Case Map Editor into Designer
XIVY-1639 Write UI/UX Specification for Business Case Map Editor
XIVY-1625 ModelValidationException when two similar rest-endpoints exists in different ivy-application
XIVY-1574 DocBook can not longer be validated in oxygen XML Editor
XIVY-1538 Include the simple SMTP ‘mailsnag’ in the Designer
XIVY-1368 Warn/Analyze/Improve protection against SQL Injection in an ivy Database Step
XIVY-1458 Validate macro fields
XIVY-1643 Finish OSGi engine product