ihouvet
ihouvet
### Overview There is a very little standardization across the different views listing configuration items (e.g. Forms table, Ref List table, Roles table, etc…). For the sake of consistency there...
### Overview Currently only admins have the option to view the latest version. This can however be quite limiting when testing since testing with different roles is often required to...
### Overview Current configuration item process imports all items from configuration migration packages, and creates a new version, regardless if the configuration item being imported is actually different from the...
### Overview Current current configuration item lifecycle includes a ‘Ready’ state, which indicates that the configuration has been finalized, but it is not Live yet. This does not seem to...
### Overview Image the following scenario: - Client App references both Module A and Module B - Both Module A and B also reference Module C, but Module A references...
### Overview The notion of Configuration Inheritance was partially defined in the initial configuration item specification, but it was not implemented. Imagine the following scenario: - MyApplication which uses uses...
### Background Dynamically generated crud endpoints are extremely useful in that the reduce the amount of boilerplate code that needs to be written just to expose CRUD functionality on entities....
### Overview Some places in Shesha still use the term 'Widget' when referring to form components. Any such references need to be updated to us the term 'Component' 
## Background The form templates are currently very simplistic, and only provide a handful of components (basically title area, toolbar, and data table in the case of TableView template) and...
### Acceptance Criteria 1. It should be visible to the user whether the reference list is Code based (i.e. implemented as an Enum) or Data driven 2. If the reference...