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

Advanced Grid Widget needs cell click event / binding

Advanced Grid Widget needs cell click event / binding

Currently when a user clicks a row on a table its possible to use "selected rows changed" event with "selected rows" binding to open a popup with the values from the selected row.

 

However, a common use case is needing to open a popup with the value of the clicked cell (including which column & row was clicked).

 

This is possible with the collection widget but seems overkill for a simple functionality that's needed very frequently. Also the collection widget is not as performant as the advanced grid widget.

 

 

Advanced grid - current state:

- Know which row was clicked

- Know the values of the row that was clicked

 

Advanced grid - desired state:

- Know which cell was clicked

- Know the value of the cell that was clicked

6 Comments
cbaldwin
13-Aquamarine
Status changed to: Implementation In Progress

A new Grid widget is being developed in 2020.

Ichiro_1486
3-Visitor

Hi,

 

We are Hitachi High-Tech Solutions Corporation.

This time, a user requested to add the function of ThingWorx system.

 

The function they'd like to add is to specify a TCP/IP listener port number

as of connecting from the ThingWorx server that they manage to the "remote thing".

and the specified number needs different from actually communicating port number.

 

The present, the user has placed  a "remote access" widget in a Mashup and connected using Java.

this method allows being specified a listener port number.

And the future, they'd like to completely migrate to RAC without using Java;

place a "Remote Access Client Linker" widget in the Mashup and connect using RAC.

 

Can you add listener port function into Remote Access Client Linker widget?

Please kindly consider this matter.

We are looking forward to hearing from you soonest.

 

Best regard,

 

Ichiro Ishihara,

Hitachi High-Tech Solutions Corporation

a.p.moffa
5-Regular Member

Ichiro,

 

Thank you for your input.  I would like to clarify something:  ThingWorx offers two different types of Remote Access and Control frameworks - one is based on the native ThingWorx Edge and the second is based off the Axeda agent.  We'd like to understand which version of RAC you are using?

 

While we are on the topic of Remote Service, our long-term roadmap has us extending the Axeda style RAC capabilities to the ThingWorx Edge - this includes the addition of the Global Access Server (GAS) network for ThingWorx Edge based devices.  This requires an update to the C and .net SDK's and the addition of a Remote Access Edge Extension, all of this work is targeted to be delivered this calendar year (2021).

 

Axeda defines the remote session capabilities via the agent/edge – and that includes the port number to be used at the edge.  But we need to remember, the port being used at the edge is important to the edge device and the application running at the edge but it is irrelevant to the port we set at the service technician's computer - that is just part of the physical tunnel and does not define the session capabilities   We do understand that it may be desirable to set ports on the diagnostic PC so that they "align" with the traditional ports used for the function.  To achieve that, we will be releasing an IP and Port configuration feature in RAC in the Spring 2021 release of ThingWorx.  So for example, if you require that an SSH remote session must be on port 22 all the time, you can define the port as 22.  If you need to open multiple sessions from the same PC, you will need a unique IP and Port combination, but since you fixed the port we will cycle IP addresses (127.0.0.1 … 127.0.0.255) for each parallel tunnel created.  Functionally, SSH session 1 would be 127.0.0.1:22, session 2 - 127.0.0.2:22 and so on.  Likewise we can fix the IP (aways 127.0.0.1) and then alter the port number. In addition, we also let you define ranges for those cycles (i.e. Ports could be set to 17,000 to 17,010 or IP can be set to 127.0.0.10 to 127.0.0.15).  It's a very flexible environment.

 

Regards,

Anthony Moffa

ThingWorx Product Management 

 

Ichiro_1486
3-Visitor

Dear Mr. Anthony Moffa,

 

Thank you for the information.
I’m sorry for the delayed response because I’m NOT familiar with “ThingWorx Ideas” System.

First, this is about ThinsWorx’s RAC.

I appreciate for considering enhancement of RAC function.
I’ll inform our customer of the information as informal news.
We are looking forward to releasing ThingWorx version implemented new function.

 

Sincerely,

 

Ichiro Ishihara,
Hitachi High-Tech Solutions Corporation

 

cbaldwin
13-Aquamarine
Status changed to: Under Consideration

 

@aashwait ,

 

Do you only want to keep track of the last cell the user clicked on, or support multiple cell selections?

 

Chris

 

olivierlp
Community Manager
Status changed to: Under Consideration

Will consider for future release and new grid web component.