<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

cDevWorkflow v8.7 – Business Object Version

Posted by Dileepa WIjayanayake on Dec 10, 2015 7:52:13 PM


The new version of cDevWorkflow focuses on (1) cDevWorkflow event generation and (2) workflow use of Business Objects.

(1) cDevWorkflow contains an Enterprise Service Bus (ESB) for event based processing that, until now, could only process events generated by external applications. The latest release of cDevWorkflow now generates events from within and can trigger events based on cDevWorkflow changes. For example, an event can be generated when an instance is executed. Event handlers associated with these events will execute and perform functions based on the handler functionality. All events will also receive event parameters based on the type of event.

For example, when a workflow instance is deleted from cDevWorkflow, you might want to delete its associated data from the host application. In order to the perform this, we can define a handler for the instanceDeleted event to remove data from the host application. Then, whenever a workflow instance is deleted from cDevWorkflow, an event is fired and placed onto the ESB. The ESB will use the handler to delete data from the host application. Event generation within cDevWorkflow can be turned on/off via an application setting or by setting the event generation API property. A list of currently supported events is displayed in the occurrence table below. Future versions of cDevWorkflow will support more and more events.

Business Object

(2) The second major enhancement in version 8.7 is Business Object (BO) support. If your host application has business objects that are accessible via an API, you can now access those business objects in cDevWorkflow and use them within cDevWorkflow processes. For example, a host document management application might have business objects such as folders and documents. These objects would have properties such as objectName, objectID, dateCreated, dateUpdated, etc. If the host application makes these object properties accessible through an API, these business object properties can be utilized inside cDevWorkflow processes. For example, “document.dateCreated” can be utilized in an expression to make a decision. Business Objects can be also accessed and manipulated using the cDevWorkflow’s API. For a detailed example of the implementation, configuration and use of a Business Object in cDevWorkflow see http://www.cdevworkflow.com/build-a-business-object/.


In addition to Event Generation and Business Object support, cDevWorkflow v8.7 adds a host UI enhancements, performance improvements and overall improvements. Check out the version history or the version readme file to learn more.

You may also be interested in reading more on the subject of Configuring a Custom Workflow Step.

A small sampling of the Workflow Technology for BPM Solutions contained within our cDevWorkflow product offering can be found here: Workflow Technology That Works.

[hs_form id="9"]

Learn more about our Process Automation & IT, QA Services or Software Development products and solutions on the Web!  Visit us at: Innovative Process Solutions




Topics: Blog, Business Object