https://github.com/OAGi/Score/issues/486
Allow delete deleting the association(s) from a revised ACC.
#1 - Remove ASCC/BCC record from DB.
- The way Execute the same logic we are currently taking for rev=1. Unlike ACC/ASCCP/BCCP, ASCC/BCC is will be permanently removed from DB.
- History A history of this action is stored in Log table.#2 - Mark as deleted a ‘Deleted’ state.
- What if add/delete multiple times Do we need to keep properties such as ‘guid’ or ‘definition’ for the association deleted by the actions? What if the user often takes ‘Add/Delete’ actions for the same association. Do we allow the records that have the same den and from_acc/to_asccp?
- When inserting an association, we may able to use the previous record if it exists.
- Should we include preserve the ‘Deleted’ CCs of deleted states in the new release?Questions
- How No need to generate worry about backward-compatibility. ? What if the developer misses the insert?
- If there are BIE references (for End-user CCs , and Extensions), block the deletion.
- Upliftfor {a.} logic should be changed. b/c we are using GUID for matching key. but we can not cannot keep the removed record's GUID.
for {b.} deleted state association is not available in BIE.
Move to (refactor‘Move to’ feature (One of refactor features).
based ACCs.to upper-level
e.g.
Production Order Line Base. Details
- Status Line Base. Details (target from acc*)
- Line Base. Details (o)
- Line Identification Base. Details (o)The ACCs that is basing the target ACC.to lower-level
e.g.
Production Order Line Base. Details (o)
- Status Line Base. Details (target from acc*)
- Line Base. Details
- Line Identification Base. Details
- If there are multiple ACCs that are basing based on the same target ACC, it can not cannot be available.
e.g. Maintenance Order Line Base / Shipment Request Order Line Base / Shop Floor Control Base Line Base ...Are we allow the move to only {a.} ? if there is only one {b.}, should we allow it?
...