Everything in a solution, a publisher prefix so names never clash, and one package from Dev to Test to Production: unmanaged to build, managed to ship.
https://t.co/t2YBCb6xdJ
#parsware#parswareplatform#modeldriven#alm#devops
A field’s type decides what it stores; its control decides how it’s filled in. In Parsware you pick the control per form, down to one you built yourself.
http://localhost:3001/blog/024-choose-the-control-a-field-uses
#parsware#parswareplatform#modeldriven#form#formdesigner
Building an app gives it to nobody. In Parsware you share it with a role, see exactly who that reaches before saving, and the sharing travels with the solution.
http://localhost:3001/blog/021-your-first-app-shared-with-the-people-who-need-it
#parsware#modeldriven#role#rbac
Two people edit the same record. In many systems the second save erases the first. In Parsware it’s refused with a reason, and after a reopen both changes are kept.
http://localhost:3001/blog/020-two-people-one-record
#businessapps#parsware#parswareplatform#modeldriven