We discussed making the target optional so that it could be used only when it makes sense.
Further clarifications needed for the changes in the UI and the backend.
UI changes
- Add Decision Point Modal: Site would be default field, with button or arrow dropdown to add optional Target
- Decision Point table - remove target column, only show when target is defined in the Add Decision Point modal
- Data tab - remove Target when shown
Backend changes
- Change types
- Target may still be a required field in the DB, possibly replace with empty string when unused? May be easier than defining a rule for decision points that use targets and those that don't use targets
- Refactoring (we still have DPs called "Partition" in several places)
We need a design for "stacking" the site and target in the displays - like on the payload card. Site, with target in parentheses. Apply this design everywhere we display DP with site & target. Truncate or wrap?
We discussed making the target optional so that it could be used only when it makes sense.
Further clarifications needed for the changes in the UI and the backend.
UI changes
Backend changes
We need a design for "stacking" the site and target in the displays - like on the payload card. Site, with target in parentheses. Apply this design everywhere we display DP with site & target. Truncate or wrap?