Method and system for providing software functionalities to users of multi-tenant applications via inheritance

A non-transitory computer readable medium (CRM) storing instructions for providing software functionalities to users of multi-tenant applications via inheritance, comprising:

• defining a plurality of functionalities to be inheritable by a tenant application, in a master application, comprising:
• selecting the plurality of functionalities from a set of implemented functionalities;
• and
• defining a scope for the selected plurality of functionalities,
• wherein each of the plurality of functionalities is a customization to the master application specific to a first plurality of users;
• publishing the master application after defining the plurality of functionalities;
• and
• after publishing the master application:
• receiving a first request to generate the tenant application, wherein the first request specifies the master application and a first functionality of the plurality of functionalities to be inheritable by the tenant application;
• generating the tenant application in response to the first request, wherein the tenant application comprises the first functionality and a first custom functionality, wherein the first custom functionality is not provided in the master application;
• publishing the tenant application to a second plurality of users, wherein the first plurality of users is a superset of the second plurality of users;
• receiving a second request to access the published tenant application from a user of the second plurality of users;
• and
• validating the first functionality, prior to publishing the tenant application, wherein validating the first functionality comprises verifying that elements required by the first functionality are accessible to the user.

A system for providing software functionalities to users of multi-tenant applications via inheritance, comprising:

• a computing device comprising a computer processor;
• an application server, executing on the computer processor, and configured to:
• obtain a definition of a plurality of functionalities to be inheritable by a tenant application, in a master application,
• wherein the plurality of functionalities is selected from a set of implemented functionalities,
• wherein a scope for the plurality of functionalities is defined, and
• wherein each of the plurality of functionalities is a customization to the master application specific to a first plurality of users;
• publish the master application after the definition of the plurality of functionalities is obtained;
• and
• and after publishing the master application:
• receive a first request to generate the tenant application, wherein the first request the master application and a first functionality of the plurality of functionalities to be inheritable by the tenant application;
• generate the tenant application in response to the first request, wherein the tenant application comprises the first functionality and a first custom functionality, wherein the first custom functionality is not provided in the master application;
• publish the tenant application to a second plurality of users, wherein the first plurality of users is a superset of the second plurality of users;
• receive a second request to access the published tenant application from a user of the second plurality of users;
• and
• validate the first functionality, prior to publishing the tenant application, wherein validating the first functionality comprises verifying that elements required by the first functionality are accessible to the user.