ThingWorx Ideas

1. What version of Thingworx are you currently running? 9.0.8 2. Describe the problem you are trying to solve: I can't be sure when reading values in a VStream that the quality of the tag was GOOD, BAD or UNKNOWN when the property was logged. It would be nice to have this info logged with times and values. Otherwise, just the ability to skip bad/unknown quality values when choosing to log the property would be enough. 3. What business value would your suggestion represent for your organization? I should used a workaround with Streams and I think this is not optimized as I should find the right trigger of the log and check the tag quality foreach property I want to log. Performance issues could appear with a large amount of tags I need to log. ... View more

ThingWorx Azure IoT Connector relies on the connection string to connect to the associated storage account. We would like to create a feature request to have the Connector authenticate to the storage account using an identity rather than the connection string. ... View more

Flow services have a hardcoded limit of 64 KB. It is sometimes necessary to create much longer, more complex JavaScript services. This limit should be configurable. ... View more

Today (Thingworx 9.1) an infotable property is only generating a data change event if the number of rows in the infotable changes. It should generate a data change event if any field in any row changes.    The use case is that when building SCO applications, many machine suppliers supply info via OPC UA Arrays and they become infotables in Thingworx. Then you need to be ablity to process event based business logic when any value in the table updates.    In a current project, the alarms from one machine comes via an three boolean OPC UA Arrays. They are 400, 400 and 50 in length. The only way they can be handled today is to either adress them as individual properties (if the machine supplier can supply that via OPC UA) or to fire events Always, which means that the check through the whole array for new alarms have to be executed every second.     If we could fire an event when a field in the infotable changes with the old and new values, it is a simple script to loop it and set/reset alerts based on the change. And it will be easier to both develop and maintain. And overall performance of the platform would probably be better.      ... View more

When tags are generated using the OPC-UA Client driver in Kepware they are created with Client-Access "Read/Write" as default. There should be an Option on either the device or channel in Kepware to change this default behavior to Read only. (The workaround currently is to utilize the export/import CSV function to change the the tag property to Read Only before importing the CSV file )   The reason is that in the normal ThingWorx monitoring scenario with Kepware, e.g. monitor a temperature value: It is dangerous to forget to change this configuration to "read-only" after importing tags.   This is quite easy to miss. Missing means that values in the PLC can be changed from the ThingWorx platform (depending on configuration). This can be extremely dangerous both from a process and/or safety perspective. ... View more

As per the nature of ThingWorx, a Thing Hierarchy is set up using Thing Templates and Thing Shapes in order to model our devices/machines in the real world. Thing entities are created off of these Thing Templates/Shapes and inherits all the properties/events/services/subscriptions from its parents. Kepware allows us to easily retrieve information from the machines and send it to ThingWorx via the Industrial Gateway to map to our machine Thing entities. But when the inherited properties are bound to the Kepware tags from the Industrial Gateway, ThingWorx considers these newly bound properties as "overridden", therefore any changes to the property from the Thing Shape level may or may not apply.   If the property is set to "Fetch from remote every read",  this will causes an overflow of errors in the logs because all of those connected things that inherit the remotely bound property (that remains on the shape level) are trying to fetch but there is no connected corresponding Kepware property.    Thing Shapes/Thing Template should be able to work with Kepware in order to support both the ease of connectivity that Kepware brings and the inheritance model that ThingWorx is known for.  ... View more

When a SCADA/Device has enormous amount of tags/nodes exposed under one parent Node in OPC-UA, its hard to find the right child node. There is no filter to filter out nodes using the Tag Generation feature on the OPC UA Client driver. AS-IS it can only filter out Leaf tags.    This makes it enormous time-consuming to navigate in the OPC-UA server when there is a flat node structure. E.g. try to find a node with a specific name in a unsorted list of 1000 nodes by browsing.   Proposal: Enhance the Leaf filter for the OPC UA Client driver under Tag generation with a node filter that makes it possible to filter any level in the tree structure exposed by the OPC-UA server.  ... View more

The Retain feature is a part of the Mqtt protocol and is very useful in a asynchronous world where assets can be up/down, connections can be broken etc,,, ... View more

Our company is beginning to use Thingworx to pull data from Windchill and a standalone database. One feature that we would like to implement is the ability to read the relationships between WTUsers and WTGroups. An example follows: 1. Thingworx displays a list of WTGroups from Windchill and the user picks a group from the list. 2. After the user picks a group, a new service fires which queries the users in that group and provides the user with a new list to choose someone from the group.   Unfortunately the relationships between WTGroups and WTUsers are stored in WindchillDS and not in the Windchill database. This means that we are unable to gather this information because Thingworx does not currently support reading data from an LDAP. ... View more

Thingworx should provide the ability to turn off and turn on Azure IoT Hub Connector directly from the platform. For Example, during maintenance or deploy activities It could be useful to shutdown the IoT Hub Connector to avoid data loss.   Users do not always have the ability to access the server where the connector is installed.    ... View more

It is known that ThingWorx's role as Service provider can fetch data from Resource provider-Windchill after an SSO authorization process as documented in  "PTC_Single_Sign_on_Architecture_and_Configuration_Overview_Guide_172779". It would be helpful in some use cases if ThingWorx could act as a Resource provider to some third party services like Alexa / IFTTT.   ... View more

Hi Team,   Lot of times, TWX platform shuts down due to license expiration without any warnings.   Only when i check the Application log files from repository i come to know that this is due to License expiration.   Is there any Notification mechanism available as a default which could notify the user or at least the administrator ( through mail or status display on the platform) regarding the possible expiration of license in a month or day?   This will save some time in debugging.   Regards, Saran ... View more

If you specify a server name for KW to use to connect to TW it often gets resolved with an IPv6 address... and the connection fails (until you give KW an IPv4 address for TW). This means we can't use IPv6 or FQDNs/DNS. It also makes certificate validation slightly dubious. ... View more

There are some PTC-supported Extensions, like MQTT, that have new releases from time to time. At this moment in time, the ThingWorx platform Help Center, does not contain release notes for those extensions, but it does contain Release Notes for the Platform itself. We need to have a section somewhere, either in the PTC ThingWorx Platform Help Center, or somewhere else, where we document the release notes for those extensions. ... View more

Enable the content type/headers to be set for each part within a post multipart request. These are currently fixed/hardcoded which is limiting. When sending REST requests to external APIs, they may expect certain content types and request requests that do not conform. ... View more

Hi ,   I am trying to call rest api which is using request as "x-www-form-urlencoded", I am using thingworx PostText Service but everytime getting Below error whereas I have passed username and password. result {"error":"Argument \u0022username\u0022 is required."}   Below is the code : I have made username,password, and url hidden in below code var params = { proxyScheme: undefined /* STRING */, headers: undefined /* JSON */, ignoreSSLErrors: false /* BOOLEAN */, useNTLM: undefined /* BOOLEAN */, workstation: undefined /* STRING */, useProxy: undefined /* BOOLEAN */, withCookies: undefined /* BOOLEAN */, proxyHost: undefined /* STRING */, url: "https://" /* STRING */, content: "" /* STRING */, timeout: undefined /* NUMBER */, proxyPort: undefined /* INTEGER */, password: "abc" /* STRING */, domain: undefined /* STRING */, contentType: "application/x-www-form-urlencoded" /* STRING */, username: "xyz" /* STRING */ }; // result: STRING var result = Resources["ContentLoaderFunctions"].PostText(params);   Output: result {"error":"Argument \u0022username\u0022 is required."}     Any kind of help would be highly helpful for me. Waiting for your response. Thanks In Advance. ... View more

I would like some more Services in the IndustriaGateway-Template. e.g: The complete access to the Tags of KepServer is only possible by binding those to THingProperties. Would be great to have some additional Services to read/write KepServerTags by Service ...    ... View more