Active/Inactive state handling for elements in MooD

As a Solution builder

I want built in MooD functionality to handle active/inactive states for elements

So That i can control the selection and display of elements towards the end user without having to rely on the constant use of queries that checks against a pick item or boolean field for whether or not the element is inactive whenever i want to use the defined relationship.

The context being among other things that MooD's event log does not persist for Elements that are deleted from the repository, and as such it's best practice never to delete Elements for which one might want to retain an event log. Moreover it's often important to preserve the element in the state it was in when rendered inactive in the repository, for instance a retired application or an employee whom has left where you need to retain information about all of the activites that employee undertook or the governance roles held. 

Benefits Currently if one wants to build a solution that is somewhat future proof, one should never really use the built in relationship field functionality and instead always rely on a query that finds the relationship but checks the active/inactive state of the element. If MooD was able to handle Active/Inactive it would make it so much easier to use the built in functionality as intended, and utilize things like the default "elements that i can relate to" for single/multi element pickers, without having to worry about the user selecting an inactive element.

Acceptance Criteria 

1. MooD handles active/inactive states, and it's possible to set this state using MooD BA as well as with button actions and synchronizers
2. It's possible to modify the display value for Active/Inactive for non-english uses
3. Inactive elements are automatically excluded from selectors, graphs and matrices
4. It should be possible to toggle on the display of Inactive elements, maybe as a global setting for the given session.
   In which case the solution build can choose to give the users that option through a button action or instead modify their graphs/matrices/selectors to contain a query that conditionally displays inactive elements through the where clause. Essentially the solution builder then controls when and where inactive elements are displayed, and has to consider when they might want to be included, rather than worry about always excluding them.
5. It should be possible to style inactive elements differently, for instance the solution builder might want to always display the inactive elements with "strikethrough" applied to the element name, or a conditional colour formatting.

Customer / Originator Solution builder

Priority Medium