Platform
Learn
Community
Support
Sign up
or
Log in
Profile
messages
Messages
logout
Logout
Platform
Home
Downloads
IPP
Licensing
Project Sizing
Beta
Learn
Training
Documentation
Evaluation Guide
Community
Jobs
Home
Forums
Forge
Ideas
Badges
Members
Support
Partner Guide
Resources Library
Opportunities
Account Management
Pre Sales Demos
Sign up
or
Log in
Home
Jobs
Forums
Forge
Ideas
Members
Badges
Community
›
Ideas
›
Notify into Webblock
Advanced Search
2
Followers
2
Likes
Notify into Webblock
António Matos
António Matos
at
BOOL
+ 4
#6 990
in Community Rank
Frontend
On our radar
It would be nice to have a notify into a webblock.
We can send information from a webblock into a screen, but we can't send information into an webblock without refreshing it causing a rerender of everything inside the webblock.
It's almost like calling a webblock screen action from inside a screen action from the parent screen/webblock.
This would allow for more dynamic screens
Created on 12 Dec 2015
Comments (4
)
Gary
1 Jun 2016
Gary
CTO
at
IBM
#2 002
in Community Rank
We also need this!
J.
3 Jun 2016
J.
Outsystem MVP, Outsystems Expert developer, Senior consultant
at
CoolProfs
+ 12
#9
in Community Rank
so how do you expect this to work?
- webblock has to know which screen the notify is coming from.
- how do you prevent a infinite loop of notifying the webblock notifies screen, screen notifies webblock, webblock notifies screen, screen notifies webblock.
further more, WHY do you need it?
António Matos
3 Jun 2016
António Matos
at
BOOL
+ 4
#6 990
in Community Rank
The behaviour would be similar to have a hidden button inside the webblock, and click it trough javascript on the parent window.
The webblock would expose a screen action to its parents, and the child screen action could be called inside a parent screen action (much like a normal action).
This would be great for big webblocks with lots of content. Imagine you only want to refresh a small part of the webblock, the parent would call the exposed screen action that does this refresh.
The only way to have an infinite loop is to have a notify on the webblocks exposed screen action and to call that exposed screen action on the parents notify action and not have any control if the action was called (very easy thing for a programmer to control)
George Jeffcock
6 Jun 2016
George Jeffcock
API Junky
at
Jitterbit
+ 2
#355
in Community Rank
I think I am with J on this.
There has to be some rules/principles that the platform is based on and I think this is one of them. WebBlocks can not be notified peroid and the paltform has been built on that and other principles. It may be restrictive but as a sotware developer as we all are I think we can see why it is a principle and removing it now multiplies the complexity expodentially outweighing the benefit at this stage of maturity of the platform. My vote would be live without it but if designing the platform from the begining it would be nice to be able to notify any 'building block' of a window.
views
506
Followers
2
Loading...
Loading
(hidden) New Badge Popup