Skip to Content (Press Enter)
Back to Ideas
51
Like
Follow Idea
2016-11-21 23-23-05
Gonçalo Borrêga
Invoke a webblock action from a screen (with output arguments)
1700Views
20Comments
On our RadarOn our Radar
Frontend (App Interfaces)
This would allow to have isolation on the webblocks and have the screens coordinate several sections of the page, all in the same transaction.
Ex: The screen manages a person, and we have a webblock responsible for saving the address section, another the contacts, and another the general detail. The button Save on the Screen would call all the Saves in the webblocks.

This would increase reusability a lot.
11 May 2010
Copy link to comment

I agree with the need, but I would probably implement it with webblock callbacks inside the same transaction.
11 May 2010
Copy link to comment
2016-11-21 23-23-05
Gonçalo Borrêga
As long as the callbacks start having strongly typed parameters (one of the strongest points the platform has gotten us used to) and it has an output....
12 May 2010
Copy link to comment
I believe this idea could be "joined" with this one: https://www.outsystems.com/ideas/555/

This is so necessary when you want to implement your own controls.
11 Jan 2012
Copy link to comment
Or like this one https://www.outsystems.com/ideas/1212/webblock-output-parameter/
In .Net you can create a public property with an object from a UserControl/webBlock and the main page can call it as a output parameter in Outsystems.
For example:
Page A has a UserControlX.
The UserControlX  has a textBox "Name" and a checkBox "Visible"
Page A can access the information inside the UserControl:  UserControlX.MyEntity
UserControlX :
public string MyEntity
    {
        get
        {
           return GetMyWebBlockData();
        }
    }
 
 
public MyEntity GetMyWebBlockData()
    {
           MyEntity myEntity = new MyEntity();
 
           myEntity.Name = txtName.Text;
           myEntity.Visible = cbxVisible.Check;
              
 
           return myEntity;
         
    }
 
In my situation I’ve a save button in the Page A and I would like to save the information inside UserControlX/WebBlock.
07 Aug 2014
Copy link to comment
We really really need public variables on webblocks as everyone is running into this limitation.
I've seen some really nasty workarounds involving session variables and it is blocking a lot of scenarios where webblocks (with public variables) would be the perfect and very clean solution.
24 Jul 2015
Copy link to comment
This is already possible with the Event System component. Check its documentation - on Lesson 05 it is shown how to split a form into fragments, each on its own web block. And how to save all fragments from a single save button inside the screen.
26 Jul 2015
Copy link to comment
@Tim: we use NotifyWidget callbacks + serializing data, but yeah, it's dirty.
@Leonardo: of course someone made something to make it possible, but I'd like a native solution!
30 Jul 2015
Copy link to comment
Event System component is awesome Leo. Great Job! :)

But we still don't have a good and native solution to access information inside a webblock. Webblocks with public variables (like @Tim idea), with output parameters or passing parameters by reference are good solutions (and very old too), but for uknown reasons they never was attended...
30 Jul 2015
Copy link to comment
Event System component is awesome Leo. Great Job! :)

But we still don't have a good and native solution to access information inside a webblock. Webblocks with public variables (like @Tim idea), with output parameters or passing parameters by reference are good solutions (and very old too), but for uknown reasons they never was attended...
30 Jul 2015
Copy link to comment
Hi,

When you drag a web block to a screen, we should be able to access all widgets inside that web block, while we're in the context of that screen.

Since a web block is rendered just as a simple copy of code to the screen, the widgets should be accessible at runtime, and thus, at design time.

Merged from 'Accessible widgets inside Web Blocks' (idea created on 2010-11-12 16:12:57 by Gonçalo Almeida), on 2016-10-24 14:17:35 by Goncalo Borrega
12 Nov 2010
Copy link to comment
Agreed!

I now need to do some 'funky stuff' to get output from a web-block.

It would be nice to be able to declare some variables inside a web-block as 'public'



Merged from 'Accessible widgets inside Web Blocks' (idea created on 2010-11-12 16:12:57 by Gonçalo Almeida), on 2016-10-24 14:17:35 by Goncalo Borrega
13 Dec 2010
Copy link to comment
2016-11-21 23-23-05
Gonçalo Borrêga
Merged this idea with 'Accessible widgets inside Web Blocks' (created on 2010-11-12 16:12:57 by Gonçalo Almeida)
24 Oct 2016
Copy link to comment
Merged this idea with 'Let a component call actions exposed in its children webbocks (a la OOP)' (created on 08 Nov 2018 16:46:49 by Tiago Lopes)
14 Jun 2019
Copy link to comment

Imagine that a page uses a certain webBlock that has a screen action that performs something.

How many times did you have the need of calling that action not within the context of the webBlock but in the context of the page?

I know that there is a workaround for this.. to hide a button in the webBlock, add a cssClass 'someClass' to it, assign that action and then:

javascript :: document.getElementsByClassName('someClass')[0].click()

Anyway, the platform could let us do this in a more elegant way like adding a property 'IsPublic' to the screen actions and let the parents use the public screen actions of its children webblocks.



This comment was:
- originally posted on idea 'Let a component call actions exposed in its children webbocks (a la OOP)' (created on 08 Nov 2018 by Tiago Lopes)
- merged to idea 'Invoke a webblock action from a screen (with output arguments)' on 14 Jun 2019 16:53:36 by Tiago Simões
08 Nov 2018
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Changed the category to
Frontend


This comment was:
- originally posted on idea 'Let a component call actions exposed in its children webbocks (a la OOP)' (created on 08 Nov 2018 by Tiago Lopes)
- merged to idea 'Invoke a webblock action from a screen (with output arguments)' on 14 Jun 2019 16:53:36 by Tiago Simões
08 Nov 2018
Copy link to comment

I couldn't agree more, this should be high priority



This comment was:
- originally posted on idea 'Let a component call actions exposed in its children webbocks (a la OOP)' (created on 08 Nov 2018 by Tiago Lopes)
- merged to idea 'Invoke a webblock action from a screen (with output arguments)' on 14 Jun 2019 16:53:36 by Tiago Simões
19 Nov 2018
Copy link to comment

I think this would be SUPER useful.  

Think of the many times, you need to do something in a web block when the parent Saves, without loosing the information that the web block has been compiling.


I.e. uploading documents to a page that hasn't been saved yet, and when you save, then the documents are all assigned to the page.



This comment was:
- originally posted on idea 'Let a component call actions exposed in its children webbocks (a la OOP)' (created on 08 Nov 2018 by Tiago Lopes)
- merged to idea 'Invoke a webblock action from a screen (with output arguments)' on 14 Jun 2019 16:53:36 by Tiago Simões
18 Mar 2019
Copy link to comment
Changed the status to
On our RadarOn our radar

Hi Tiago,

Indeed being able to call actions in children blocks can sometimes be handy. I'll add this to our radar so we can tackle it in a future release.

Thanks,
Tiago Simões



This comment was:
- originally posted on idea 'Let a component call actions exposed in its children webbocks (a la OOP)' (created on 08 Nov 2018 by Tiago Lopes)
- merged to idea 'Invoke a webblock action from a screen (with output arguments)' on 14 Jun 2019 16:53:36 by Tiago Simões
14 Jun 2019
Copy link to comment

Hello,

Great news..

This would be even more useful if this webblocks actions run in the same transaction.. i.e., only one call to the server, only one db transaction..

Best

15 Jun 2019
Copy link to comment