Confirmation message?

Use the prompt event response type, no code needed and it supports string substitution for building the message.

docs.infor.com/.../lsm1454148024166.html

Differing style/buttons are available and these can also prompt WinStudio Events.

if you absolutely have to code then your code can trigger the event handler which shows the prompt, and the prompt event can in turn invoke another event handler with script attached.

In many cases no code is required to do basic operations like variable management and conditional checks.

Use the prompt event response type, no code needed and it supports string substitution for building the message.

docs.infor.com/.../lsm1454148024166.html

Differing style/buttons are available and these can also prompt WinStudio Events.

if you absolutely have to code then your code can trigger the event handler which shows the prompt, and the prompt event can in turn invoke another event handler with script attached.

In many cases no code is required to do basic operations like variable management and conditional checks.

Very interesting Lee, and although this is not my thread I'm wondering: the doc seems to say that the prompt would allow for the posting to occur even without an answer because it is asynchronous and non-blocking (?).
So, does this mean it would not suffice for a confirmation message, whose purpose is to block the further events to execute unless the user clicked Yes/OK on the prompt?
(or did I misunderstand the doc?)

Hi Florent.  

The way the prompt is designed, it should be the last handler in the event, unless you want operations to continue whilst the prompt is open.

I think the docs mention the standard behaviour to avoid confusion.

It will trigger secondary event(s) depending on which button is pressed.

Begin with a GenerateXmlPrompt event which displays the prompt, then does nothing.

Have a GenerateXmlOK event which does the generation, firing that event off OK button in the Prompt.

A GenerateXmlCancel event could be fired if you wanted to do something when the user cancels the operation (though usually on a 'cancel' there would be no follow up actions).

Lee

¡Ey Lee! Thanks very much, this really helpful me.
Now i can validate "something" depending of my user's decisions.