| HTML |
|---|
<style>
.text-span-6 {
background-image: linear-gradient(99deg, rgba(170, 163, 239, .5), rgba(125, 203, 207, .5));
border-radius: 50px;
padding-left: 15px;
padding-right: 15px;
}
#title-text {
display: none;
}
.panelgradient {
background-image: linear-gradient(180deg, #d5def0, whitesmoke);
border-radius: 8px;
flex-direction: column;
justify-content: center;
align-items: center;
padding: 4rem;
display: flex;
position: relative;
}
</style>
<div class ="panelgradient">
<h1 style="text-align: center;">Solution <br>Settings>Solution<br>Settings and Tools</h1>
</div> |
Introduction to Solution Settings and Tools
The Solution section in the Designer workspace gathers detailed information about solutions, offering rich metadata and various tools to aid in designing and individually managing solutions on the software platform. It includes Solution Settings for configuration, Solution Categories for organization, Import Tags and Import Plugins for accelerate solutions creating, Export for sharing configurations, and History for tracking keys actions on the solution configuration.
On this page:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
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 Requirement for to run the Solution in Production. Even the Designer is unlimited, you should always setup those fields properly, so the Designer will limit its functionality consistent with the License required for field deployment.
Categories
Metadata labels that be used across all configuration tables, assisting to organize large size application.
Plugins
Excerpts of a Solution, it can holds Tags, Displays, or any other objects. Useful to create reusable components and enforce development standards.
Understanding The Solution Section Usage
The solution section 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 covers from CSV files to ControlLogix devices, and various other options.
Finally, if you have PlugIns created by your own team, or received from integrators, they can be added to speed up the solution development.
The Plugins are created with the Solution Export user Interface.
When you do any of those action, the Solution History tracks that 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
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|