Page History

Overview

A Solution

is a complete application built

in FrameworX, stored as a single .dbsln file

containing all configuration data including tags, alarms,

devices,

displays, scripts, and

other modules. Creating a new solution

generates this file with initial metadata

, which you then configure using Designer.

Creating a New Solution

To create a

solution

, click

New...

in Solution Center to launch the New Solution Wizard.

Step 1

: Product Features

Select the product family and

The software platform technology powers four product options:

model for your solution:

Note: Configuration tools are free. Production deployment requires appropriate license matching your selected model.

Step 2: Platform Selection

Step 3: Name and Template

1. Enter solution name
2. Review save location (default: Documents\FrameworX\Solutions)
3. Select template (optional - defaults to HeaderLayout)
4. Click Create New Solution

Solution Templates

Templates provide preconfigured components and settings for faster development.

Built-in Templates

Adding Custom Templates

Templates are standard .dbsln files stored in:

Documents\FrameworX\Templates\

To add templates:

1. Copy .dbsln file to Templates folder
2. File appears in wizard on next use
3. Modify existing templates by editing files in folder

Creating Templates

1. Build solution with desired configuration
2. Save .dbsln to Templates folder
3. Optionally include:
   • Pre-configured tags and templates
   • Standard displays
   • Common scripts
   • Device configurations

Solution Configuration

After creation, solutions contain:

Solution Files

File Structure

File Locations

Solution Creator Tool

For bulk solution creation (e.g., deploying to multiple edge devices), use the Solution Creator utility.

Use Cases

• Mass deployment to edge devices
• Creating variations from configuration files
• Automated solution generation

See Solution Creator (Reference) for details.

Best Practices

Naming Conventions

• Use descriptive names without special characters
• Include version or site identifier
• Avoid spaces (use underscores)

Template Selection

• Start with appropriate template
• Customize rather than starting blank
• Save customized versions as new templates

Platform Choice

• Choose Windows only if Windows-specific features needed
• Use Multi-Platform for future flexibility
• Consider deployment environment early

Troubleshooting

See Also

• Solution Settings (Reference) - Modify solution properties
• Solution Creator (Reference) - Bulk solution creation
• Designer (Reference) - Solution configuration
• Product Series (Reference) - Licensing models

In this section...

For details about product families and licensing models, see the Product Series page.

Wizard Step 2 - Platform

Wizard Step 3 - Solution Name and template

Define the name and review the location for saving your solution file, select a solution template and press the Create New Solution button.

If you don’t select a template, the default HeaderLayout template will be applied automatically.

Solution templates help you start faster by providing preconfigured components, settings, and modules. These templates can be customized to suit your specific application needs.

Examples of templates include starter layouts for web-based, desktop, or mobile solutions. Some templates are included with the software, and you can also create or import your own.

Adding New Templates

The templates available when creating a new solution are standard solution files located in the user's Documents folder under Templates.

To use a template received from a vendor or integrator, simply copy the .dbsln file into the Templates folder located in your Documents directory. You can also customize existing templates by opening and modifying the solution files in that folder.

Solution Creator Tool

When you need to create multiple solutions—such as deploying hundreds of edge devices based on configuration files—the platform provides a utility to automate and streamline this process.

For details, see the Solution Creator (Reference) page.

In this section: