Creating Solutions Reference

Start new solutions with the Solution Creator.

Reference → Solution →  Solution Center → Creating | Managing | Server | Licensing | Upgrading

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 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\ProView DS\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\ProView DS\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 Checklist

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