Skip to main content
Users can build and install “Applications” in Tenants to extend the functionality of the Kibo Platform and integrate with external systems. Applications can have multiple versions with behaviors and events specific to each version.To create a new Application, in KIBO’s Dev Center, click the “Develop” dropdown at the top of the page. Then click “Applications”. Users can build and install applications and tenants to extend the functionality of the kibo platform and integrate with external systems applications can have multiple versions with behaviors and events specific to each version. To create a new application in. Kebo’s Dev Center, click the drop-down at the top of the page. Then click applications. This will take us to the “Applications” menu. All existing Applications will be listed here. To create a new Application, we’ll click the “Create Application” button on the top right. This will take us to the “Applications” menu. All existing Applications will be listed here. To create a new Application, we’ll click the “Create Application” button on the top right. This will open the “Create Application” modal window, where we’ll give the new Application a required “Name” and “Application ID”. When we’ve provided the required details, we’ll click “Save”. This will open the “Create Application” modal window, where we’ll give the new Application a required “Name” and “Application ID”. When we’ve provided the required details, we’ll click “Save”. To view the Application we just created, select its row on the Applications menu. To view the Application we just created, select its row on the Applications menu. In the top row of the Application detail page, we’ll find key information about the Application, including its “Status”, “Version”, “API Version”, “Application Key” and “Shared Secret”, and “Active Package”.The available “Statuses” for an Application are “In development” and “Certified”. When a “Version” of an Application has been “Certified”, meaning it has been approved to be installed on a production tenant, it is locked down and everything about that Application is frozen. After an Application is “Certified”, its version will be “incremented” and the latest version will have the status of “In development”. We can also create different “Packages” of an Application if we need to manage it across multiple tenants or want to have different Applications that we can install. Each Package can also have its own “Version”. Only the “Release” Package can become “Certified” and deployed to a production tenant. In the top row of the Application detail page, we’ll find key information about the Application, including its “Status”, “Version”, “API Version”, “Application Key” and “Shared Secret”, and “Active Package”. The available “Statuses” for an Application are “In development” and “Certified”. When a “Version” of an Application has been “Certified”, meaning it has been approved to be installed on a production tenant, it is locked down and everything about that Application is frozen. After an Application is “Certified”, its version will be “incremented” and the latest version will have the status of “In development”. We can also create different “Packages” of an Application if we need to manage it across multiple tenants or want to have different Applications that we can install. Each Package can also have its own “Version”. Only the “Release” Package can become “Certified” and deployed to a production tenant. After our Application has been created, “Behaviors” need to be “Enabled”.To Enable these “Behaviors”, on the left “Packages” tab, we’ll select the “Behaviors” tab. After our Application has been created, “Behaviors” need to be “Enabled”. To Enable these “Behaviors”, on the left “Packages” tab, we’ll select the “Behaviors” tab. The “Behaviors” modal allows users to have granular control over the API calls this Application is authorized to make. This is a critical step in defining the scope and permissions of an “Application”.We can choose from a variety of options, including “Cart”, “Discount”, “Extensibility”, “Order”, “Product”, and more. Each Behavior can be further configured with granular permissions, such as “Read”, “Update”, “Delete”, and “Create”. This level of control ensures that the application only has access to the data and functionality it needs.Important Note: recommended configuration is to limit each Application to only the necessary behaviors for it to serve its function. The “Behaviors” modal allows users to have granular control over the API calls this Application is authorized to make. This is a critical step in defining the scope and permissions of an “Application”. We can choose from a variety of options, including “Cart”, “Discount”, “Extensibility”, “Order”, “Product”, and more. Each Behavior can be further configured with granular permissions, such as “Read”, “Update”, “Delete”, and “Create”. This level of control ensures that the application only has access to the data and functionality it needs. Important Note: recommended configuration is to limit each Application to only the necessary behaviors for it to serve its function. The final step is to install the Application onto the Tenant. To do that, we’ll click the “Install” button on the top right. The final step is to install the Application onto the Tenant. To do that, we’ll click the “Install” button on the top right. On the “Select a Tenant” modal, we’ll choose a Tenant from the list. This will deploy the Application to the selected Tenant, making it accessible for use. On the “Select a Tenant” modal, we’ll choose a Tenant from the list. This will deploy the Application to the selected Tenant, making it accessible for use. After initiating the installation, the Tenant will populate in the “Application installations” section of the Application, indicating a successful deployment. After initiating the installation, the Tenant will populate in the “Application installations” section of the Application, indicating a successful deployment. We can also verify that the Application is installed on the selected Tenant by navigating to the Tenant’s Admin UI.In the left menu, on the “SYSTEM” tab, click “Customization”, then click “Applications”. We can also verify that the Application is installed on the selected Tenant by navigating to the Tenant’s Admin UI. In the left menu, on the “SYSTEM” tab, click “Customization”, then click “Applications”. All applications configured for this Tenant will be listed on the “Applications” menu. We can select any Application here by clicking on it. All applications configured for this Tenant will be listed on the “Applications” menu. We can select any Application here by clicking on it.

Want to learn more?

Get Started with Applications

Learn more about this topic

Application Development Requirements

Learn more about this topic