Using the Launch Point Configuration Thing

Customizing Information Content > Using the Launch Point Configuration Thing

The launch point configuration thing (PTC.Factory.C_LaunchPointConfigurationThing_[ReleaseVersion]) provides a central point for many configuration and customization actions in the current release.

The Configuration page of the launch point configuration thing includes the following:

• ManagerConfigurationSettings—The managers configured for specific functional areas.

• DatabaseConfigurationSettings—The database thing configured for the database associated with ThingWorx Apps. This value is specified during the initial ThingWorx Apps installation and configuration process.

• LaunchPointEntitySettings—Configuration fields specifying the mashups launched for specific areas of the ThingWorx Apps user interface, the data table for the tiles displayed in the ThingWorx Apps console, and any custom alert notification handler.

• EquipmentTypeSettings—Configuration table where equipment types are defined.

• EquipmentContextSettings—Configuration table where contexts are managed.

• EquipmentUserInterfaceSettings—Configuration table where the mashups and menus used for equipment types are defined.

• RemoteConnectionSettings—Configuration table where settings for remote connections are managed. Remote connection settings are added or edited when:

◦ Including New Server Types or Custom Connectors in Controls Advisor

◦ Customizing the Tag Picker Common Component

◦ Displaying Azure IoT Hub Data as Property Values on an Asset

◦ Customizing the Calculation of Remote Server Status

• EquipmentStructureConfigurationSettings—Determines the default behavior for the display of assets in structure tree filters:

◦ DisplayAssetsInStructureTree—When this checkbox is cleared (the default), assets are not displayed in the structure filter on the Asset Advisor asset list page.

◦ DisplayAssetsInAlertMonitoringStructureTree—When this checkbox is selected (the default), assets are displayed in the structure filter on Alert Monitoring.

• AlertCustomizableSettings—Allows configuration of the default for the TagCountAboveLimit alert automatically created when a KEPServerEX server is connected for the first time.

For information on comparing your release-specific launch point configuration thing settings with the defaults, see Comparing Your Customizations with the Default.

Was this helpful?