The following set of instructions are for swapping between the different PIE PAMlet environments. NOTE: These instructions follow the use case of swapping between DEMO-PIE and DEV-PIE, but the scenario is similar if you intend to swap in the other direction. Step 1 - Execute the script and follow the prompts
Scenario : A mortgage application is automatically qualified and becomes ready for final approval In this scenario we will: give you a high-level introduction to using Red Hat's Business Central to view the Mortgage process and to view a Decision Table in the process (see Demo Steps: Business Central) allow a customer to submit an application for a Mortgage using the applicant's UI developed in Entando (see Demo Steps: Applicant UI) allow the mortgage lender to view the status of a mortgage application and then claim the application and move it to Final Approval (see Demo Steps: Lender UI)
PIE and the associated PAMlets are installed using the Leonardo cdk-setup-config script available from the Leonardo Public Gitbucket. There are a number of prerequisites necessary to be able support PIE. These include: An Apple MacBook with at least 16 GB of RAM. 25 Gb of free disk space per PIE. A Red Hat developers account. Accounts can be created from here. VirtualBox v6.0 or higher. VirtualBox can be downloaded from here. The Git client needs to be installed (may be default with OS) The Wget client needs to be installed. Once you have confirmed the above and downloaded the cdk-setup-config script follow the instructions below. The script will download, install and configure cdk along with all the necessary PAM and UI components. NOTE: the Mortgage Process PAMlet downloads approximately 4.8 Gb of necessary files Step 1 - Download Leoanrdo's PIE cdk-config Script
Since the first release of ARIS Connect, the concepts of publishing in ARIS have changed and lightweight workflows were introduced to provide basic support for the governance of process models. These new features have brought new and interesting experiences. However, feedback from ARIS customers with unique needs for rigorous process model governance indicated that more is needed than the lightweight workflows—like, for example, a workflow for publishing models in isolated repositories to ensure consistency for reporting and analysis. Although the gap left by the lightweight workflows can be filled by a fully-fledged ARIS Process Governance engine, budgets are often a barrier. On the other hand, manual administration (e.g. the handling of models across several repositories without the support of automation) requires a fair bit of maintenance.
In this interview with Stephen White, who was closely involved in the developed of the BPMN language, we discussed the myths that been swirling around the internet about BPMN. More specifically, we talk about some crowd-sourced myths and weaknesses that people had been discussing on the BPMN wikipedia page. Sandeep Johal: The first myth is that there is ambiguity and confusion in sharing BPMN models. Stephen White: To me this more of a tool vendor issue, perhaps. A lot of it just had to do with mobility or quality of the import export capabilities of the tool. I've soon tools that are very good at it, and other tools that are not as good at it. When you share a BPMN model, you might have issues importing it into a different tool. You might have to do some work after that, but I think that is a vendor issue. The specification itself gives the XML schema or metamodel behind it so that tools can do that. There were a couple of minor issues and I think that OMG has been addressing that. There's a committee that does interchange formats, and they've been working on that, and showing demonstrations at conferences. I think any of the technical issues are being solved, and I think it's mainly up to the tool vendors to support that .