Methods, apparatuses and computer program products for managing product feature release in a cloud-based computing environment
Various embodiments herein described are directed to methods, apparatuses and computer program products configured for managing software product feature and version releases in complex and distributed network systems. Various embodiments are directed to systems and network frameworks that are configured to provide controlled release of software features/changes through admin user notification and control interfaces. In some embodiments, a sandbox system environment may be provided to admin users to test and configure upcoming software features/changes. Additional example embodiments provide a release track system that specifies and manages feature release schedules in a complex and multitenant cloud network environment.
1. An apparatus for managing feature release in a cloud-based computing environment, the apparatus comprising at least one processor and at least one non-transitory memory comprising program code, the at least one non-transitory memory and the program code configured to, with the at least one processor, cause the apparatus to at least:
receive, from a first client device associated with a first user profile, a scheduled release track subscription request indicating a product identifier, wherein the first user profile is associated with a first organization identifier and an admin user identifier;
retrieve, from a client data repository, a second user profile associated with the first organization identifier and a non-admin user identifier;
update the second user profile to indicate a scheduled release track subscription associated with the product identifier; and
transmit a feature bundle data object associated with the product identifier to a second client device associated with the second user profile at a feature bundle release time.
2. The apparatus of claim 1 , wherein the feature bundle data object comprises a plurality of feature release data objects, wherein each of the plurality of feature release data objects comprises documentation metadata.
3. The apparatus of claim 2 , wherein, prior to transmitting the feature bundle data object to the second client device, the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to further:
generate a feature bundle notification based at least in part on the documentation metadata associated with each of the plurality of feature release data objects; and
prior to the feature bundle release time, transmit the feature bundle notification to the first client device.
4. The apparatus of claim 3 , wherein, subsequent to transmitting the feature bundle notification to the first client device, the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to further:
receive, from the first client device, an approval indication in response to the feature bundle notification; and
in response to receiving the approval indication, transmit the feature bundle data object to the second client device.
5. The apparatus of claim 2 , wherein the first client device is associated with a preview track subscription, wherein the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:
generate a feature bundle notification based at least in part on the documentation metadata associated with each of the plurality of feature release data objects; and
prior to the feature bundle release time, transmit the feature bundle notification and the feature bundle data object to the first client device.
6. The apparatus of claim 5 , wherein, subsequent to transmitting the feature bundle notification and the feature bundle data object to the first client device, the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to further:
receive, from the first client device, an approval indication in response to the feature bundle notification; and
in response to receiving the approval indication, transmit the feature bundle data object to the second client device.
7. The apparatus of claim 2 , wherein the at least one non-transitory memory and the program code are configured to, with the at least one processor, cause the apparatus to:
select the plurality of feature release data objects in response to determining that category metadata of each of the plurality of feature release data objects indicates a feature category associated with the scheduled release track subscription.
8. A computer program product for managing feature release in a cloud-based computing environment, the computer program product comprising at least one non-transitory computer readable storage medium having computer executable code portions stored therein, the computer executable code portions comprising program code instructions configured to:
receive, from a first client device associated with a first user profile, a scheduled release track subscription request indicating a product identifier, wherein the first user profile is associated with a first organization identifier and an admin user identifier;
retrieve, from a client data repository, a second user profile associated with the first organization identifier and a non-admin user identifier;
update the second user profile to indicate a scheduled release track subscription associated with the product identifier; and
transmit a feature bundle data object associated with the product identifier to a second client device associated with the second user profile at a feature bundle release time.
9. The computer program product of claim 8 , wherein the feature bundle data object comprises a plurality of feature release data objects, wherein each of the plurality of feature release data objects further comprises documentation metadata.
10. The computer program product of claim 9 , wherein, prior to transmitting the feature bundle data object to the second client device, the computer executable code portions comprise the program code instructions configured to:
generate a feature bundle notification based at least in part on the documentation metadata associated with each of the plurality of feature release data objects; and
prior to the feature bundle release time, transmit the feature bundle notification to the first client device.
11. The computer program product of claim 10 , wherein, subsequent to transmitting the feature bundle notification to the first client device, the computer executable code portions comprise the program code instructions configured to:
receive, from the first client device, an approval indication in response to the feature bundle notification; and
in response to receiving the approval indication, transmit the feature bundle data object to the second client device.
12. The computer program product of claim 9 , wherein the first client device is associated with a preview track subscription, wherein the computer executable code portions comprise the program code instructions configured to:
generate a feature bundle notification based at least in part on the documentation metadata associated with each of the plurality of feature release data objects; and
prior to the feature bundle release time, transmit the feature bundle notification and the feature bundle data object to the first client device.
13. The computer program product of claim 12 , wherein, subsequent to transmitting the feature bundle notification and the feature bundle data object to the first client device, the computer executable code portions comprise the program code instructions configured to:
receive, from the first client device, an approval indication in response to the feature bundle notification; and
in response to receiving the approval indication, transmit the feature bundle data object to the second client device.
14. The computer program product of claim 9 , wherein the computer executable code portions comprise the program code instructions configured to:
select the plurality of feature release data objects in response to determining that category metadata of each of the plurality of feature release data objects indicates a feature category associated with the scheduled release track subscription.
15. A computer-implemented method for managing feature release in a cloud-based computing environment comprising:
receiving, from a first client device associated with a first user profile, a scheduled release track subscription request indicating a product identifier, wherein the first user profile is associated with a first organization identifier and an admin user identifier;
retrieving, from a client data repository, a second user profile associated with the first organization identifier and a non-admin user identifier;
updating the second user profile to indicate a scheduled release track subscription associated with the product identifier; and
transmitting a feature bundle data object associated with the product identifier to a second client device associated with the second user profile at a feature bundle release time.
16. The computer-implemented method of claim 15 , wherein the feature bundle data object comprises a plurality of feature release data objects, wherein each of the plurality of feature release data objects comprises documentation metadata.
17. The computer-implemented method of claim 16 , wherein, prior to transmitting the feature bundle data object to the second client device, the computer-implemented method further comprises:
generating a feature bundle notification based at least in part on the documentation metadata associated with each of the plurality of feature release data objects; and
prior to the feature bundle release time, transmitting the feature bundle notification to the first client device.
18. The computer-implemented method of claim 15 , wherein, subsequent to transmitting the feature bundle notification to the first client device, the computer-implemented method further comprises:
receiving, from the first client device, an approval indication in response to the feature bundle notification; and
in response to receiving the approval indication, transmitting the feature bundle data object to the second client device.
19. The computer-implemented method of claim 16 , wherein the first client device is associated with a preview track subscription, wherein the computer-implemented method further comprises:
generating a feature bundle notification based at least in part on the documentation metadata associated with each of the plurality of feature release data objects; and
prior to the feature bundle release time, transmitting the feature bundle notification and the feature bundle data object to the first client device.
20. The computer-implemented method of claim 19 , wherein, subsequent to transmitting the feature bundle notification and the feature bundle data object to the first client device, the computer-implemented method further comprises:
receiving, from the first client device, an approval indication in response to the feature bundle notification; and
in response to receiving the approval indication, transmitting the feature bundle data object to the second client device.