The Decisions flow designer allows creation of graphical models that are able to be executed. Flows can be started by user interaction (forms), on a schedule or based on an api call or event
The flow debugger allows running of a flow in a simulation mode, seeing the path the flow took as well as the data present at each step of the flow
Data is mapped in and out of flow steps using the mapping editor.
New datastructures can be designed graphically in the data structure designer. These can either be database stored or simple types that are just used in flows.
An integrated profiler allows viewing of real time performance data of executing flows and rules. This allows hotspots and inefficent flow steps to be identified.
Workflow data can be stored and viewed in process view pages. These pages can be customized using the Decisions page and report designer to provide custom views into the process execution.
The integrated unit test framework allows unit tests to be created and executed in the debugger, on a schedule or every time a flow or rule is changed. Unit testing enforce your flows and rules to have reliable behavior as they are modified.
Combining and formatting of text is done in the merge editor. This editor is available on all flow steps.
Database integration is done using a wizard that walks a designer user through the steps of selecting/setting up a database connection, supplying the query, table or stored procedure and any other configuration information. Database integrations result in new flow steps being available in the flow designer as well as report designer datasources.
Webservice integration is available both for REST and SOAP services. Webservice integration is done by a wizard that walks through the configuration of each of the elements of configuring a webservice integration. Each method on a service will result in additional steps in the flow designer toolbox.
Entities can be extended with additional behavior like actions, validation rules and event triggers. The flow and rule engine is used to create each of these extension pieces.
The form designer is a graphical drag and drop tool that allows creation of forms in a WYSIWYG fashion. Forms can be laid out in a variety of layouts and can take advantage of CSS for styling. Forms can be dynamic with rules for control showing/hiding, custom validation rules, etc.
Here are some examples of forms built by customers or by the Decisions delivery team.
Forms can also be targeted for mobile or tablet display. The form engine will decide at runtime which form to show based on the device the user is using.
The report writer and page designer allow the creation of end user reports and dashboards that allow data to be viewed and acted on. This designer works on the basis of 'data sources' that enable the designer user to configure data access without writing sql. Reports can report on data that is in other sources, not only database stored data.
Reports, tiles, charts and matrixes can be combined with other elements (buttons, embedded forms, etc) to create rich data views for end users.
Here are some example dashboards created by our customers and delivery teams.
In addition to traditional table based report views, matrix views allow data to be viewed in a summary fashion comparing attributes of the resulting data.
Data can be viewed graphically in charts. Chart elements are able to be drilled in to see the data that makes up the different elements of the chart.
All reports can be exported to Excel for further manipulation and distribution.
Decisions includes an end user portal that is a place where users can come to view dashboards, work on tasks or start new workflows.
Decisions has a mobile portal that gives a platform for user interaction on phones and small format devices.
Integrated monitoring dashboards (built in the Decisions report writer) allow views for system management and tuning.
This is a recorded 5 day online training session that includes slides and resources.
Building responsive workflows that put the thing at the center of the model with rules that determine what can happen to that thing. Contrasting this approach with Part 1's traditional workflow design.
In this session we start from a blank canvas and walk attendees through building an app from scratch. After this session viewers should have a fundamental idea of the level of effort and process through which a designer user in Decisions can create an end to end business application.
In this session our Chief Architect and CTO review common methods of extending the Decisions Platform through our .NET SDK. This session includes a “cheat sheet” for quick ways to extend the platform.
In this session, Aaron Broughton takes attendees through building more complex forms in Decisions that utilize Data Flows to make specific fields on the form more dynamic and ultimately more user friendly.
Using the example scenario of a purchase order approval process, Eric Welmerink guides attendees through setting up approval chains and other approval-oriented interactions in your applications.
General overview of the Decisions Studio
Overview of workflow in Decisions