Test S-BPM Modeller v2

[mwageneder]

ToDo:

• Install new version of SBPM Modeller from mkolody and test it
  • https://github.com/mkolodiy/s-bpm-modeler
• Check, if Processes modelled with the new version can be imported into our platform
  • If NO, consult @amarbajric for further discussion
  • If YES, model the three example processes already modelled with the old modeller with the new one (this time in english) and UPDATE the corresponding process description which will be the example description available in the ProcessStore
• Check, If old SBPM Modeller can be replaced with the new one (since the old one is not working correctly)

[mwageneder]

Installed the new SBPM-Modeller from mkolodiy and tested it.

Importing the *.owl files into our project works fine therefore I

• remodelled the 3 SBPM Processes with the new Modeller

  • Business Trip Application
  • Buying Process
  • Employee Entrance

• evaluated if the new Modeller can be implemented into our project and the result is NO. Not within the time given.

After a skype meeting with @amarbajric we decided to further discuss this topic how we go on with the modeller. Here are some possible solutions i already discussed with @amarbajric but everybody should give their two cents:

• Since the IPPR project is based on a relational db and the new modeller is based on a NO-SQL DB (MongoDB), it can`t be implemented, it can only "coexist" with our existing project.
• We can run the Modeller simultaneusly and as a separate "service" (customers may also pay for it?) and if someone wants to edit a SBPM process, he/she has to export it from our EasyBiz Platform and import it into the modeller as a *.owlfile. Definitely complicated but possible.
• Another way of achieving a "unified" engine and modeller experience, we could have a look at the import and export functions of the two projects, if we could make use of them and trigger the import and export in the background and the customer doesn`t notice it? (if this is even possible?)

TODO

Discuss this issue maybe tomorrow or at latest during the weekly-scrum on Friday 4.5.18.

[mwageneder]

UPDATE 12.06.2018

Short Overview of the topic as this task catched my attention for a very long time!

• Started modelling SBPM processes with modeller v1 and realised the modeller is kind of buggy and sometimes he doesnt let you save the *.owl File
• I later relised, the process models i created could not be imported within the engine so..
• Since Mr. Singer told us there is a v2 of the modeller i tried modelling all processes in english now with the second newer modeller (which is way better to model SBPM-Processes by the way)
• So later on i imported them into the engine and i could set all preferences so i thought everything is fine and moved on and created all three processes with modeller v2
• after a while I realised, that there could not even be an integration of the modeller v2 within our engine (Since modeller & engine v1 are a relational DB and modeller v2 is No-SQL)
• So I tried to find a possible solution which could work for our approving scenario
• I found nothing and while doing that, i started a few processes and nothing happened
• Big problem .. all processes created with modeller v2 could be imported to our process engine, but when starting them, nothing happens
• Very worried about the fact that nothing works, I contacted Mr. Geisriegler (Creator of v1 Engine & Modeller) and he told me, the modeller is very very buggy and even the slightest mistake makes everything not working.
• So we aggreed on me doing my best to get a very simple process model to work with modeller v1 and here we go on 11th of June i finally got a process model to work appropriate
• Now June 12 i am managing to get the three process models to work as expected in April

So I am finishing the process models (final version and working as they should) till the end of the week.

Hope i could give all involved an overview where i strangeled and why this task catched my attention and my nerves for so long...

[mwageneder]

Final Update:

All Process Models are ready to execute and available on Sharepoint. Documentation is also available on Sharepoint within the Process Folder.

Task Done.