[QAARQ-31] Add content deletion support Created: 17/Dec/18 Updated: 11/Jul/22 Resolved: 19/Dec/18 |
|
| Status: | Closed |
| Project: | Queued Asynchronous Activation over RabbitMQ |
| Component/s: | activation |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Richard Gange |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Description |
|
Currently deleting a node is not supported. It's a 2 step process that requires first that the node be marked as deleted. Then you must publish the deletion. Unpublishing content is supported but is not quite the same as deletion since deleting removes the node from both author and public. |
| Comments |
| Comment by Richard Gange [ 19/Dec/18 ] |
|
I think the consensus here is that we will not attach rabbitMQ to this action. Instead call either the command workflow-activate or default-activate directly from the delete action. This will depend on if you need workflow for deletion. For example in the pages app that configuration would be here: /modules/pages/apps/pages/subApps/browser/actions/activateDeletion. So you would change the catalog property to either workflow or default. |
| Comment by Richard Gange [ 19/Dec/18 ] |
|
Docs updated to cover this. |