Doorgaan naar hoofdcontent

Your first Cordys Dashboard

Monitoring

Within an enterprise and on your processes you want monitoring. Monitoring is used to for example:
  • View the number of ongoing processes and its status
  • If certain KPI's are met
  • Triggering other processes when a certain event takes place
Cordys supports this in the form of BAM and uses certain constructs for this. In this Blog i will describe a small example on how to set up BAM and how to create Dashboards. It gives an idea on how this can be done in Cordys. I use the following picture in which the created Cordys artifacts are displayed.


Step 1 - Create a webservice

This step is not described here, but a webservice can be generated from a BPM, database or an external service can be used for example. Next i will use this webservice to create a Business Measure artifact.

Step 2 - Create a Business Measure

A Business Measure helps in measuring a particular aspect of a business process or any external data. The Business Measure provides a view on the selected attributes, contained in a Process Monitoring Object, a webservice or the external data source. In this case we use a webservice as the basis.

  • Create a new Business Measure
  • Fill in name and description
  • Select Graph because we will use it to show on a dashboard.
  • Create Measure From: Web Service
  • Select Object Source: GetProductsObjects
  • In this case we will show the products and ho much is in stock

  • Click Next
  • Select New and click Finish
A webservice is generated and a component is generated that can be used within a dashboard. 

Step 3 - Create a dashboard

Now we are creating an interface for the monitoring of the produkts in stock.
  • Create an XForm artifact
  • Drag-and-drop the Producktsinstock component (as shown in the previous step) on the UI
  • Click on Properties of this component

In the properties you can choose how the data should be displayed.
View - The type of dashboard used. In this case i choose for Bar Chart. There are a couple more possibilities
Business Object - Here you select the data that is to be used from the webservice. In this case the Old tuples  contain the products. 
X-Axis fields - Here you select the attribute that is used for the X-axis. In this case the ProductName.
Y-Axis - Here we choose the UnitsInStock attribute.

Because the webservice requires two input parameters, these are given in the Input Parameters properties.

  • Select Preview and you will see you first Dashboard with Cordys BAM

Next time i will show how to create a KPI (Key Performance Indicator) that triggers another process.




Labels:

Reacties

  1. StephaniePumphrey27 januari 2013 om 21:46

    How different, if we could create models that are readable by customers and need no extra translation by developers.

    process management bpm

    BeantwoordenVerwijderen

Een reactie posten

Populaire posts van deze blog

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
48 reacties
Meer lezen

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h...
12 reacties
Meer lezen

Cloud to Cloud Application Integration

A lot of applications have integration possibilities, so do cloud applications. The question I got from a customer is whether to have a point-to-point integration with Cloud applications or to go through their ESB solution. This blog describes some considerations. Context The customer has a HRM application in which job vacancies are managed. Furthermore that system also handles the full applicant process flow. They also have another cloud application that handles the job vacancies. This application posts the jobs to social sites and other channels to promote the vacancies. Furthermore this application has some intelligence for job seekers to advice some new vacancies based on previous visits or profiles. The job vacancies need to be sent to the Vacancies application and applicant information needs to be sent to the HRM application, when a job seeker actually applies for a job. Furthermore status information about the job application is als...
11 reacties
Meer lezen