These modules focus on a specific capability to help solve either a business problem or a specific functional requirement.
Springboard consists of one foundation module that enables the framework and provides some core capabilities and a number of non foundation modules that can be independently installed and utilised. Each module can be used individually and interdependently of each other. This gives users the ability to deploy only the necessary modules to cater for their business or technical requirements. Each module can be installed using K2’s Package and Deployment tool. A module comprises of:
- One or more purpose built reusable components that exposes the functional capability of the module
- A set of supporting artifacts that help faciilitate the configuration and execution of the components
Example of a business module:
Example of a business problem module would be a KPI Module that enables the implementation and management of KPI’s across a solution.
Example of a functional module:
Example of a functional module would be a Address Module that enables the ability to turn any control into a address autocomplete.
To see a list of current and in development modules go to the modules section.
A view component is a reusable view that exposes the capabilities of a module. Multiple view components function as part of a module, which can be used in new or pre-existing K2 solutions and are completely reusable.
You can apply the modules to any pre-built K2 solutions by adding our Foundation Loader View Component which will allow you to utilise the extent of all our other View Components on your platform. Examples of View Components:
The Loader View Component of the foundation module is responsible for loading the framework for all other modules to work.
The Theme View Component of the foundation module is responsible for applying styling to the page.
View Component Types
View Component Types can be broken down into the following:
- [View] as in ViewComponents – K2 view that can be dragged and dropped onto any form that has the SBM4K2.Foundation.Components.Loader.
- [Logic] as in LogicComponents – K2 smartobjects that incapsulate logic that can then be utilised in any K2 workflow, view or form.
- [Workflow] as in WorkflowComponents – K2 workflow processes that are intended to be reused.
How do I get access to Springboard Modules for K2?
In order to install Springboard Modules for K2 on your environment, you will need an to request an API Key. You can request an API key by sending us a message via our contact page.
How do I use Springboard Modules for K2?
- Once you have requested and applied your API Key to gain access to Springboard Modules for K2 on your environment
- In your K2 Designer, drag the following View onto your Form SBM4K2.Foundation.ViewComponents.Loader
- Rule execution for the form will only be executed once the Springboard Module for K2 has completely loaded.
- Make sure that the SBM4K2.FoundationViewComponents.Loader is the first action being executed with the View Initalized execution method on the Form is Initializing Form rule.
- Once you have completed the above, you can add any other rules as well as drag and drop any other module view components onto the page.
In the K2 Designer, click the View Knowledge Base to understand how each Module works/if you need additional information.
Springboard Modules for K2 provides a debugging ability by utilising a hidden view called “Table Debug.” To get this working at Runtime, you need to run the Form and append the URL with “sbmdebug=true.”
Devmode is a runtime capability to assist with applying setting to your K2 forms.
To enter DevMode append sbmdevmode=true to the forms query-string and your will see a top bar appear showing that you are now in DevMode: