Page History

Navigation Pages

Key Concepts

Target Platform

Defines the operating system and framework for the solution:

Product Family and Model

Licensing configuration for production deployment:

Categories

Metadata labels for organizing large-scale applications:

• Applied across all configuration tables
• Used for filtering and grouping
• Associated with default symbols

Plugins

Self-contained solution components:

• Reusable across solutions
• Include tags, displays, scripts
• Version controlled
• Update managed

Typical Workflow

Initial Setup

1. Verify Settings - Check Target Platform and Product Model
2. Define Categories - Create organizational structure
3. Import Tags - Bring in existing definitions
4. Add Plugins - Include reusable components

Development

1. Use Categories - Apply to new objects
2. Export Regularly - Create backups
3. Track History - Monitor changes
4. Update Plugins - Keep components current

Deployment

1. Validate Settings - Confirm production configuration
2. Export Solution - Create deployment package
3. Review History - Check recent changes

Module Navigation

Solution Explorer Location

Solution Explorer
??? Solution
    ??? Settings
    ??? Categories
    ??? Import Tags
    ??? Import Plugin
    ??? Export
    ??? History

Quick Access

• Direct navigation: Click module name
• Search: Type "Solution" in search box
• Recent: Check Recent Items on Welcome page

Common Tasks

Data Storage

Configuration Location

All Solution module settings stored in .dbsln file:

Temporary Folders

Solution-Data folder structure:

Solution-Data/
??? Designer/     # UI settings
??? Runtime/      # Execution cache
??? Git/          # Export files
??? Backup/       # Build backups

Integration Points

With Other Modules

External Systems

Best Practices

Settings Management

• Set Target Platform early
• Match Product Model to license
• Configure Python path if needed
• Set Culture Info for localization

Category Usage

• Define before creating objects
• Use consistent naming
• Apply to all object types
• Associate with symbols

Plugin Management

• Version control plugins
• Document plugin contents
• Test before updating
• Keep update history

Export Strategy

• Regular full backups
• Export before major changes
• Create plugins for standards
• Use Git integration

Troubleshooting

Common Issues

Validation

Child Pages

Configuration Pages:

• Solution Settings - Global configuration
• Solution Categories - Organization system
• Solution Import Tags - Tag import wizards
• Solution Import Plugin - Plugin integration
• Solution Export - Backup and plugin creation
• Solution History - Event tracking

Related Topics:

• Configuration Workflow - Best practices
• Temporary Data Folders - File structure

See Also

• Designer (Reference) - Main Designer documentation
• UNS Module (Reference) - Tag configuration
• Runtime Module (Reference) - Execution settings

Key Concepts and Terms

The Solutions section holds key global settings, such as Target Platform, and a set of tools to allow Import and Export configurations.

TargetPlatform

Defines the Operating Platform where the Solution is intended to run. It can be Windows Only (.NET Framework 4.8), or Multiplatform (Linux and any OS support .NET 8.)

Product Family and Model

Define the licensing requirements to run the solution in production. Even though the Designer is unlimited, you should always set up those fields properly so that the Designer will limit its functionality consistent with the license required for field deployment.

Categories

Metadata labels that can be used across all configuration tables, assisting in organizing large-scale applications.

Plugins

Subsets of a solution, which can holds Tags, Displays, or any other objects. Useful to creating reusable components and enforcing development standards. 

Understanding The Solution Module Usage

The Solution Module is typically used only when a new Solution is created. 

Usually, it is important to double check if the Target Platform, Product Family and Model, are correctly setup.  When using Python, its necessary also to locate property the path for the Python engine.

For large solutions, defining the Categories at the begging will prove useful to organize your configuration. 

If you have tag definitions available on other systems, you can bring them with the Tag Import Wizards, which support importing from CSV files, ControlLogix devices, and various other options.

Finally, if you have PlugIns created by your own team or received from integrators, they can be added in this section to speed up the solution development.

Plugins are created with the Solution Export user Interface. 

When you perform any of these actions, the Solution History tracks the event.

Configuring Solution Settings and Categories

Go to Solution Settings for animation on the settings available. 

Go to Solutions Categories to learn how to define and use Categories.

Working with Import and Export Tools

Go to Solution Import Tags on how Import Tag definitions from other systems. 

Go to Solution Import PlugIns on how Import PlugIns into the solution.

Go to Solutions Export on how to backup the solution, or create PlugIns

Using the Solution History 

Go to Solution History on how to track major Solution events, and update Plugins.

Temporary Data Folders

When editing and running the solution, temporary sub-folders are created under a Solutions-Data folder.

In most cases, it's not necessary to have any direct interaction with these folders, other than knowing they don't store solution configuration — only user UI settings and temporary files. Therefore, they can be deleted at any time if necessary.

In this section: