Hi All,
I’m new to Servoy and have been reading lots of documentation, haven’t yet worked with it hands-on. I understand that Servoy is multi-tenant from the ground up. One of the things I haven’t seen are Servoy design strategies for an ISV to develop a single-application that can be shared among all tenants and then have tenant-specific customizations/configurations. From that point forward, how can each tenant individually configure the base application while still accepting fixes/enhancements from the base that the ISV supports?
Take Contact Management for example:
ISV does Contact Management and develops a particular data model, UI, and supporting business logic that is shared among all tenants. Now what does it look like when a particular tenant needs to add tenant-specific attributes to their “version” of Contact, add those attributes to the Contact input form, and add business logic to support those attributes? Are tenants copying/cloning such that they no longer get fixes/enhancements from the base Contact Management app that the ISV supports? Does the response change if the tenant needs to tweak something about the “base”, ISV-delivered app, as opposed to simply adding on it?
With this in mind, are there existing documents/posts that describe this relationship between an ISV and its tenants with respect to tenant-specific customizations/configurations to the “base” application?
Thanks,
Eric