FAQs

General Questions

What is Jetveo?

The Jetveo Platform and App Builder is a low-code application builder that combines an intuitive user interface with the power of C# language for the fast and efficient development of powerful business solutions.

It enables both senior and junior developers to streamline and speed up the development of a wide range of applications for desktop browsers and smart phones.

The platform is intuitive and user friendly, with a lot of automation, shortcut keys, and templates that expedite the creation of a minimum viable product. Many advanced features are available to customize the app for the end users.

The Jetveo Platform has detailed App Overviews for projects and to delineate access to each app instance. The Jetveo Cloud uses Microsoft Azure to securely maintain all of the data. And the Jetveo App Builder streamlines the development process by handling repetitive tasks, such as establishing databases and building UI, and providing the flexibility of custom C# coding for complex business logic.

What is a low-code platform?

Low-code programming is a system for automating the steps for developing apps, starting from nothing to creating a minimum viable product to having consultations with the client to publishing the app for end users. Intuitive graphic displays guide the user and sometimes custom code can be added.

The end customer gets advanced technology quickly. But low-code programming is especially beneficial for both senior and junior programmers because advanced features and complex code are handled through the intuitive interface.

Do I need to know C#?

The Jetveo App Builder requires a basic knowledge of C#. However, there are many templates to copy and paste available in the Developer Portal.

How do I access the Jetveo Platform and App Builder?

Go to jetveo.io. Establish a free account.

This will give you access to the Development Portal / Development Interface where you can start creating apps and access the Support Portal.

There are two levels of applications:

• Free Applications
• Standard Applications Both are intended for commercial use.

The Free Application is limited to five end users.

The Standard Application is subject to the Price List and depends upon the number of end users and the optional features used.

Who is Jetveo Platform and App Builder for?

The Jetveo Platform and App Builder is for several categories of developers. Only a basic knowledge of C# is necessary:

• Senior developers benefit from the ease with which they can complete the foundational parts of apps. They can customize features with C#.
• Junior Developers can use their modest experience to experiment with more advanced programming. Quick iterations show the results of their work. They can also contribute to larger projects within the multi-person process.
• Entrepreneurial Freelance Programmers can use the app builder to develop business solutions for their own customers and sell their apps on the marketplace.
• IT Departments can use the app builder to work as a team on more complex apps, then make quick in-house corrections, adjustments, and enhancements on the fly.

How experienced should you be to effectively use Jetveo?

Jetveo has an intuitive interface that empowers users with only a basic level of computer knowledge.

Junior programmers and users with no experience should be able to build a simple app, like for an internal workflow (which would include data management, menu, UI, state machine). The development of these aspects would essentially be of the no-code style.

However, there are several places where users would benefit from knowing how to code in C# in order to fully utilize the whole platform. This would enable the building of complex apps, like ERPs with integrations. These would require a basic knowledge of C#, LinQ, Enity Framework, and Rest APIs. In general, C# will allow you to write your own code when necessary, then very basic LinQ and Entity Framework expressions are used throughout and Rest and CRUDL APIs will help you connect to other applications/systems.

What is the Partner Program?

Individuals and companies can join the overall Jetveo organization. You can expect a startup environment without unnecessary bureaucracy, where you have room for your own ideas and solutions. Thanks to the broad scope of our platform, there is a wide range of areas to pursue.

There are many advantages of the Partner Program, including speeding up customer development, becoming part of a network of experts to share knowledge and contacts, training and certification, a service-level agreement, a direct line to Jetveo for suggestions, savings to increase your revenue stream, and an incubator for young talent.

Can I download the source code of apps that I build?

Yes. However, this is an option feature that has a nominal cost.

What types of apps have been created with the Jetveo Platform and App Builder?

Many different types of businesses have benefited from applications that have been built on the Jetveo Platform. Apps have been created for the following basic functionality:

• Warehouse Management
• Meter Reading
• Decommissioning workflow
• Commissioning workflow
• Approval workflow
• Headless CMS
• SPA
• Enterprise Resource Planning (ERP)
• Facility management
• Mobile back end application
• Report Generator
• Customer Relations Management (CRM)
• Online contracts
• Securing Passwords

What makes Jetveo different?

The Jetveo Platform and App Builder is in the sweet spot between classic programming and a low-code platform. This provides the best of both worlds: the flexibility and power of C# and the intuitive simplicity of a low-code platform. It streamlines the development process in many ways:

• Fast Development. Using established procedures and building upon existing foundations speeds up the creation process because developers are not required to write the same code again and again and they do not have to reinvent the wheel each time.
• Minimum Viable Product. Using the logical step-by-step process develops the core of the applications so that they can more quickly be made available, without having to wait for the attachment of every feature. Providing an MVP provides the customer with access sooner in order to keep them involved to provide important feedback and customization options.
• Short learning curve. It does not take long for new users to get up to speed on the platform. This reduces the time necessary for training and more quickly gets the developer working on paying projects.
• Tools. All of the necessary tools are available for building, testing and running your applications. Enhancements and bug fixes can be made quickly for a new iteration.
• Accumulating Experience. Junior and novice developers can use the intuitive interface to start working immediately, getting their hands dirty and providing a real-world learning experience.
• Team Concept. Large and complex projects can be broken up into small pieces so that multiple developers can work at the same time and handle their personal expertise, like database creation, back end development, and front end development, before all of the parts are merged together into one.
• Intuitive User Interface. The step-by-step process is intuitive and similar to general-audience coding platforms. Shortcut keys are available throughout. And automation removes a lot of repetitive work.
• Cloud Storage. Maintain data and coding in a safe and secure cloud, which makes it all available anywhere with internet access.
• Potential. Apps can handle a wide range of features, including: Digitalization and ability to work with data; the development of Smart Forms; simple procedures for Approvals; the establishment of logical Workflows; well-defined Document Management; development of a Mobile Back End as the foundation for the Mobile Front End user interface; Integrations with any number of other apps; and a modern feel for normal operations.
• Professional support. The Developer Portal is packed with information and examples for efficiently using the Jetveo Platform and App Builder. There are also tutorials that can be followed, step-by-step or reverse engineered.
• Proven past performance. Jetveo has been used to develop apps for a wide range of business, including international cultural leaders (National Theatre of Prague), innovative textile producers (Bamboolik), a network of advanced preschools (Elanek), a municipality that wanted to streamline the process of reading meters (Hradec Kralove, Czech Republic), document enhancements for financial and insurance companies (Avant, Allrisk, finGood and two German companies that manage hundreds of properties.

How does the Jetveo App Builder work?

Every developer and programmar is different. However, the most common development process starts at the top of the side bar menu and moves down through each section from Data to UI to Business to Code to Config to Security to Integrations.

In other words: 1, define the data model; 2, modify the UI; 3, create workflows and implement business logic; 4, add components and/or provide custom coding; 5, configure the app; 6, implement the security; and 7, Release the source code.

Then, on the App Overview, create an instance, start the instance, and access the app through a web browser.

How do I save my work?

Saving pages as you build apps is important because they often fit together and drop-down menus will only be populated when the tabs have been saved.

To save the page on which you are currently working, click CTRL + S.

If you have multiple unsaved tabs, click CTLR + SHIFT + S to save them all.

PLATFORM OVERVIEW

The Jetveo Platform has two main sections: the Workspace, which has App Overviews and diagnostic statistics, and the App Builder, which is where the source code is developed.

Workspace

The Workspace is where you are when you log in.

The topbar has several features (from left to right):

• the Jetveo logo;
• the name of the workspace;
• the search feature;
• a link to open the Developer Portal side panel; and
• access to user information, with a drop-down menu to switch to other Workspaces (and create a new Workspace to help organize projects and access) and a link to log out.

The sidebar has two sections: Apps and Admins.

• Apps is the default initial page (see above) and it shows the list of apps related to this workspace. The main section of the workspace page includes the following:
  • + Create App is at the top of the sidebar and in the middle of the page.
  • Each App Package is listed, with related instances.
    Click on the App Package to get specific details and statistics on the App Overview (see below). Apps can have multiple instances.
• Admins provides the list of users who have access to this workspace.
  • Click “Invite” to provide additional users with access to the workspace.
  • Only the name and email is necessary for the invitation.

How do I create a new Workspace?

At the far right of the platform top bar, click the user name. Select My Workspaces. This will show all of the Workspaces that exist for the user.

Click Create New to establish another Workspace. It requires only the title for the Workspace.

App Overview

What are the different parts of the App Overview?

The App Overview has details, basic information, useful links and statistics about the app and its related instances.

The leftmost box has details about the app.
Application – Shows the version of the App that is shown.
Current version – Shows the number for the active release that is currently in the App Builder and being worked on.
Release Version – Shows the version of the source code that was part of the most recent release.

Edit Application — Access to the App Builder.
+ Create Instance — Access to the dialog box to create Development and Production instances.

More actions:
Release history — List of releases, with the ability to create forks for testing purposes.
Publish on store — Link to publish the app and make it available for other developers.
Delete application — It is possible to delete the entire App Package. However, know that each instance needs to be deleted first (i.e., on the App Overview, go to the instance; click More; then click Delete. Confirmation is required.) Confirmation is required to delete the App Package and all of the source code.

The rightmost box shows the different instances related to the app.
Several actions are available across the top:
Update App — Press this button to implement the source code that had just been released.
Stop/Pause — Binary toggle that allows the user to make the application available or make it idle. This is connected to the colored circle to the left of the Instance name: Green means that the instance is running; orange means that the app is in the process of being started or stopped; and red means that the app is not in operation.
Settings — Link to the Development Settings overview, including tabs for General, Dev Instance, Configuration, Features, API and DMS. Dev Instance, which is available only for Development instances, includes the Test User Email and Test User Password, which are necessary for logging into the Development version of the app.
Errors — A grid to show errors within the instance, including when it occurred, the state, the context, the error, Detail and Actions.
Users — For Development Instances, this is a direct link to the Settings > Dev Instance tab. For Production Instances, this links to the list of users who have access to the app.
+More — Three additional options are available (depending on the state of the instance): Download API SDK; Office adding manifest; and Delete.

The body of the app instance box shows updated information and settings for the following, which may change according to the state of the instance. The first column shows:
Open Instance — Opens the instance in a web browser.
Open Instance preview — Opens the instance in a web browser, which is updated as soon as pages are saved on the App Builder.
All Instance URLs — This drop-down menu show the URLs for the different versions of the App instance, which is useful for copy-and-pasting for personalized email communication or sending to a mobile device for testing.

The lower left corner identifies the instance as Free or Standard.

The second columns shows:
Development
Free application instance
Cloud environment
Jetveo authentication

The third space includes donut charts for the following statistics:
Users
Data Storage
API Calls

——————

Development Settings

What is the different between a Development Instance and a Production Instance?

The source code developed in the App Builder is made available on the internet through instances. There are two different types: Development and Production.

Both instances are shown in the App Overview. Click Create Instance to establish a new instance. Each instance can be started and stopped. They should be updated after each release of the source code with the Update App button. Click Settings to access the basic information.

Development
Development Instances are mainly used for testing. There is access for only one user for testing purposes.

Production
Production Instances include access for all users who are added through the App Instance Overview. Click “Users”. You can define to locations to which users can go. Even the developer must provide themselves with access to the Production version of the app.

How do I establish Development Settings?

The Development Settings are the basic settings for the app instance. There are six tabs.
General – The General tab is the default setting and includes basic information.

Instance
Name — This is the name that is used for the instance on the App Overview and within the App. “DEV” is added by default.

Domain
Custom Domain — Mark the checkbox to establish a domain that is different from the default setting.

Dev Instance – This tab includes basic access to the instance.
Test User

• Test User Email — The default setting is test@test.com
• Test User Password — A password is randomly generated. It can be changed to a more memorable password to facilitate access to the app instance.
• Test user Security Roles — If Security Roles were developed as part of the app, the Test User can have specific roles assigned in order to create different scenarios.
• Test User Security Claims — If Security Claims were developed as part of the app, the Test User can have specific claims assigned in order to create different scenarios.

Developer Support
Enable Release Preview Development — This toggle between “yes” and “no” defines whether the preview instance features is turned on to facilitated the fast generation of the updated app.

Configuration –
Features – Some features, like Email Notifications, are established in this tab.
API –
DMS –

App Overview

I forgot my credentials to access the app. Where can I get them? and How do I change my credentials to access the app?

On the Platform Workspace, go to the appropriate App Overview. Select the appropriate App Instance.

• For a Development instance, click Users (or click Settings and go to the Dev Instance tab). Test User Email and Test User Password are in the first column.
• For a Production instance, click Users to see the list of people who have been granted access to the app. Locate the user and click Detail to get their Login. Click Reset Password to send an email to the user with a new password.

How do I define where administrators and users can go in the app?

Apps can be designed so that users are allowed to access only designated areas. This is done through Security Roles and Security Claims. Both are established in the App Builder in the Security section.
Security Roles are general categories, like Administrator, Manager, Customer, or Accountant, in order to define the areas and functions to which they have access.
Security Claims define the areas and actions, like Can See Financial Reports or Can Change Employee Data, that are available to the user

How do I delete an application?

There are two steps to deleting an application.
1. Delete instance. On the App Overview, go to the instance. Go to More and click “Delete”. Confirmation is required.
2. Delete app. On the App Overview, go to the first column. Click Delete Application to delete all of the source code. Confirmation is required.

For what is the “Play” / “Pause” toggle in the upper left of the app instance?

This toggle button defines whether the app is actively in operation. Click “Pause” to idle the app so that it does not make API Calls, send schedule messages, or follow business-command triggers. Click “Play” to turn on the app.

Note that the color of the circle to the left of the instance name reflects the state of the app: Green means that the instance is running; orange means that the app is in the process of being started or stopped; and red means that the app is not in operation.

For what is the “All Instance URLs” link?

If you don’t want to access the app through a browser this option provides the URLs for both the Application URL and the Application Preview URL. This makes it easy to copy-and-paste the URLs in notes or emails.

How do I host an application on-premises?

You typically want to have some kind of full web-server in front of Jetveo App. This server should work as a "reverse-proxy" which handles https certificates and security.

Following example shows IIS configuration as a reverse proxy in web.config file:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="ReverseProxyInboundRule1" stopProcessing="true">
                    <match url="(.*)"/>
                    <action type="Rewrite" url="http://localhost:8080/{R:1}"/>
                </rule>
            </rules>
        </rewrite>
        <security>
            <requestFiltering allowHighBitCharacters="true"/>
        </security>
    </system.webServer>
</configuration>

App Builder

What are the parts of the Jetveo App Builder?

The Jetveo App Builder is where the source code for apps is programmed, edited and maintained.

On the Jetveo Workspace, click “(+) Create App”. Or, locate an existing App and click the name; on the App Overview, in the leftmost box, click Edit Application.

The Jetveo Apps Builder has a topbar, a sidebar menu, a side panel menu, the editor section, and, if necessary, the Developer Panel on the right. The Status Bar is across the bottom.

Topbar

The top bar of the App Builder is similar to top bar on the Workspace; however, the page title has been expanded with links to the Workspace and the App Overview. The features are (from left to right):

• the Jetveo logo;
• the name of the Workspace (which links to the Workspace) / the name of the application (which links to the App Overview) / the version of the application;
• the search feature;
• a link to open the Developer Side Panel and access helpful information; and
• access to the user account information, with a drop-down menu to switch to another workspace connected to the user account and a link to log out.

Return to the Workspace in two different ways: click the Workspace name or, in the user account section, click “Switch workspace” and select the appropriate destination.

Return to the App Overview in two different ways: click the App name or, at the bottom of the sidebar, click “Close”.

Sidebar Menu

The sidebar has icons that link to different sections of the App Builder, which have subsections for building and editing the app. The main sections are (see below for more details about each section):

• Data
• UI
• Business
• Code
  —
• Config
• Security
• Integrations
  —
• Release
• Close

The top sections (i.e., Data, UI, Business, Code) are directly related to the building and editing apps. The middle sections (i.e., Config, Security, Integrations) establish settings for the usage of the apps. The bottom has two operations: Release will implement or update the source code; and Close will take the user to the App Overview to access the source code through an app instance.

Side Panel Menu

Click on any section in the sidebar to show its subsections in the side panel. The default presentation is to show the Data subsections.

Subsection headers include the name (i.e., Entities), a create button (i.e., (+)) and a create folder button (i.e., [Folder +]). When new pages are created, they are listed in the space below, where they can be organized in folders. Each section can be expanded or minimized (i.e., the caret symbol to the left of the name).

Double-click pages to open them into the Editor (see below).

The subsections can be reduced/expanded vertically by placing the cursor over the topline and dragging it to the desired height. The side panel can be reduced/expanded horizontally by placing the cursor over the rightmost line and dragging it to the desired width.

Subsections in each of the sections are similar (see below for more details).

Editor

The work of the App Builder is done in the Editor.

The initial display will show the name of the App, the version and useful shortcuts. Pages that are created and settings dialogs appear in the Editor.

Each page that appears in the Editor will have a tab across the top. Names in blue are tabs that have been saved. Names in brown and that show an asterisk are tabs that are not saved. Click [CTRL + S] to save the tab that is open in the Editor. Click [CTRL + SHIFT + S] to save the tab that is open in the Editor.

Developer Panel on the right (if necessary)

Support is always just a click away. Click the (?) key in the topbar to open the Developer Panel on the right. It provides on-screen information to explain different aspects of the App Builder.

Feedback (if necessary)

Jetveo is always interested in feedback, whether it is positive comments or constructive criticism to make the platform better. Click the ! in the speech bubble to provide feedback.

Status Bar is across the bottom.

The App Builder provides status information as you develop your apps. The number of Errors (i.e., “(x)”) and Warnings (i.e., “/!\”) are listed in the Status Bar at the bottom of the page.

Note that both errors and warnings are shown each time a page is saved. These are removed when subsequent steps are taken. In other words, it is best to complete the basic settings before consulting the Status Bar.

Data

The Data Section establishes the foundation for the app. It has four subsections: Entities; Codebooks; Aspects; and Search Indexes.

Entities

What is an Entity?

Entities are the building blocks of an app. They serve as storage devices. They are made up of attributes that hold data. For example, a Support Ticket App would likely have an entity named “Ticket”. It would be filled with information related to that ticket, including the title, when it was created, the description of the problem, and to whom it is assigned.

The entity is accessed through three pages on the User Interface (which are created automatically as part of the entity-creation wizard).

• The entity’s Create Page (i.e., Ticket Create page) is what the end user will see when they access the app and add information.
• The entity’s Detail Page (i.e., Ticket Detail page) is the page that is generated from the information provided on the Create Page, plus additional elements, like a kanban workflow, the ability to add attachments, a comments section for internal communication, and a change log. It is where changes are made after the initial creation.
• The entity’s List Page (i.e., Ticket List page) is a simple list of the entities with basic information and a link to the Detail pages.

Entities are connected to other entities and to codebooks. For example, if the Ticket Detail page includes the ability for the user to add an Attachment (i.e., a screenshot, document, image), then that attachment would need to be maintained in a separate entity, most likely one called “Attachment”. This Attachment entity would then need to be connected to the Ticket entity as a Composition reference type: One Ticket List can have several Attachments.

Codebooks

What is a Codebook?

Codebooks, which are sometimes known as Static Lists, are data that does not change. It is used to establish the basic values that are used throughout the app. For example, in the Support Ticket app, tickets can be designated according to their status: New, In Progress, Closed. These are foundational values that do not change. (And they cannot be changed in the source code except through a new release.)

Aspects

What are Aspects?

Aspects are sets of attributes and references that can be added to Entities, Codebooks, Aspects, and Business Commands to eliminate repetitive work.

For example, many apps include elements that require timestamps for each step of a workflow, like Requested Date, Created Date, Accepted Date, Assigned Date, Progress Date, and Finished Date. Rather than create each attribute anew whenever you create a new entity, you can simply include the shared aspect.

The aspects can be created as a shared aspect from scratch or they can be created in an entity and then designated as a shared aspect.

Search Indexes

What are Search Indexes?

The Search feature enables users to quickly locate information within an app. For example, three letters can be input to locate the title of a Support Portal ticket. The specific index can be defined according to specific attributes. Additionally, a prefix can be used to narrow the search results, which is particularly useful when multiple entities are included. For example, enter "T" to limit the search to only a specific entity.

UI

The UI section defines the presentation of the app so that data can be added and used. It has four subsections: Application Menu; Entity Pages; Shared Views; and Dashboards.

Application Menu

What is the Application Menu?

Apps have an established top navigational menu that crosses horizontally at the top of the app. Links can be added to it. For example, a Support Ticket app might have a link to the Ticket List and a link to the Create page in order to create a new ticket.

Entity Pages

What are Entity Pages?

There are three different types of entity pages: Create Pages, Detail Pages, and List Pages.

Create Page
The Create Page is what the end user will see when they access the app and add information.

There are five parts to the page:

• The General section includes the basic information.
• The UI section includes elements like icons and the page title and subtitle. It also determines where the information goes after it is saved.
• The Security section defines who and when the page will be shown.
• The Public Access section defines whether and how the page will be shown to a public user.
• The Layout section is the main area for the layout of the page. Information can be added as a header. Specific Actions (e.g., a button to “Send Email”) can be added. And many components are available in the Layout Editor.

Note that some components do not fit in the Create Page. For example, Attachments cannot be added to a Create Page; they can only be added to a Detail Page after the element has been added.

Detail Page
The Detail Page is the page that is generated from the information provided on the related Create Page. It can also include additional elements, like a kanban workflow, the ability to add attachments, a comments section for internal communication, and a change log. It is where changes are made after the initial creation of the page.

There are five parts to the page:

• The General section includes the basic information.
• The UI section includes elements like icons and the page title and subtitle. It also determines where the information goes after it is saved.
• The Security section defines who and when the page will be shown.
• The Public Access section defines whether and how the page will be shown to a public user.
• The Layout section is the main area for the layout of the page. Information can be added as a header. Specific Actions (e.g., a button to “Send Email”) can be added. And many components are available in the editor layout, including the kanban workflow, the ability to add attachments and more.

List Page
The List Page is a simple list of the entities with basic information and a link to the related Detail Page.

There are seven tabs on a List Page:

• General – Four sections have basic information, General, UI, Actions and Data.
• Columns – Determine the columns that will be included on the list page.
• Highlights – Ability to highlight a specific column and information.
• Filters – Defines the ability to control how the data on the page can be organized.
• Filters layout – Defines the layout for how the filtering will be applied.
• Commands – Defines the specific actions that can be implemented on the page.
• Batch commands – Defines the actions that can be used to affect multiple parts of the page (e.g., Delete All)

Shared Views

What are Shared Views?

Layouts can be saved and transferred between pages. Often, the layout of a Create Page is replicated at the top of the Detail Page. Designating the layout of the Create Page as a Shared View will share time and keep the layout consistent. Plus, if a change is made on one page, it will be automatically made wherever the shared view has been implemented.

The Shared View can be created as a Shared View from scratch or it can be created on a specific page and designated as a Shared View.

Dashboards

What are Dashboards?

Dashboards are the main view for an app. The layout is similar to that of a Create or Detail page, with the opportunity to add Actions (i.e., action buttons) and the ability to implement components (i.e., kanban dashboard).

There can be multiple dashboards, with access defined through the Availability Expression.

Business

The Business section defines the different mechanisms that are available within the app. It has four subsections: Commands; State Machines; Business Events; and Scheduled Tasks.

Commands

What are Commands?

Commands are part of the business logic of the app. They define actions that will occur or pages that will be shown at specific points.

The main page includes four sections:

• General
• UI
• Security
• The workspace, which includes three tabs: Code, Model and View.
  Code — Space to provide custom C# coding to define an action.
  Model — Space to include specific Attributes (including Inherited Attributes) and References to facilitate the results of the command.
  View — Layout editor to define the page that will be produced. It is similar to a Create or Detail page.

Example 1: You can define that, if there is a change to text of a Support Ticket app, the app will generate a specific piece of information for a Change Log.

Example 2: You can define that as soon as a manager assigned a task to a user, an automated email will be sent to notify that user.

State Machines

What are State Machines?

State Machines provide the framework for a workflow. They are defined according to a codebook, which contains values that do not change. Transitions (and conditions that allow those transitions) can be established. Plus, additional actions can be added to produce a result according to the specific conditions.

For example, the Support Ticket app could have a workflow that moves tickets from New to In Progress to Closed. New could be linked to In Progress and In Progress could be linked to Closed, but a link need not exist between New and Closed. Furthermore, a Transition Condition could be established to preclude tickets from being Closed unless the condition is fulfilled.

Business Events

What are Business Events?

Business Events define triggers that will allow a certain action to occur. Business Events define the actions that are possible for specific Business Commands. Depending upon the event, there are sections to define the Trigger, the Child Changes and the Attribute Changes.

Scheduled Tasks

What is a Schedule Task?

Business Commands can be automated so that they occur on a specific day and/or at a specific time.

Code

The Code section enables the user to add custom coding to the basic settings defined in the sections above. It has three subsections: Custom Code; Templates; and Global Usings.

Custom Code

What is Custom Code?

C# coding can be brought into the app through the Custom Code feature. Establish the code with a specific name. Use that name in Business Commands, Templates, and other places to customize the actions of the app.

Templates

What are Templates?

Templates define a specific part of the app. They can be brought into several different parts of the app according to the name of the file. For example, the text of an email can be established as a template to which the Business Command will connect.

Global Usings

What are Global Usings?

—

Config

The Config section defines the basic configurations of the app. It has four subsections: Package Settings, which are listed as App Settings, Resources, and Translations; App Configuration; App Features; and Technical Users.

How do I change the name of my Application Package?

In the App Builder sidebar, go to the Config section. Click “App Settings”.

The text entered for “Application Name” will be used as the overall name on the App Overview. Related instances can be provided slightly different names.

What are App Settings?

App Settings define the basic settings for the App, including Application Name, Version String, Company Name and Application Logo.

What are Resources?

This is the repository for different building blocks that are used in the app. Four different types of resources can be added:

• Add Application Resource
• Add Image Resource — Upload logos and images that are to be used in the app.
• Add External Assembly Resource —
• Add NuGet Package Assembly Resource — Locate NuGet Packages that will be implemented into the app, like an email server for email notifications.

How do I add a logo to my app?

Logos need to be uploaded and then set in the Development dialog. They can be used for the login page for end apps and at the top of the end app.

The logo should be transparent. The recommended size is 500x500. Horizontal logos can be no more than 500 pixels in width. Jetveo supports the following formats: Png and Jpg.

1. Upload image In the sidebar, click CONFIG. In the Config Side Panel, locate the Package section and click “Resources”. Click “Add Resource”. Select “Add Image Resource” from the drop-down menu. Select the image file to upload. NOTE: Make sure to save the page to make the logo available. You may need to refresh the browser, too.

2. Set image in App Settings dialog In the sidebar, click CONFIG. In the Config Side Panel, go to App Settings. Click “Application Logo” and select the logo from the drop-down menu.

How do I translate the text of my app into different languages?

The text of an app can be quickly translated into different languages. English, Czech, and German are currently available.

The language of the online version of the app will match settings of the web browser. For example, if Czech is the main language selected in the Settings, then the Czech version will be shown. Otherwise, the default version (i.e., the language in which the app was created, will be shown). The app can be translated into all three languages at the same time.

Note: Close all of the open tabs in the App Builder topbar so that the translations will have access to every page.

In the App Builder sidebar, go to the Config section. At the top of the side panel, click “Translations”. Select the language in which the original version of the app was created.

User Interface
On the top line, to the left of the language, click the Copy icon.
Locate (+) Add Language in the upper right.
Select the language into which the source language will be translated.
—
Open a new web browser tab and type: deepl.com
Paste the original text into the leftside box, which is labeled “Detect Language”
Change the rightside box to the language you chose in the App Builder.
Copy all of the translated text.
Return to the Jetveo translations interface.
— Click into the top data box of the new language.
Paste the translated text.
Spot-check the translations to make sure that unique words are translated correctly.

Repeat the process for Codebooks.

App Configuration

App Features

Technical Users

Security

The Security section establishes the settings to control who has access to the app. It has three subsections: Data Access; Security Claims; and Security Roles.

Data Access

Enables you to set security conditions for Create, Update, and Delete Operations and access to Detail and List pages of all entities in the app.

Security Claims

Claims are essential elements of application's security. They are used to prevent users accessing certain pages, viewing sensitive fields of information, and editing important entities. Security Claims can later be grouped into Security Roles.

Security Roles

Security Roles are collections of Security Claims, that can be assigned to the user of the app. For example, the Accountant has access to financial data but not personnel files and a Human Resources staff member has access to personnel files but not financial data.

Integrations

The Integrations section defines who third-party software is incorporated into the app. It has three subsections: CRUDL APIs; Command APIs; and MS Office Addins.

CRUDL APIs

Command APIs

MS Office Addins

—

Release

When the basic pages of the app have been established — and when the Status Bar is clear of errors — the Release button will create or update the source code for the app.

Instances then need to be updated and started in order to access the app.

Close

The Close button at the bottom of the sidebar closes the App Builder and takes the user to the App Overview.