מהן תבניות פתרון? קורס וידאו למנהלי ארגון

התמליל להלן הוא התמליל באנגלית של הסרטון, כפי שנאמר בו, והוא אינו מתורגם. לצפייה בחלק מסוים, השתמשו ברשימת הפרקים שלמעלה.

Chapter 1. What a template is

Goal: Understand what a solution template is, what it creates for you, and why it exists.

Welcome to the Kav Studio Academy. This first course answers one question: what is a solution template? A template is a ready-made set-up for one kind of job, such as taking appointments. You answer a few questions, and the platform creates the pieces for you. It is not code. A template is a versioned file, written by the platform team: the questions to ask, and a recipe of what to create. One wizard can draw any template, so every template feels the same to use. Take the calendar template. From your answers it creates the booking form, the calendar capabilities that find times and book them, your appointment types, and the routing that tells the assistant when to offer a booking. It can also link a Google calendar. All of it stays editable afterwards. The result is consistent, and much faster than building by hand.

Chapter 2. The gallery

Goal: Find a template in the Solutions gallery and know what to have ready before you start.

Open Solutions in the Studio menu. This is the gallery of templates available to you. The Available tab lists them as cards. Search by name, description or category, or use the category chips to narrow the list. Each card shows the name, the category, the version, and what the template does. Under it is what you need first. Here: a department that takes the appointments, and a calendar account, which is optional. Each item says whether it is ready. Choose Set up to open the wizard. Seeing the gallery needs the solution read permission. Installing needs solution apply.

Chapter 3. The wizard

Goal: Answer a template's questions in the wizard, part by part, and watch the preview.

The wizard opens on the template's own page: its name, its version, and the environment you are in. Three steps run along the top: Questions, Review and Install. Nothing is created until the last one. Open What this solution sets up to read, in plain words, everything your answers will create. The questions come in four parts here: where bookings go, your services, how bookings look, and what the assistant says. A button at the bottom moves you on. First, choose the department that takes the appointments. Its opening hours decide when people can book. The calendar account is optional, so we skip it. Connecting one is the next course. Now a service: a name, and a length in minutes. Booking hours are optional; left empty, the department's hours apply. Every question has an information mark, with an explanation, an example and the limits. On the right, the panel shows what your customers will experience, and it updates as you type. The last part is the scoping note: one short sentence about what booking is for, and what it is not for.

Chapter 4. Review before anything changes

Goal: Read the review, understand each action, and know why it is safe to continue.

The second step is the review, called What will change. This is the safety net. It is a preview only. The server checks your answers and works out the exact plan. Nothing is written yet. The plan is grouped by the part of the platform that owns each item: assistant, routing and forms; appointments; and connections. Every row has an action. Create means a new row. Already present means nothing to do. Edited by hand means someone changed that row, so the template leaves it alone and shows the differences. Blocked means the row belongs to something else. The licence line tells you whether your plan includes this template. Further down are the routing checks: sample sentences, like I want to book an appointment, that must reach the right capability. A failing check blocks the install. Here, they all passed. If anything surprises you, go back and change your answers. When you are happy, choose Next: install.

Chapter 5. Install and the result

Goal: Install the template and read the result table.

On the Install step you apply the plan. The request is accepted at once, and the work continues in the background. A result table follows each item, from Waiting to Applied. The other outcomes are Already present, Needs your attention, and Failed. Install is safe to repeat. If an item needs attention or fails, apply again, and finished items are not done twice. When everything is applied, Next steps appear: try it in the widget, connect your calendar, and see bookings.

Chapter 6. After the install

Goal: Manage an installed template: edit it, upgrade it, understand drift, and uninstall safely.

After installing, open the Installed tab. It lists every template in this environment, with its version, its status, and when it last changed. Open takes you back into the wizard in edit mode, with your earlier answers filled in. Change one, and the review shows exactly what would change. Everything the template created is ordinary Studio content. Here is the booking form it made, in Forms. You can edit it like any other form. If you edit a row by hand, the template respects that. At the next review the row is shown as edited by hand, with the differences, and it is never overwritten. When a newer version of a template is released, the Installed tab shows Upgrade. Upgrade asks only the new questions, and summarises what is new, changed or removed. You can still choose to edit all the answers. Uninstall switches off the rows the template created. It deletes nothing. Rows you edited by hand stay as they are, and your answers are kept, so you can install again at any time. Uninstall is blocked while there are future confirmed bookings, so nobody's appointment disappears. We will cancel this one and keep the template.

Chapter 7. Recap and what comes next

Goal: Remember the shape of every template, and where the next course goes.

Let's recap. A template is a versioned, ready-made set-up: questions, and a recipe of what to create. It is data, not code. The wizard asks, the review shows what will change, and the install creates it, safely and repeatably. What you edit by hand is never overwritten, and uninstalling switches rows off instead of deleting them. More templates will follow the same wizard, so what you learned here applies to each of them. Next course: connecting a calendar. Thank you for watching.