Kinetic Data – Kapps

Video Transcript

Hello, my name is Arne Holmes and I’m here to talk to you about caps. caps are like containers within a space, or kinetic environment. They allow administrators to organize forms and workflows together and delegate their management with ease. Common examples of caps, our ticketing systems, case management systems, customer portals, or Self Service portals.

Each of these have a distinct user experience and workflows that need to be kept organized. Each created cap will have its own management section that allows cat builders and owners to configure and view the caps sub components, like cap settings, forms, submissions, form types, security definitions, category definitions, attribute definitions for caps, categories and forms and web hooks. settings within the cap scope, like categories form types and security definitions are only available within that one cap and aren’t shared between caps.

Let’s dive into how we could configure a cap. The first part of a cap is the Details tab. This is a read only section that contains the cap name it slug, its time of creation, and who created the cap and the time of the last update and who updated the cap.

You will see the cap name which is often used for display, you will see the cap slug, which is the unique identifier and use for code references and the URL of the cap. There is the submission label that sets the default label for all of the forms and the cap. If this is left blank, the submission labels will default to their submission ID. And lastly, the display page information.

This is either controlled by the space if the space is set to a single page application, or the display page or the redirect URL. If the space is set to a single page application for its display page, you will not receive any options for the display page in the caps details.

The next part of the cap is the Attributes tab. This is where Cap level attributes are set and given a value but not where they are created. The attributes defined on this page are generally things that will be used across all caps, like what bundle package to use, or the caps description, or even an icon. But you can also give values to come and fallback attributes for forums.

In case attributes are not defined at the forum level, such as an approval form slug or a submission workflow. Lastly, we have the Security tab. This section contains four cap settings and four default settings for forms within the cap.

There are cap permissions, the cap display field, which sets who can see and render the cap, the cap modification field, which sets who can make updates to the cap, the form creation field, which sets who can create forms within the cap, and the submission support field which provides some search and visibility features within the cap. There are form defaults, the form display field controls who can see and ultimately submit forms the form modification field controls who can change and update the form.

This is often set to a security definition that includes form developers and platform administrators. The submission display field controls who can see submissions. This is often set to the submitter of the submission and platform administrators. The submission modification field controls who can modify a particular submission.

This is also often set to the submitter of the submission and platform administrators.

That’s really all there is to it. caps are a great way to help keep your forms and workflows organized and control who can create, view, edit and use your forms and their submissions.