Skip to main content
Solved

Value stays in task input field even after resetting its value to null in default code.

  • December 20, 2024
  • 2 replies
  • 89 views

Dennis1690
Vanguard
Forum|alt.badge.img+4

Context: I’m running into the issue that my inputfield is being populated by the ID (of the tablerow, not the lookup value) even when I’ve resetted it’s value to null. It only happens when the default triggers. 

Also the inputfield behaves like it’s null. I know this because I’ve build checks to enable functionality based on population of that field. For instance.. @supplier_1 is not null » do something. That ‘something’ isnt available or happening.

What I’ve tried: 

  • Check our logs
  • Check indicium logs
  • Set @supplier_1 = null
  • Set @supplier_1 = ‘’
  • Check the tsf send message parameter for aborting my flow.
  • Change order of code, first the message then the set = null and vice versa.

Neither of them seems to work.

What is the expected behavior and how am I helped? »  If I can get a empty value in the task popup so my userbase doesnt get confused.

Version: 24.2

Best answer by Mark Jongeling

Hi Dennis,

Which exact Universal GUI version are you using? It seems to me this could be a possible bug. Maybe the latest version has you covered 😄

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

2 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3945 replies
  • Answer
  • December 30, 2024

Hi Dennis,

Which exact Universal GUI version are you using? It seems to me this could be a possible bug. Maybe the latest version has you covered 😄


Dennis1690
Vanguard
Forum|alt.badge.img+4
  • Author
  • Vanguard
  • 25 replies
  • January 15, 2025

We will upgrade first , if that doesnt solve Ill reopen a new ticket.


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