Visual Flow Designer and Debugger

All ‘Decisions’ Studio business designers are visual. Visual designers allow for gathering around this ‘on-screen whiteboard’ where all stakeholders can see and discuss the design-implementation. Yes, the design is the implementation because the diagrams, rules, and forms that are designed are also operating.
Coding is for Developers! No Code

Coding is for Developers! No Code

‘Decisions’ was built to allow business people to understand and often create/maintain critical business processes and rules. Coding is for Developers! Are you a developer? You can contribute to the project by adding elements to the toolbox using the Decisions SDK.

Self Validating As-You-Go

Self Validating As-You-Go

When building or editing a workflow in the Decisions Platform, the designer will tell you about breaking changes as you edit. These issues might be missing data, steps not connected properly, or invalid configuration values.

Plan at High Level & Implement Complete Processes

Plan at High Level & Implement Complete Processes

Our workflow designer builds end-to-end business applications but can be used to plan a process at a high level. A business user can use placeholder steps and other visual elements in the workflow designer to plan and collaborate without getting into the details. Designer users with additional steps in the toolbox can evolve that business model into the finished application while the initial business models often become dashboard diagrams for showing team members the status of the workflows.

Automatically Track Key Business Metrics

Automatically Track Key Business Metrics

Any step in a workflow can participate in or set a Business Metric. Business Metrics in the Decisions Platform are key business indicators that can be specific to certain processes or used across all processes. These metrics show up on dashboards and can be tied to alerts, which makes it easy for you to start finding rule and workflow changes that will improve your company’s efficiency.

Nesting Flows

Nesting Flows

You build a workflow and it automatically becomes a single step that other designer users can put in their workflows. When you make a useful process, the business logic can be used over and over again without ever being recreated, which means the longer you use the Decisions Platform, the faster you can automate things that are specific to your business. Linking workflows together is natural in ‘Decisions’, and you can freely move from one workflow to the next when you are editing so that you are able to understand and think about the big picture. Linked workflows also let you control permissions so that sections of business logic can be protected from unwanted edits.

Dependency Browsing

Dependency Browsing

Since the reuse and linking of different design artifacts is so easy on the Decisions Platform – understanding where different artifacts are used is critical. ‘Decisions’ includes a fully independent browser that allows you to inspect and navigate both ways: to items using a design and to items the design is using.

Branching/Merging/Looping

Branching/Merging/Looping

Workflows do not always follow a ‘direct path’ from beginning to end. Rules can be used to determine which path needs to be followed. Additionally, there are a number of workflow control steps that allow you to solve problems that:

  • Require you to do a certain activity a number of times
  • Iterate through a list and take action on each item in the list
  • Have a number of active tasks working at the same time (branching/merging)
  • Start workflows that are operated on another thread/scope
API Access

API Access

When you build a flow or a rule in the Decisions Platform, it will automatically create a specific service that can be used as SOAP (Simple Object Access Protocol) and/or REST (REpresentational State Transfer) to interact specifically with that rule flow. This makes integration with the engine easy.

‘Decisions’ also has a comprehensive suite of specific web services that allow developers to integrate with the Flow and Rule Engine as well as all of the supporting business services. A developer can search the system for flows and rules, build up interactions, and run them using the SOAP or REST services.