Mark elements as deprecated
292
Views
5
Comments
New
Service Studio

I think having the ability to mark elements (actions, screens, structures...) as Deprecated in order to notice where the changes should be made in order to substitute it by the most recent one, this could be done by adding a Boolean property on the element properties such has:

When having the "Yes" value a Warning on the Service Studio would be displayed regarding every place where this element is used.

1.PNG

Why not do the same as OutSystems does and give them a prefix DEPRECATED_

Hi Daniël the advantage would be to have the elements appear as a warning on the Service Studio, so the developer knows where all the deprecated elements are being used without having to use "Find Usages" for each, as well as having to change all the elements name manually once this property is set the element would be renamed to DEPRECATED_(name).

Good thought !!!

A dedicated property would be a good time saver. It could have scope for being reported on in the architecture dashboard to help identify deprecated actions/webblocks that are still in use etc. 

2016-04-21 20-09-55
J.
 
MVP

Long overdue and I agree with it.

This will help enormously if truechange reflects it as warnings.