more granularity of public exposure of elements

By J. on 13 Mar 2013
Hi,

Complex environments have lots of espaces, extensions. Some extensions are used exclusively by a certain part of the applications. some extension.espaces like richwidgets are used *everywhere*.
Especially with the proposed 4-layer architecture. There is a lot of manual maintenane and checking how espaces and extensions are referred to each other.

The public/private is not really up to par with such environments.

I like to see much improvement in that department.

"Protected" state
==============
Element in protected state is only available to refer in the package/espace it belongs to.
This would benefit extensions you need to have, but only accessable via the espace-wrapper.
other applications need to use the wrapper instead of accessing the extension by themself.
this is per element.

more fine-grained would be
"Selected" state
============
You can choose which espaces are allowed to refer your selected-state elements.
Not sure if this set espace-wide or per element.
per element is really heavy on the outsystems-housekeeping
Justin James18 Aug 2013
One of our biggest challenges is that our business objects layer has gotten absolutely massive. We would love to split this into multiple eSpaces so that two developers can work on it at the same time without merging so often or requiring many republishes of consumers. However, to do so would require us to make every entity public + not read only, so that the different eSpaces can all work together. We really need a way to make an entity public + not read only, but only for certain eSpaces, and make it public + read only for the rest.

Basically, I need an equivalent of "protected" or "friends".

J.Ja


Merged from 'Entities - Need protection between "Public" and "Private"' (idea created on 2013-08-18 16:57:02 by Justin James), on 2014-01-24 11:40:04 by Gonçalo Borrêga
J.20 Aug 2013
100% agreed.




Merged from 'Entities - Need protection between "Public" and "Private"' (idea created on 2013-08-18 16:57:02 by Justin James), on 2014-01-24 11:40:04 by Gonçalo Borrêga
J.4 Aug 2015
Bump, I need this still :)
Curt Raddatz5 Aug 2015
I too would love to see this feature.  It is important that Outsystems talk to a number of large customers who have run into this is and gather their input before designing this change.  I would hate to see one or two 'flavors' added (public, private, friends, etc.) without trying to design and implement the best solution for everyone.