There is nothing like previewing the future of Business Rules and Business Process tooling. Be among the first one to leave footprints in the fresh snow as we take you on a tour of the JBoss Business Rules Management System (BRMS) and JBoss Business Process Management Suite (BPM Suite).
Attendees will be provided with the background architectures, a live demo of their capabilities, and a look at how they are Cloud enabled by the OpenShift cloud service. Join us for an hour of rules, processes, cloud, and crystal ball gazing!
7. Process Modeler & Simulation
Enable process modeling and simulation in a business
user friendly, web-based environment.
Key features:
■ Web-based BPMN 2.0 process modeler
■ Context menu for easy creation of flows
■ Visual validation
■ Integration with service repository
■ Simulation of business process
7
erics@redhat.com | @ericschabell
8. Target users
Process Analyst Creating and simulating business processes
Developers. Creating business processes, collaboration with process
analysts / developers adding execution details
8
erics@redhat.com | @ericschabell
10. Key features
Enable the configuration of logical and physical data models
with no coding.
Key features:
■ Simple data modeling UI.
■ Supports multiple physical representations of data model.
■ Conceptual information added, such as user friendly names.
■ A common tool for analyst and developers.
■ Automatically generates all assets required for execution.
■ Single representation enables developer roundtrip.
Benefits:
■ Make data models first class citizens in the process improvement cycle.
■ Capture and document data models by analyst.
■ Allow for full process automation with data and forms, without the need for
development skills.
10
erics@redhat.com | @ericschabell
11. Target users
Process / Data Analyst.
Capture requirements. Create data model.
Developers.
Create data model.
11
erics@redhat.com | @ericschabell
13. Form engine & modeler
13
erics@redhat.com | @ericschabell
14. Key features
Enable the configuration and execution of forms
with no coding.
Key features:
■ Form Modeling WYSIWYG UI for forms.
■ Form autogeneration from data model / Java
objects
■ Data binding for Java objects
■ API for embedding and rendering forms with
custom data.
■ Customized forms layouts (*)
■ Forms embedding
■ i18n support.
Benefits:
■ Enable non technical users to create forms and
execute them in processes.
■ Develop complex UI in a WYSWYG fashion for
data capture and presentation.
14
erics@redhat.com | @ericschabell
15. Target users
Process Analyst & developers. Building & testing forms.
Developers. Add advanced configuration to forms. Embed forms in custom
components.
End users. Using forms in tasks or other modules.
15
RED HAT CONFIDENTIAL
18. Business Rules Editors
Enable the configuration and execution of business rules models.
Key features:
■ Decision tables. Import from excel
■ Test scenarios
■ Rule validation
■ Integrated with processes
Benefits:
■ Enable non technical users to create and customize business
rules.
18
erics@redhat.com | @ericschabell
22. Key features
Process instance management and task list
management.
Key features:
■ Starting process instances
■ Inspecting the current state of process instances
■ Visualization of current state
■ Managing process instances
■ Task list management
■ Claiming, starting, completing task (using task
forms), etc.
Benefits:
■ Enable business users and end users to start and
manage process instances in a user-friendly manner
■ Task list management and task life cycle
management
22
erics@redhat.com | @ericschabell
23. Target users
End users. Starting, inspecting and managing process instances and tasks
Administrators. Managing process instances and tasks
23
erics@redhat.com | @ericschabell
26. Key features
Enable the configuration of business dashboards by
configuration with no coding.
Key features:
■ Visual configuration of dashboards (Drag'n'drop).
■ Graphical representation of KPIs (Key Performance
Indicators).
■ Configuration of interactive report tables.
■ Data export to Excel and CSV format.
■ Filtering and search, both in-memory or SQL based.
■ Process and tasks dashboards with jBPM.
■ Data extraction from external systems, through
different protocols.
■ Granular access control for different user profiles.
■ Look'n'feel customization tools.
.
Example: Editing an indicator.
Example: Dashboard with active filter
26
erics@redhat.com | @ericschabell
27. Target users
Managers / Business owners. Consumer of dashboards and reports.
IT / System Architects. Connectivity and data extraction.
Process Analyst. Dashboard composition & configuration.
27
erics@redhat.com | @ericschabell
28. Dashboards
TOOLBAR (With edit permission)
BREADCRUMB
NAVIGATION
INDICATOR (CLICK TO DRILL DOWN)
CURRENT FILTER
28
erics@redhat.com | @ericschabell
29. Create indicator
1. Click on the panels palette
3. Select 'Create panel'
2. Select 'Key Performance Indicator'
4. Drop panel in the layout region
29
erics@redhat.com | @ericschabell
{"5":"We will start with a discussion of how the BRMS comes to be. We will breeze over the background of BPM, discuss how the project jBPM releases are incorporated into the BRMS product.\nFrom there we will examine the interesting points as they apply to a business user, followed by the more technical elements of BRMS that will be of interest to developers.\nFinally we will summarize in an overview the new BPM components that come from the jBPM project. We will also mention the components that will NOT be included into the BRMS 5.3 product that are in the jBPM project. These are up and coming features that have yet to mature enough for inclusion at this time, but you can expect to appear in future versions of BRMS. \n","34":"We will start with a discussion of how the BRMS comes to be. We will breeze over the background of BPM, discuss how the project jBPM releases are incorporated into the BRMS product.\nFrom there we will examine the interesting points as they apply to a business user, followed by the more technical elements of BRMS that will be of interest to developers.\nFinally we will summarize in an overview the new BPM components that come from the jBPM project. We will also mention the components that will NOT be included into the BRMS 5.3 product that are in the jBPM project. These are up and coming features that have yet to mature enough for inclusion at this time, but you can expect to appear in future versions of BRMS. \n","1":"<number>\n","2":"We will start with a discussion of how the BRMS comes to be. We will breeze over the background of BPM, discuss how the project jBPM releases are incorporated into the BRMS product.\nFrom there we will examine the interesting points as they apply to a business user, followed by the more technical elements of BRMS that will be of interest to developers.\nFinally we will summarize in an overview the new BPM components that come from the jBPM project. We will also mention the components that will NOT be included into the BRMS 5.3 product that are in the jBPM project. These are up and coming features that have yet to mature enough for inclusion at this time, but you can expect to appear in future versions of BRMS. \n","20":"We will start with a discussion of how the BRMS comes to be. We will breeze over the background of BPM, discuss how the project jBPM releases are incorporated into the BRMS product.\nFrom there we will examine the interesting points as they apply to a business user, followed by the more technical elements of BRMS that will be of interest to developers.\nFinally we will summarize in an overview the new BPM components that come from the jBPM project. We will also mention the components that will NOT be included into the BRMS 5.3 product that are in the jBPM project. These are up and coming features that have yet to mature enough for inclusion at this time, but you can expect to appear in future versions of BRMS. \n"}