Libraries

Libraries contain object definitions or templates to add to your projects. For example, libraries contain graphic elements such as values and tanks to use in your project. Library templates also exist for miscellaneous objects, pre-defined code called scripts, style sheets or themes, and widgets to interact with at runtime.
You can configure both local and remote libraries to store objects and variables in Git repository. Add components from
Libraries
to
Project view
. Push and pull libraries to see the latest changes users make to remote libraries as you would remote projects. Create a template to create objects, object types, and variables that have similar attributes.
Libraries
have pre-configured widgets with which to interact and configure the device at runtime. 

Library types

Type
Description
Template library
The default library of objects that you cannot edit or remove. Template libraries are provided for:
  • GraphicElements
    Illustrations of objects that you can include in the runtime application display to provide additional context, such as a light-emitting diode (LED), a butterfly valve, and reactor tanks.
  • Miscellaneous objects
    Components that perform operations within the runtime application, such as loggers, alarms, and converters.
  • Scripts
    Pre-defined code that performs functions within the runtime application, such as notifications, counters, and data transfer.
  • StyleSheets
    Pre-defined theme that defines the look and feel of the pages of your runtime application, such as a light them, a dark theme, and a material-design inspired theme.
  • Widgets
    Objects that the user can interact with in the runtime application, such as a login form, an alarm grid, and a color picker.
Custom library
A library created by a user that contains a set of objects either curated from the template libraries or customized for specific automation scenarios.
TIP: To find a template quickly, select any item under
Components
and start typing.

Library repositories

You can store libraries locally or in a remote Git repository. Libraries are available across
FactoryTalk Optix
projects.
Libraries are saved in the
C:\Users\
UserName
\Documents\Rockwell Automation\FactoryTalk Optix\Libraries
folder.

Library updates

Libraries and library objects are tied to the version of the
FactoryTalk Optix
software with which they were originally configured. When you install an updated version,
FactoryTalk Optix
updates the built-in template libraries to make the libraries compatible with the new software.
If your project contains custom libraries that use components that changed in the updated version of
FactoryTalk Optix
, you must manually update the custom libraries.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.