David Watkins

Permissions: setup up perms for logical and physical flow operations

3

### Description Similar to #6061 ### Resourcing We intend to contribute this feature

Attestations: changes to data types for logical flows not picked up as 'breaking' changes to app flow attestation

2

### Description Looks like data type changes to logical flow are incorrectly recorded with a `child_kind` of `DATA_TYPE` not `LOGICAL_DATA_FLOW`. *Historical fix* To fix old data use something like: ```...

LGTM is reporting the following (`ScenarioRatingItem`): https://lgtm.com/projects/g/finos/waltz/snapshot/7466e0642c67bd03d3c148e8e93e8d613325184b/files/waltz-service/src/main/java/com/khartec/waltz/service/scenario/ScenarioRatingItemService.java?sort=name&dir=ASC&mode=heatmap#x7da8d21ae41bd43:1

Candidates: - [ ] physical-spec/utilities.js (whole file)

Person Hierarchy should be part of entity_hierarchy

4

Or more precisely it does not write anything which causes hierarchy lookups on that one thing to fail ;)

### Description - create formatter file - [ ] indentation (2 lines between methods) - [ ] no `import foo.*;` - [ ] stack params (not sure if possible) -...

### Description Admin feature (similar to remove orphans) ### Resourcing We would like to add this request to the Waltz team's feature backlog

### Description Currently phys flows, logical flows etc can have an `is_readonly` flag set on them. Physical specs cannot. As far as I can tell this is a simple omission,...