Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X

ThingWorx Glossary A - T

No ratings
Here's a short list of vocabulary terms used throughout the ThingWorx documentation.



alertA declarative way to create an event in ThingWorx that is triggered when a defined value or limit is reached or exceeded. All properties in a Thing shape, Thing template, or Thing can have one or more alert conditions defined. Alert types are specific to the data type of the property; the following base types can be used for alerts: Boolean, Datetime, Infotable, Integer, Location, Number, and String.
alert historyA comprehensive table that records all information when an alert is triggered. The data is stored until it is removed manually.
alert processing subsystemSubsystem that manages the alert history stream. See Subsystem.
alert summaryCompiles data from the last reset of the server to the current state. You can view, acknowledge, and sort (by acknowledged or unacknowledged) alerts on the Alert Summary page.
AlwaysOnProprietary binary protocol for communication between edge devices and the ThingWorx Platform.
application keySecurity tokens used for authentication in ThingWorx when not using a standard credentials method of authentication. They are associated with a given user and have all of the permissions granted to the user with which they are associated. Application Keys are typically used to assign permission control to remotely-connected edge-devices. Application keys are also known as: appKeys.
application logA collection of all of the messages that the ThingWorx application generates while operating. Based on your settings (such as WARN and DEBUG), this log can display system messages.
authenticatorAn entity that allows you to implement user authentication, such as single sign-on or certificates, outside of ThingWorx.



base typeType of data such as DATETIME, HYPERLINK, INFOTABLE, and NUMBER.
bindingIn order for your application to display data collected from your devices, you need to bind a Widget to a Data Source. See mashup binding.
blogA type of Widget that mimics the functionality of a 'web log' to provide online journal functionality. Posts may be made both by users and the ThingWorx Platform.



ClientConfiguratorA class common to all of the object-oriented Edge SDKs that handles configuration (URI, port, support for proxying, tunneling, file transfer, etc.) of the ConnectedThingClient. It is used by the edge device to control its behavior and connect to the ThingWorx Platform.
communication logA record of all communication activity with the ThingWorx platform. These communications can be between the following:a connection server and the platform, WebSocket devices and a Connection Server, WebSocket devices and the platform.
ComposerModeling and design environment in ThingWorx where you create the back-end of your IoT application. ThingWorx Composer runs as an HTML5 web application.
Composer logRecords all activity performed in the Composer and its interaction with the platform layer.
configuration logContains all of the messages that the ThingWorx application generates for create, modify, and delete functions in the ThingWorx Platform. For example, if a Thing or Mashup is created, modified, or deleted, that information is recorded.
ConnectedThingClientA class common to all of the object-oriented Edge SDKs that handles communication between Edge and the ThingWorx Platform.
connection serverA server application that allows the connection of remote devices and handles all message routing to and from the devices.



dashboardA dynamic Mashup constructed from a grouping of Gadgets. A Dashboard may be modified during runtime so that certain Gadgets are displayed, while others are hidden.
dataRow entries in data tables, streams, value streams, blogs, wikis, and properties.
data shapeA type of ThingWorx entity made up of field definitions and related metadata that represents the data in your model. Each field in a data shape has a data type. ThingWorx has a defined set of base types, including: Boolean, Datetime, Hyperlink, Image, Infotable, Integer, Number, and String.
data tableA storage table that has a primary key and optional indexed fields; similar to a standard relational database table. A data table has the following predefined fields: Timestamp, Tag, Source, SourceType, and Location. A Data Table can be connected to external databases in order to import/export records.
data tagMechanism to label data to assist in grouping, filtering, and finding it. A ThingWorx tag is defined by the combination of a ThingWorx vocabulary and a specific vocabulary term; shown as Vocabulary:VocabularyTerm. Tags can be used to create a relationship between many different ThingWorx entities.
directory services authenticationA system, such as an LDAP service, that provides the ability to securely login through other applications outside of the ThingWorx Platform.



Edge MicroServer (EMS)Allows edge devices or data stores to connect to the ThingWorx Core through either the Internet or a firewall using the AlwaysOn™ binary protocol. See WebSocket-based Edge MicroServer (WS EMS).
entityHighest-level objects created and maintained in ThingWorx. For example, Things, Thing Shapes, and Thing Templates.
eventRepresents a change in state or value of a property. Interrupts the ThingWorx Core can subscribe to for purposes of receiving notifications when something happens.
event processing subsystemSubsystem that manages event processing for external subscriptions (Things subscribing to other Things) throughout ThingWorx. See Subsystem.
export import subsystemSubsystem that manages data export and import file sizes. In a system where many users have import/export permissions, these settings can help to alleviate importing/exporting large amounts of data at the same time. See Subsystem.
extensionA collection of entities, resources, and widgets used to extend the functionality of the ThingWorx Platform. This collection is packaged into a zip file, which can be uploaded to any ThingWorx Platform and used to serve a specific function.



federationA concept to enable sharing a large solution workload among ThingWorx servers by using local data Things (streams, value streams, data tables, wikis, or blogs) that publish to remote data Things (remote streams, remote value streams, remote data tables, remote wikis, or remote blogs).
federation subsystemSubsystem that manages the federation of Things among ThingWorx servers. See Subsystem.
field definitionDefines a field of a data shape. A field definition defines the base type, name of the field, and whether the field is a primary key.
file transfer subsystemSubsystem that maintains file transfer settings between remote Things, file repositories, and federated servers. See Subsystem.



gadgetReusable self-contained mashups that make up dashboards; can display historical or current data. Gadgets contain predefined parameters and additional metadata, which handles the sizing requirements of a dashboard.



infotableThe aggregate base type within ThingWorx. InfoTables have a DataShapeDefinition that describes the names, base types, and additional information about each field within the table.



localization tableProvides the ability to display run time labels in different languages or in userdefined terminology. You can configure localization tables with tokens, which can be assigned to the labels in the Mashup Builder. Each localization table in ThingWorx represents a different language.
logging subsystemSubsystem that manages various logs, such as Application, Script, and Communications. See Subsystem.
logsThe various monitoring tools that record the activity in your ThingWorx model. The available logs are the application log, communication log, Composer log, configuration log, security log, and script log.
Lua Script ResourceA utility that is used to run Lua scripts and implement remote Things at the edge device level.



mashupA graphical visualization of the model and data. Mashups have the ability to produce enriched results from the combination of presentation and data aggregation, making the application more useful and effective.
mashup bindingThe process of identifying the data source for widgets to display in the Mashup Builder.
mashup builderThe tool used to create and configure Mashups.
masterVisualization entity that provides consistent framing of a mashup's contents. A master is commonly used for items that display throughout the mashup, such as logos, menus, and titles.
mediaLocally-stored media artifacts necessary for your ThingWorx application implementation. In most cases, these include images and icons used for entities such as menus, style definitions, and mashups.
menuA hierarchical navigation structure consisting of links to mashups or URLs that is represented by a widget in a mashup.
message store subsystemSubsystem that processes outbound queued messages for various remote Things, including federated servers. See Subsystem.
model bindingThe process of attaching properties to entities in a model. There are two types of property bindings: local and remote. Services and events are remote only.
model tagMechanism to label ThingWorx entities to assist in grouping, filtering, and finding ThingWorx data and searching and discovering entities efficiently. A ThingWorx tag is defined by the combination of a ThingWorx vocabulary and a ThingWorx vocabulary term.
modelThe collection of ThingWorx entities created to represent your process, solution, and/or application.



networkDefines the relationships between Things and allows you to define a "Thing hierarchy" (parent, child).



organizationA hierarchical structure used to allow/deny visibility, access, and functionality to resources within ThingWorx. Users and User Groups are used to populate Organizations.



persistence providerA type of database which stores all collected ThingWorx information. The default database for ThingWorx is Neo4j. Other persistence providers can be created or configured within the platform. A configured instance of a persistence provider package can be utilized in run time data entities (streams, value streams, data tables, blogs, and wikis) to tailor the specifics of their persistence (such as location, run time characteristics, and tuning).
platform subsystem

Subsystem that provides overall Platform monitoring and configuration. See Subsystem.

ProjectUsed to logically group a collection of entities.
propertyRepresents a behavior of the actual Thing or process that you are modeling. Can also be thought of as a parameter or variable.



remote ThingA device or data source that is geographically separated from the ThingWorx Platform and is accessed over the network (Intranet/Internet/WAN/LAN). That device is represented as a remote Thing on the Platform.
resourcePlatform-provided services to aid in implementing your applications.
RESTAPIRepresentational state transfer (REST) application program interface (API). The ThingWorx API can be accessed at: host:port>/ Thingworx////characteristic>?.
run time dataData represented by streams, value streams, data tables, blogs, wikis, and properties.



script logContains all of the messages that the ThingWorx application generates while executing JavaScript services. You can use the logger.warn function to write information to the script log from the services you are running. Generally, ThingWorx will only publish errors to this log that are incurred while running a service.
securityGranular security model available within the ThingWorx Platform. There are two sets of permissions, one for design time and one for run time. The design time permissions are for managing who is allowed to modify the model (create, read, update, and delete entities), while the run time permissions determine who can access data, execute services, and trigger events on a Thing (which includes Data Tables, Streams, and Users). For each permission, you can explicitly permit a User or Group to be able to do something (like edit a Thing) or explicitly deny a Group the ability to do something (e.g. the Users Group is not allowed to edit a Thing). You can apply permissions at the Group level and at the User level. An explicit denial of a privilege always overrides a privilege grant.
SecurityClaimA class common to all of the object-oriented Edge SDKs used by a ClientConfigurator to store authentication information for a ConnectedThingClient.
security logContains all of the messages that the ThingWorx application generates regarding users. Depending on the log level, it can include login and page requests information.
serviceA function which a Thing can perform. A service can be defined at the Thing Shape, Thing Template, or Thing level.
state definitionA collection of style definitions that are applied using data-based rules in a mashup. Evaluating the data to specific ranges or values allows you to perform data-based formatting, such as changing the background color of cells in a grid widget.
streamA storage table that is optimized for time-series data. Writes to a stream are done asynchronously. Querying a Stream returns the entire record.
style definitionA collection of HTML styling elements that can be applied to a widget. All colors, text, and line formats are managed and rendered in the mashup environment using style definition entities.
subscriptionAn action that executes when an event occurs.
subsystemConfigurable ThingWorx Platform functionality that can be adjusted for specific Platform performance requirements. See Subsystem.
system userA default user in ThingWorx that manages internal service permissions but allows external API layer permissions to be set for each user.



tagUsed to label ThingWorx entities and data to assist with grouping, filtering, and locating ThingWorx entities and data. A ThingWorx tag is defined by the combination of a ThingWorx vocabulary and a ThingWorx vocabulary term. Vocabularies and vocabulary terms are customizable.
ThingThe digital representation of physical assets and/or processes that have properties and business logic. All ThingWorx Things are based on Thing Templates.
Thing ShapeAn abstract definition that represents the behavior of a concrete Thing or Things. Defines properties, services, events, and subscriptions for Things that implement the Thing shape. Typically, the Thing Shape is implemented by a Thing Template, which is then the basis of actual Things.
Thing TemplateProvides base functionality with properties, services, events, and subscriptions that Thing instances use in their execution. ThingWorx Things are derived from Thing Templates.
ThingWorx SDKSoftware development kit available in several languages, including C, Java, .NET, and iOS. The terms edge application or client application may be used when referring to a custom application built on an SDK. The term edge component may be used to describe a solution that includes multiple edge components (EMS, SDKs, ADO service, OPC service, etc.)
tunnel subsystemSubsystem that handles tunneling between remote Things. See Subsystem.



Click here for ThingWorx Glossary U - W

Version history
Last update:
‎Nov 16, 2022 02:43 PM
Updated by:
Labels (1)