Skip to main content
Solved

Message design differ


Forum|alt.badge.img+4

Hi all,

when executing the “tsf_send_message” function I get 2 diffirent design of the message box.
For context, in img 1A. I use a custom made message named “warning_msg” in a DEFAULT control procedure which return the design shown in img 1B.

img 1A
img 1B

 

Now I use the same concept of the “tsf_send_message” (img 2A) in a TASKS control procedure but as we can see in img 2B, it uses a diffirent design. I think it uses the browser default message.

img 2A
img 2B

 

I would like to use the same design accross all procedures. Please help!

Thanks.

Best answer by Mark Jongeling

Hi,

I think this is a limitation of the Web GUI. Since already a pop-up (the Task) is open, it may not be able to throw another one but I'm not sure. Is this still a problem or were you able to find a workaround?

Idea created: 

 

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

2 replies

Forum|alt.badge.img+4

Hey Mark,

I was able to get it working like I wanted with a workaround involving process flow and decisions. But I also think it would be really handy if the first method was also a valid option. I think I will create a idea for this.

Thanks 


Mark Jongeling
Administrator
Forum|alt.badge.img+23
  • Administrator
  • 3972 replies
  • Answer
  • June 20, 2022

Hi,

I think this is a limitation of the Web GUI. Since already a pop-up (the Task) is open, it may not be able to throw another one but I'm not sure. Is this still a problem or were you able to find a workaround?

Idea created: 

 


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