Skip to main content
Merged

Double click on record task enabled for multiple columns

Related products:Software FactoryUniversal GUIUI/UX
  • November 12, 2024
  • 9 replies
  • 100 views

For a while now, there is an option to activate a task via double click on a specific column. This however, only narrows it down to activating/starting the task when double click on one specific column. It would be very a nice feature to be able to select multiple columns to activate/start the task instead of just one. An example:

There are 3 columns in a table that are related to a specific Agent:

  • Agent name
  • Agent phone nr
  • Agent email

If I click on one of the 3 columns, the one task “Add agent info” will pop up. 

 

Is this possible to implement? Or better yet, is this already possible?

Did this topic help you find an answer to your question?

9 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3945 replies
  • November 15, 2024

Hi Vince,

You can indeed already achieve this using three None-logic tasks with process flow that have the actual task as follow-up action. 

Alternatively you could opt to include an Icon field in your grid with a sort-of Card image, that when double-clicked shows the Agent info.


Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
NewUnder review

Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • 1032 replies
  • December 18, 2024

@Vince D At the moment you have two options:

  1. Don’t select a Double click column: this will ensure the Task is executed when double clicking anywhere on the Grid record
  2. Do select a Double click column: this will ensure the Task is executed when double clicking on the configured Column in the Grid record.

I feel it would be confusing to offer even more variation there. Instead, it makes more sense to have a visual cue on the Grid that suggests clicking on it results in more information. In line with the alternative suggestion by ​@Mark Jongeling, we much more prefer to properly implement below Idea instead of your suggestion:
 

Is there some Use Case or argument I am missing, or can you agree with the current options combined with the implementation of showing Table tasks on Grid line?


Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • 1032 replies
  • December 18, 2024
Under reviewNeeds feedback

Forum|alt.badge.img
  • Author
  • Apprentice
  • 8 replies
  • December 18, 2024

Thank you all for your replies. Below my reaction on both comments:

 

@Mark Jongeling 

You can indeed already achieve this using three None-logic tasks with process flow that have the actual task as follow-up action. 

  • I don't think this could be achieved. since only one table task on the same table with the same task can be available

     

 

Alternatively you could opt to include an Icon field in your grid with a sort-of Card image, that when double-clicked shows the Agent info.

  • This seems to be a nice alternative which we could investigate. However, this would not be the preffered method, since our users want to see all data straightforward in the screen (reason: reachign out Agents fas by having info straight into their screen).

 

@Arie V 

  1. Don’t select a Double click column: this will ensure the Task is executed when double clicking anywhere on the Grid record
  2. Do select a Double click column: this will ensure the Task is executed when double clicking on the configured Column in the Grid record.
  • We are aware of this function, and we have already our ‘double_click_edit’-task on the whole grid record so this would not suffice. 
  • I do like the visual cue of table task of the grid line, since our users are then nudged to where they can fill in their Agent Details 

 

Therefore, I think we can live with the given options and am curious about the implementation of the grid line.  

 

Thanks 😁


Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3945 replies
  • December 18, 2024
Vince D wrote:
  • I don't think this could be achieved. since only one table task on the same table with the same task can be available

Hence the "three” in three None-logic tasks 😉

That would require three separate uniquely named tasks; e.g. task_1, task_2, task_3


Forum|alt.badge.img
  • Author
  • Apprentice
  • 8 replies
  • December 18, 2024
Mark Jongeling wrote:
Vince D wrote:
  • I don't think this could be achieved. since only one table task on the same table with the same task can be available

Hence the "three” in three None-logic tasks 😉

That would require three separate uniquely named tasks; e.g. task_1, task_2, task_3

 

Ah that sound logical to me! Thanks for elaborating. 


Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • 1032 replies
  • December 18, 2024
Updated idea statusNeeds feedbackMerged
Idea merged into:

All the votes from this idea have been transferred.

Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • 1032 replies
  • December 18, 2024

@Vince D Alright, based on your reply I have decided to merge this Idea with the one about Tasks on Grid lines.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings