4
 Followers
21
 Likes

Notify improvements

Frontend
Implemented
on 26 Sep 2018
Development Environment 11.0.109.0

The notify  handling is very nice, but i think we miss some stuff to make it more powerful.


1. ability to bubble the notify directly instead of going to an action "OnNotify" where the only thing is in the action:

NotifyWidget( NotifyGetMessage())


2. add a 2nd parameter which is called "MessageId", which is taken from the newly Introduced static-entity "Message".

   so you can handle message in a consistent way without have to check the message with index/substr or whatever



Created on 26 Feb 2014
Comments (11)
Merged this idea with 'Add native OS support for "Event System" Forge component or similar functionality' (created on 12 Oct 2017 18:43:49 by erik berg)

The external OS framework has a very limited call back mechanism between Web Pages and WebBlocks. The internal OS framework is much robust supporting bi directional communication between components.  The Forge component "Event System" also developers to tap into the internal framework.  The OS internal framework can change per release, leaving the "Event System" component inoperable for breaking changes.  Thus if one uses the "Event System" component, future OS upgrades are limited to those that "Event System" supports.  Adoption of the "Event System" component therefore is a high risk proposition.  OS should include the "Event System" component or similar wrapper around the OS internal framework.  With OS support, the risk of using the "Event System" component will be eliminated.

OS sells its self as a component based architecture, however any webblock component is really a second class citizen compared to the native OS components because the webblock has limited scope to what it can access, modify, and execute. 



This comment was:
- originally posted on idea 'Add native OS support for "Event System" Forge component or similar functionality' (created on 12 Oct 2017 by erik berg)
- merged to idea 'Notify improvements' on 27 Sep 2018 09:03:53 by Vasco Pessanha

This component is awesome, thank you Erik!

Liked :)



This comment was:
- originally posted on idea 'Add native OS support for "Event System" Forge component or similar functionality' (created on 12 Oct 2017 by erik berg)
- merged to idea 'Notify improvements' on 27 Sep 2018 09:03:53 by Vasco Pessanha
Merged this idea with 'Web Block and Popup Notify replaced by Events' (created on 24 Jul 2018 17:02:47 by Carlos Alexandrino)

In Web Applications (as implemented in P10 for Mobile Apps) Web Block and Popup notifications should be done in a structured way through events with the possibility of defining input parameters (just like Mobile that is really good)



This comment was:
- originally posted on idea 'Web Block and Popup Notify replaced by Events' (created on 24 Jul 2018 by Carlos Alexandrino)
- merged to idea 'Notify improvements' on 27 Sep 2018 09:04:37 by Vasco Pessanha

Changed the category to Frontend




This comment was:
- originally posted on idea 'Web Block and Popup Notify replaced by Events' (created on 24 Jul 2018 by Carlos Alexandrino)
- merged to idea 'Notify improvements' on 27 Sep 2018 09:04:37 by Vasco Pessanha

Changed the category to Frontend and the status to

Implemented
on 26 Sep 2018


Hey guys,

I'm glad to announce that, with the release of OutSystems 11, you can now use webblock events in Web applicatitons!

As usual, a special thank you to the idea creator, Joost, in our release notes.

Don't forget to check OutSystems 11 what's new to see all the new features that were released:

https://success.outsystems.com/Documentation/11/New_in_OutSystems_11

Merged this idea with 'Web Blocks Screen Action executed on Web Page Ajax Submit - Event OnAjaxSubmit' (created on 16 Oct 2017 22:04:59 by Eduardo Jauch)

It is very common to have forms where a certain number of web blocks are repeated, through the use of a List Records, for example.

But it is very trick to be able to validate or submit inputs to be saved on those web blocks at the same time.

Would be nice to have the possibility of calling a Screen Action on an event like an "OnAjaxSubmit", enabling the execution of the action in case of an Ajax Event on the parent, for example, without having to resort to confuse/obscure JavaScript code + hidden inputs.

Of course, the transaction would probably be a problem, where I think the solution would be to all the events triggered at this moment to be in the same transaction (I don't know if this would be possible).



This comment was:
- originally posted on idea 'Web Blocks Screen Action executed on Web Page Ajax Submit - Event OnAjaxSubmit' (created on 16 Oct 2017 by Eduardo Jauch)
- merged to idea 'Notify improvements' on 27 Sep 2018 09:23:11 by Vasco Pessanha

It's not supported by OutSystems, but you may want to look at: https://www.outsystems.com/forge/component/597/event-system/



This comment was:
- originally posted on idea 'Web Blocks Screen Action executed on Web Page Ajax Submit - Event OnAjaxSubmit' (created on 16 Oct 2017 by Eduardo Jauch)
- merged to idea 'Notify improvements' on 27 Sep 2018 09:23:11 by Vasco Pessanha

Hello Gonçalo,

I know Event-System. Already used it :)
But the idea is to implement something directly into the platform that make this easier on those scenarios.

Cheers,
Eduardo Jauch



This comment was:
- originally posted on idea 'Web Blocks Screen Action executed on Web Page Ajax Submit - Event OnAjaxSubmit' (created on 16 Oct 2017 by Eduardo Jauch)
- merged to idea 'Notify improvements' on 27 Sep 2018 09:23:11 by Vasco Pessanha
views
887
Followers
4