UDesigner

Classic Designer

Like traditional web applications, Unqork applications are also web-based and can perform the same tasks and processes. Unqork applications can be module-type or workflow-type applications. Module-type applications let you take advantage of Unqork's Module Builder and its various components to build applications. Workflow-type applications are typically process-specific, letting you create applications that an {{glossary.end-user}} can navigate. The versatility of Unqork applications lets you combine modules with workflows to perform any task you require.

Working With Multiple Applications

While we’ve defined the two types of applications in Unqork, many times "application" is an umbrella term to describe an application that consists of multiple applications. Let’s say you're creating a meal-delivery application where customers submit a meal order. Then, a driver picks up the meal from a hub and delivers it to the customer. This application might consist of multiple applications designed to execute the following functions:

Customers use one application to create the order and submit it to the hub.
Drivers use another application to create a profile and select a delivery shift.
Another application assigns routes to drivers based on their availability.

Each application in this example might also have its own respective schemas (orders, drivers, shifts, and routes) defined by a data model. This data model's overall goal is to deliver meals to customers. So, each application contributes to your overall meal-delivery application.

Creating an Application

To create an Unqork application, you must have a workspace to store it. Once you have a workspace, you can create one or more module-type or workflow-type applications inside it.

Navigate to the workspace where you want to create an application. At the top right of your open workspace, click + Create App. A {{glossary.modal - LC}} displays with two tabs for customizing your application. After completing the configuration of your application, click Create.

If you create an application from your homepage, you are required to assign it to a workspace.

App Details

The App Details tab is where you set up the basic application configuration. This tab lets you assign an application name, select an application type, define the application's entry point, and so on.

Setting	Description
App Name*	Enter a unique application name. It's best practice to choose a name that helps you and your team identify the function of the application. Entering a name for your application populates the App Path field in a concise URL format. *The App Name field is required.
App Path*	The URL-friendly format of your application's name. This field can be modified or left with the default path. *The App Path field is required.
App Type*	Use this drop-down to set this application as a module-type or workflow-type application. Depending on your selection, a module or workflow is automatically created in the application. *You must select an App Type.
Module Type*	Available for Module App Types. After selecting the Module App Type, you'll use this drop-down to select a Module Type of API, Front-End, or Other. To learn more about Module Types, view our What Is a Module? article. *You must select a Module Type.
App Entrypoint*	Specify the module end-users are directed to when they access the application. Or, select New Entrypoint to set the module or workflow as the starting point. Once selected, you must define the entrypoint's module type. *You must assign an App Entrypoint.
App Description	Use this field to add a description of this application.

Advanced Settings

The Advanced Settings tab lets you control your application data by enabling data and application versioning, as well as styling your application.

Option	Description
Data Versioning	Determines how long data persists in modules. When enabled, Unqork stores all submission revisions belonging to the application. Disabling this setting hides the WORM Storage setting. By default, Data Versioning is set to (ON). If this setting is set to (OFF), Unqork does not create a revision for the application’s entrypoint module. But a revision is created for all other application modules, regardless of whether the setting is enabled.
Enable Application Versioning	Enables Creators to create copies of the application. When set to (ON), Creators can create a new version of the application at any time, retain historical versions for stability, and view and restore prior versions. By default, Application Versioning is set to (OFF). To learn more about App Versioning, view our Introduction to Application Versioning article.
Style	Select a style that {{glossary.end-users}} see in {{glossary.Express View}}. No selection defaults to the default style specified in Style Administration. To learn more about creating styles and selecting a default style for your environment, view our Style Administration article.
Header Module	Select a custom header module to display in Express View. To learn more about header modules, view our Header Module article.
Footer Module	Select a custom footer module to display in Express View. To learn more about header modules, view our Footer Module article.
Login Module	Select a custom login module to display in Express View. To learn more about header modules, view our Login Module article.
Logout Module	Select a custom logout module to display in Express View. To learn more about header modules, view our Logout Module article.

Viewing an Application

After creating your application, open it to begin building. Inside each application, a list of all modules and workflows is displayed, based on the application type. After opening an application, you can search for or filter by a module or workflow, sort the list, and view any of the modules and workflows stored in the application.

To view an application in a workspace:

Inside your workspace, locate the application you want to view.
From the Actions column, select View Application. Your application opens in the same tab.

Promoting an Application

Unqork designs environments to support each phase of the SDLC (software development life cycle). When you’ve decided it's time to promote your application to the next stage of development, you need to promote the application from its current environment level to the next one. Unqork refers to the next environment level where you'll promote your application as the target environment level.

To promote an application from its current environment level to the next, ensure you've selected all the dependent elements that make up the application. These elements might include modules, styles, assets, Data Collections, and so on.

Modules can belong to more than one application.

After you’ve determined the necessary elements for the application, select the target environment level where you want to promote the application.

To learn more about promoting applications at the Application level, view our Promoting Applications article.

Promoting App Elements to Another Environment

In addition to promoting entire applications from one environment to another, the Unqork Designer Platform enables you to promote individual modules from one environment to another. Promoting modules can be helpful if you want to promote a specific module that exists outside of the context of an application.

To promote a module that is dependent on an entry point module, the entry point module must be promoted with it or before or it. If the entry point module is not promoted as well, the promotion fails.

To learn more about promoting app elements, view our Release Management Dashboard Tool article.

Resources

Unqork provides you with the ability to create web applications. In general, a web application is a type of software that uses web browsers to perform tasks. In Unqork, an application is a program that performs the same tasks using web browsers. An Unqork application can be either a module-type or workflow-type application.

Module-Type Applications

To create a module-type application, you must define an entrypoint module. The entrypoint module determines the point of entry into the application. Therefore, the application ID and the entrypoint module ID are consistent.

What Is an Entrypoint?

During the planning process of building an application, it’s important to consider how your end-user interacts with the application. Specifically, how and where your end-user accesses and interacts with your application.

Once you determine the entrypoint, it’s important to consider the application's data model. Does the application create submissions? Should end-users be allowed to update submissions? These are important questions that help you decide permissions for an end-user interacting with submission data.

When creating and updating Unqork submissions as a non-Administrator Express role, saved Property IDs must be present as a component in the module or application where the submission is written. When writing to Unqork submission data, Super-Users (Administrators with Full Submission Access) behave differently from non-Administrators. The Super-User role superseding all RBAC controls for writing Property IDs to Unqork submissions. Therefore, Super-Users can write Property IDs to a module even if the Property ID doesn't exist on the module.

By default, Data Versioning is enabled for every application. That way, Unqork can store any submission revisions that belong to the application. The option to enable WORM (Write Once Read Many) storage is only visible when Data Versioning is set to ON. If you decide that you don’t want end-users to edit, overwrite, or delete any submission data, then you must enable WORM storage. By default, WORM storage is disabled in your application.

To learn more about WORM storage, see our Navigating Workspaces article.

WORM storage is only compatible if the entrypoint is a schema module that stores submissions.

Workflow-Type Applications

A workflow-type application is a separate entity from a module-type application. But workflow-type applications can contain modules linked together to execute a process.

Working With Multiple Applications

Sometimes it might be necessary to create multiple applications. While we’ve defined the two types of applications in Unqork, many times the term application is an umbrella term to describe an application consisting of multiple applications. For example, let’s say you're creating a meal-delivery application where customers submit a meal order. Then, a driver picks up the meal from a hub and delivers it to the customer. This application might consist of multiple applications designed to execute the following functions:

Customers use one application to create the order and submit it to the hub.
Drivers use another application to create a profile and select a delivery shift.
The application assigns routes to drivers based on their availability.

Each application in the above example might also have its own respective schemas (orders, drivers, shifts, and routes) defined by a data model. This data model's overall goal is to deliver meals to customers. That way, each application contributes to your overall meal-delivery application.

Creating an Application

To create an Unqork application, you must have a workspace to store it. Once you have a workspace, you can create one or more module-type or workflow-type applications inside it.

Navigate to the workspace where you want to create an application. At the top right of your open workspace, click + Create App. A {{glossary.modal - LC}} displays with two tabs for customizing your application. After completing the configuration of your application, click Create.

If you create an application from your homepage, you are required to assign it to a workspace.

App Info

The App Details tab is where you set up the basic application configuration. This tab lets you assign an application name, select an application type, define the application's entry point, and so on.

Setting	Description
App Name*	Enter a unique application name. It's best practice to choose a name that helps you and your team identify the function of the application. Entering a name for your application populates the App Path field in a concise URL format. *The App Name field is required.
App Path*	The URL-friendly format of your application's name. This field can be modified or left with the default path. *The App Path field is required.
Style	Select a style that {{glossary.end-users}} see in {{glossary.Express View}}. No selection defaults to the default style specified in Style Administration. To learn more about creating styles and selecting a default style for your environment, view our Style Administration article.
Header Module	Select a custom header module to display in Express View. To learn more about header modules, view our Header Module article.
Footer Module	Select a custom footer module to display in Express View. To learn more about header modules, view our Footer Module article.
Login Module	Select a custom login module to display in Express View. To learn more about header modules, view our Login Module article.
Logout Module	Select a custom logout module to display in Express View. To learn more about header modules, view our Logout Module article.
App Type*	Use this drop-down to set this application as a module-type or workflow-type application. Depending on your selection, a module or workflow is automatically created in the application. *You must select an App Type.
App Entrypoint*	Specify the module end-users are directed to when they access the application. Or, select New Entrypoint to set the module or workflow as the starting point. Once selected, you must define the entrypoint's module type. *You must assign an App Entrypoint.
Module Type*	Available for Module App Types. After selecting the Module App Type, you'll use this drop-down to select a Module Type of API, Front-End, or Other. To learn more about Module Types, view our What Is a Module? article. *You must select a Module Type.
App Description	Use this field to add a description of this application.

Data Settings

The Data Settings tab lets you control your application data by enabling data and application versioning, as well as style your application.

Option

Description

Data Versioning

Determines how long data persists in modules. When enabled, Unqork stores all submission revisions belonging to the application.

Disabling this setting hides the WORM Storage setting.

By default, Data Versioning is set to (ON).

If this setting is set to (OFF), Unqork does not create a revision for the application’s entrypoint module. But a revision is created for all other application modules, regardless of whether the setting is enabled.

WORM Storage

WORM data storage prevents the overwriting or deletion of records. Enabling this setting sends data revisions to a WORM-compliant storage. A slider prompts you to set the number of days data should persist in storage.

Enabling WORM Storage removes previous submissions and attachments.

By default, WORM Storage is set to (OFF).

Enable Application Versioning

Enables Creators to create copies of the application. When set to (ON), Creators can create a new version of the application at any time, retain historical versions for stability, and view and restore prior versions.

By default, Application Versioning is set to (OFF).

To learn more about App Versioning, view our Introduction to Application Versioning article.

Previewing Your Application

Once you create an application, you can preview it from your workspace and application page.

For more information on navigating an application, visit our Navigating an Application article.

To preview your application from the workspace page:

Open your workspace.
In the Applications tab, click the (ellipsis) on the application tile you want to preview. The application settings menu displays.
Select Preview to preview your application in {{glossary.Express View}}.

To preview your application from the application page:

These instructions assume you have already created an application in your workspace.

Open the application you want to preview.
Click Manage ▾.
Select Preview to preview your application in Express View.

You can also view an application preview in Express View using the following application URL path: https://www.{your-environment}unqork.io/app/{appPath}#/display/{moduleId}/{submissionId}/{moduleId}.

For example, an application named application-settings was created in the training environment. The moduleId of the application is 6517325819f7fec671368ff4 and has no submissionId. So, the Express View preview of this application uses the following URL: https://trainingx.unqork.io/app/application-settings#/display/6517325819f7fec671368ff4.

Styling Your Application

As with application configuration, styling your application occurs in the development process. The Unqork’s Styles team can style your environment using custom CSS (cascading style sheets). By default, your application has available styles that you can apply.

To learn more about creating and uploading your own styles, see our CSS Upload article.

To access environment styles:

At the top right of the top right of the Unqork Designer Platform, click Settings ▾.
Click Administration.
Under Environment, select Style Administration.
From the grid, find the style you want to use.
From the Manage ▾ drop-down, select Set As Default.

Use the Manage drop-down to edit style descriptions and promote the style from one environment to another.

Promoting Your Application to Another Environment

When you’ve decided it's time to advance your application to the next stage of development, you need to promote the application from its current environment to the next environment, or target environment. Unqork designs environments to support each phase of the SDLC (software development life cycle). Promotion is the process of advancing your application between environments. To promote an application from its current environment to the next, ensure you've selected all the dependent elements that make up the application. These elements might include modules, styles, assets, data collections, and so on. After you’ve determined the necessary elements for the application, select the target environment where you want to promote the application.

Keep in mind, modules can belong to more than one application.

Promoting Your Module to Another Environment

In addition to promoting entire applications from one environment to another, the Unqork Designer Platform enables you to promote individual modules from one environment to another. Promoting modules can be helpful if you want to promote a specific module that exists outside of the context of an application.

To promote a module that is dependent on an entry point module, the entry point module must be promoted with it or before or it. If the entry point module is not promoted as well, the promotion fails.

To learn more about promoting applications and modules, see our Release Management Dashboard Tool article.

Resources

Best Practices: Configurations

Building Accessible Applications in Unqork

Component Configuration Best Practices

Node Configuration Best Practices