Architect Consultant blog

This year's Cordial was held on the 9th and 10th October in Putten. The yearly event is getting more popular because it was packed. Some of the highlights for me: A couple of very entertaining presentations with content. Must see: Freek Vermeulen  on why organisations find it so difficult to change. Magnus Lindkvist  on the present and future trends Meeting a lot of interesting people in the BPM field Partner dinner with excellent food Nice to hear that integration and BPM skills are still very much needed in the future :-) See the CEO of Cordys in person Presentation of CIZ of a project with Cordys Case Management. With  Ciber  i also participated within that project. So it was nice to hear of the succes The partnership of Cordys and Aquima . A business rule engine that can be used seeming less with Cordys And of course more can be found on  http://www.cordys.com/resources Looking forward to it again next year!

In a lot of projects i have done for customers there are a few misunderstandings i often see with BPM or Business Process Management.  1) You are not doing BPM when using a BPM tool It is often called already BPM because it is hot, but the business is not process oriented at all. This is because a BPM tool is introduced bottom up, but the organization is not process oriented at all. In fact the business is process oriented (by default there is of course always a process), but this is not analysed or controlled.  2) Flexibility comes not for free This is maybe in theory but in practice i have rarely seen this. Making a solution flexible requires a lot of future knowledge which is often very difficult of course. You can only make your BPM solutions flexible where you know you need the flexibility.  3) BPM does not solve it all As with all new hypes, this is the next magic tool that solves it all. Of course this is not the case and it requires a lot of good thinkin...

You can test a decision table with the test tool of Cordys (see  Here ). However sometimes you want to automate tests with for example soapUI. In this case it is advised to generate a webservice from the Decision Table. This is nicely described  here . However I ran into a problem that the prefix of namespaces must be entered when the Decision Table was selected. After a while I found the problem. You use Schema files for the input of a Decision Table. Go to the definition of the Schema and double click it: The you should check the Namespace Prefix in this namespace. This prefix must NOT be empy. When I filled in the prefix I was able to generate the webservice on the Decision Table again.