Overview
This page has information about plugins, how to manage the installed ones and how to create new onesPlugins are encapsulated solution components that can include displays, scripts, symbols, templates, and more. They can either be imported as a read-only, allowing for easy removal and update of plugins or as a merge, fully integrating the plugin into the solution and allowing the user to edit all components that come with the plugin. To know more about exporting/creating plugins, click here.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Importing a Plugin
In Solution
Working with Plug-Ins
What are the project plug-ins?
Content
How to import a plug-in?
On Project Settings → Import Plugin, you find all the information required to import a component into your projectsolution. Once you have an exported item from any other projectsolution, you will be able to import it in your own projectsolution.
On the top of the display, you will find these buttons:
Import plugins options | |
Add and merge to the solution | Fully merges the plugin into the solution, allowing the user to edit the plugin’s components directly in the Solution Designer. |
Add as read-only | Imports the plugin in an encapsulated manner. Ensures the possibility to safely remove or update them later. |
Plugin search options |
This button allows editing of the pre-created component, but it will not be possible if the “Contents Hidden” option was used to create it.
In the grid below these buttons, you will find all the components already exported and some information about themShow plugins from local folder | Directly |
search the directory for any pre-built components available on your computer. |
Show components from Cloud |
This list can contain any pre-created component available in your computer or in the Cloud.
| Note | ||
|---|---|---|
| ||
If the component has been exported using the “Force as Plugin” option, the “Add as component” option (embedded in the project) will not be able to be selected. |
Select if the component will be an embedded component.
Shows the solution components available on the Cloud. |
Plugins info | |
|---|---|
Name | The designated title assigned to the plugin. |
Preview | A preview image that represents the |
plugin. |
Source |
Installed Plugins
On Run → Extensions → Installed PlugIns,you find information about the pre-installed plugins in the project.On the top of the display, you will find four buttons:
Remove the plugin and dependencies from the project.
If the plugin has not been created with the option "Force as Plugin" enabled, so you can convert the plugin into a component and merge it into your project.
In the grid below these buttons, you will find all the components already exported and some information about them.
Component information
Creating a New Plugin
Creating a new component or plugin is a very interesting feature if you have different projects that require similar structures/functionalities. The first step in this process is to create a new project that only contains the elements required to fulfill the desired purpose.
Once you have the project working, go to Project Settings → Export. On the top of the display, you will find five buttons:
Uncheck all the pre-selected items on the grid. You can use both the SHIFT and CTRL keys to select one or more items. The unchecked items will not be exported at the end of the process. You can manually uncheck them. Then, go to the “Export” column and edit it.
This button opens the “Make new component” display, where you can configure the properties of the component.
Save as Text File
Export the components as a XML file while keeping the structure and information about the component.
When exporting tags also export
The tags created on the project can be used in many different configurations on the system; such as Alarms, Historian, and Devices. To include these configurations when you export a tag, you have three checkboxes:
Alarm Items: Include the pre-configured alarm items for the specified tag.
Tag Historian: Include the pre-configured tag historian information for the specified tag.
Device Points: Include the pre-configured device points for the specified tag.
Auto Check Dependencies
When you use the checkbox “Auto Check Dependencies”, whenever an object is checked, any secondary dependency on this object like tags, templates, images, will be checked too.
Specifies where the plugin is stored, either locally or on cloud-based storage. | |
Date modified | The most recent date when changes were made to the plugin. |
Version | The current release number of the plugin indicating its development stage or iteration. |
Product version | Specifies the version of the product on which the plugin was based. |
ReadOnly | This attribute indicates whether the plugin's settings or configurations can be altered. |
Description | A concise textual overview detailing the functionality or purpose of the plugin. |
In this section:
Under this display you have:
Hides the contents of the component; this means that this component cannot be edited once its imported to a new project.
A preview image that represents the new component.
The version of the new component (e.g.: 0).
Description of the component being created.
| Page Tree | ||||
|---|---|---|---|---|
|