Introduction to class topics and terms followed by a walk-through of kinops Consoles.
As a new developer, you are tasked with creating an Employee Onboarding form for your organization. After agonizing over multiple tools, you wisely chose Kinetic Request CE!
Over the course of the class you will create an onboarding form while learning about and using Request CE. An example of the completed form is available with the first activity.
Onboarding is one of the toughest and most important processes in an organization. It's an employees first exposure to how things work with their new employer.
For the purposes of this class, we are going to simplify things a bit. We only have two days to turn out a process, and we have a lot of material to cover.
Our onboarding form needs to do three things, collect information on the new employee and their supervisor, determine if and what they need for hardware, determine if and what applications that they need.
The class uses kinops, a cloud based version of Request CE that is already configured and includes some background data and forms. Each student has access to their own kinops instance which is available for a short time after class is over.
kinops documentation and help is available at help.kinops.io.
Guides, solutions, and resources for Request CE are available on Community.
Internal Application Documentation
These topics are also available through Community, but be aware that they are updated after any new release is available. Internal application docs are always the most up to date.
Here are some basic terms in use throughout the class.
kinops - A hosted collection of our Kinetic applications that provide a way to "Streamline Everyday Work for Teams".
Queue - Fulfillment system used within kinops.
Services - Collection of Forms used within kinops. They are structured in the model of a Service Catalog.
Discussion - Used within kinops to invite and discuss issues with a variety of people.
Space - A logical partition used for some types of multi-tenancy. Spaces within an instance of the application live on the same database but contain their own data, permissions, and users.
Kapp - A collection of related forms within a Space. A service catalog is a typical example of a Kapp. Kapp stands for "Kinetic Application".
Form - Basic presentation element for kinops and Request CE. Holds questions, text and other elements. Displayed using a bundle/theme.
Slug - URL-safe, friendly name representation used by forms and other resources within the application. Slugs are unique within a Kapp.
Available through the drop-down on the upper left, or along the left side of the main Portal.
To get to the Request CE consoles go to the Admin Console and click on the Kinetic Request link
All of the available consoles are listed under each Kapp.
For the remainder of the class, I will refer to Catalog when describing a Kapp.
Default is the Overview console that includes two different graphs of Submissions, and a list of recently updated forms.
Options along the right side allow you to select a specific form, or filter to a set of forms.
This console holds management information for this Space. There is a separate System console that is covered later.
The default is the Overview console, similar to Kapps. The above Settings console is a little more interesting.
Goals for the class
Fun - please have fun. If you're not having fun, see the instructor.
Each article and activity has a specific goal. In general you should know the following at the end of class.
- kinops navigation
- console management in kinops
- Form Creation including pages, questions, and text elements.
- Bridge Resources
- Consoles for managing Request CE