Hi Franek,
I'm sorry to ask this, but did you ask yourself how this would be possible? Since your are mentioning Git I'm assuming that you are a developer and therefore would be able to create a concept how it would be possible.
I read your message thought about it for a short time and dropped the idea. The issue is not the Git integration but that everything that entailed with it.
That's the current situation:
- There are no code files but data rows, which we would commit to git.
- There are multiple dependencies between the data rows.
- Simply everything in WEBCON is build on the integer ids.
- You need to commit all the applications, data sources, connection etc. to git
Issues:
- While you could compare the data rows from one table to another, that's mostly useless because there are dependencies. You would need some kind of visualization to decide, whether something should be merged into a branch without accidently breaking something else.
- Since everything is build on the integers this would need to be refactored to GUIDs. If this change would be applied, I would skip the next major release until everything is fixed.
- What are you doing if you are having workflow instances in steps, which you aren't (yet) available in a commit?
- Adding, removing and readding fields, because of switching branches, which could cause that the same field in the same environment has a different database column which in turn is used somewhere else?
- Security issues with passwords etc.
- Setting up Git
WEBCON BPS is a low code product targeting non developers at end customers , and this change would benefit only a very small percentage of the customers I would guess. The implied risks and costs simply aren't worth the effort.
Feel free to correct me and point out any errors. We would really be glad if there would be something because we, as a partner, are providing the same application to multiple customers and it would be great to have a comparison option between the current deployed version and the new one, before deploying it.
Best regards,
Daniel