I'm glad you liked the new BPM features.
> Shouldn't the process definition be available on backoffice, so that the customer may alter processes whenever he wants?
The process definition will be available for business profiles in a backoffice (not in ServiceCenter). Business users will be able to understand and propose changes for the process using the ECT submit feedback on top of a process definition diagram. Still the process changes need to be implemented by the developers, as it is the only way to ensure a smooth and stable operation for the final result.
> How does one sell this BPM to a customer? What advantages does this bring to "him" ?
Being able to implement business changes (either process oriented or not) with a minimum effort and risk is our most important goal. Our tools, methodologies, and best pratices are aligned with this goal.
What we have found in multiple customer installations is that BPM suites that are more business oriented (allowing business to completely change process definitions) are very good at the process definition level, but fail to offer the robust changing mechanisms that we promote with a single tool.
There is also a set of facts and falacies that should be understood when selling the OutSystems Plaftorm:
I hope this helps. These ideas were the foundation for the BPM Features that we added in 5.0. Let me know if you need more information.
Besides the fallacies that Lúcio depicted very clearly, I’d just want to add something I believe it’s one of the biggest differentiators of the Agile Platform 5.0, which is bringing together two different lifecycles, the application development and the business process management, into a single and unified environment.
Now, in Service Studio 5.0 you can model the application and the process together, side-by-side, in one single model, and in one integrated environment, without the burden of complex and costly integration. This also means that whenever a change is needed, it happens both in the application and the process, you change it consistently and you deploy it once. Then in Service Center you will also be able to monitor applications SLA and processes instances as well.
If you can think in a process application, we just added a new layer – the process layer –but taking full advantage of all the other existing layers, the Database model (to trigger process events), the User Interface (binding process activities to screens), Security settings (reuse the existing permissions areas in the process), and Integration (using all integration adapters you have in place). But above all, the TrueChangeTM mechanisms that you had for applications are now extended to the process, and guess this, they are done on-the-fly!
Last but not least, as you know one the major goals of a BPM initiative is flexibility and performance improvement. As such we also introduced a new set of powerful business activity reports and graphs in 5.0. You can review process performance, trends, service level agreement fulfillment, team workload and more to help you keep an eye on your organization's processes performance. And they are all accessible through simples and one click-away web blocks.
Hope this helps.