Site properties shared between multiple eSpaces
2336
Views
17
Comments
On our RadarOn our Radar
Backend

It would be useful to have, what we could call, site properties that would be shared between multiple eSpaces. This would avoid the replication of site properties with the same value over multiple eSpaces.
The solution to this is to create a public user action that only returns the value a site property, and is consumed by other espaces.
Although, if site properties could be made public, that way it would be easier to share site properties among espaces.
2016-04-21 20-09-55
J.
 
MVP
Good suggestion.

@Tiago, yes, but the problem with that is, you have to republish the consumers espace when a site-property is updated.
because the property is cached in the consumers-espace.
which imho, is not correct!


Maybe you could store the properity into a database table and enable caching on the query.

Get the information from the database, use it in any eSpace you wish.




Joost,
Don't know exactly what you mean when you say you have to republish the consumer espace when the site property is updated.
In 5.1 tried the following test, and it works ok, as I expected:
1-Consumer espace consumes action that returns the value of a site property.
2-In consumer espace displayed the current value of the site property. Ok.
3-In producer espace updated the value of the site property.
4-In consumer espace displayed the current value of the site property. Ok, displayed the new value.
No republication was needed of the consumer espaces.

Good suggestion.

@Tiago, yes, but the problem with that is, you have to republish the consumers espace when a site-property is updated.
because the property is cached in the consumers-espace.
which imho, is not correct!


very good

Merged this idea with 'Public/Private site properties' (created on 27 Oct 2016 13:37:00 by bfcantante)

Instead of have duplicate site properties in all espaces why not share? I speak about for example the Currency, DecimalSeparator, GroupSeparator.



This comment was:
- originally posted on idea 'Public/Private site properties' (created on 27 Oct 2016 by bfcantante)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:09:37 by Kilian Hekhuis
Merged this idea with ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 13:45:07 by Huarlem Lima)

Would be of good help if 'Site properties' and 'Session Variables' had 'public' property.



This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis
2016-04-21 20-09-55
J.
 
MVP

Why?


You can create action-wrappers for them?




This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis

Precisely to avoid this work.



This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis
Changed the category to
Backend


This comment was:
- originally posted on idea ''Site properties' and 'Session Variables' with 'public' property' (created on 05 Sep 2018 by Huarlem Lima)
- merged to idea 'Site properties shared between multiple eSpaces' on 08 Nov 2018 11:10:18 by Kilian Hekhuis

I like this idea but it should be share as read-only and only allow the owner eSpace or Service Center to change it.

Agreed. Site properties should be treated as read-only anyways, changing them in code is bad practice.

Merged this idea with 'Give ability to make site properties public' (created on 19 Sep 2019 08:13:14 by Stefano)

Have a property public (boolean) for a site property so we can expose the site property outside the module.


I found this idea which pretty much solves the problem as my idea would. But it would be far more easy if we could just set the property public just like we do with server actions.

https://www.outsystems.com/ideas/5779/accelerate-creation-of-actions-to-expose-site-property-values?IsFromAdvancedSearch=True



This comment was:
- originally posted on idea 'Give ability to make site properties public' (created on 19 Sep 2019 by Stefano)
- merged to idea 'Site properties shared between multiple eSpaces' on 22 Oct 2020 05:53:21 by Daniël Kuhlmann

This is a duplicate of 481



This comment was:
- originally posted on idea 'Give ability to make site properties public' (created on 19 Sep 2019 by Stefano)
- merged to idea 'Site properties shared between multiple eSpaces' on 22 Oct 2020 05:53:21 by Daniël Kuhlmann