Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Build, protect and deploy apps across any platform and mobile device
Automate decision processes with a no-code business rules engine
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
I hope you all enjoyed the first three videos in our OpenEdge 11.3 Tech Tip video series of four. In those first three videos, I gave you an introduction to 11.3, a tour of a business process, and instructions on how to build a process-oriented application using OpenEdge BPM. I also showed you how to use Corticon BRMS for OpenEdge.
As I wrap up the series, I will show you how all of these elements come together, allowing you to build applications with agility and shortened time-to-market. In this fourth and final 11.3 Tech Tip video, I will explain how to call a Corticon decision service from BPM, modify a ruleset and redeploy a decision service. I will also show you how quick and simple it is to use evolving rules. Watch below.
If you missed any of the videos in this tech tip series, click here to watch them and any other OpenEdge 11.3 videos you may have missed. As always, please share your comments and questions below.
Gary is responsible for developing go-to-market strategies, providing technical marketing support and developing best practice materials for the Rollbase aPaaS platform.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.