Currently to put a document in the trash, we change its lifecycle state to deleted. This has several unfortunate consequences:
- the lifecycles have to have a 'deleted' state
- the lifecycles have to be designed with appropriate transitions to the 'deleted' state
- putting a document in the trash loses its previous lifecycle information, so we have to guess a lifecycle state if the document is restored (removed from the trash).
To avoid this, we should use a specific system property boolean ecm:isTrashed instead of the lifecycle state to denote trashed documents.
The will be Java and NXQL APIs to access this boolean.
- depends on
-
NXP-25762 Fix detection of trashed state and browsing trashed folderish
-
- Resolved
-
- is related to
-
NXP-23798 Trash Flow
-
- Resolved
-
-
NXP-24883 Fix BulkLifeCycleChangeListenerTest on MariaDB/MySQL
-
- Resolved
-
-
NXMOB-513 Handle new trash implementation in all NXQL queries
-
- Resolved
-
-
NXP-24335 BAF: Resilient Bulk Actions Framework
-
- Resolved
-
-
NXJS-136 Add new Trash API
-
- Open
-
-
JAVACLIENT-151 Add new Trash API
-
- Resolved
-
-
NETCLIENT-10 Add new Trash API
-
- Resolved
-
-
NXPY-54 Add new Trash API
-
- Resolved
-
-
PHPCLIENT-15 Add new Trash API
-
- Resolved
-
-
NXP-25259 BAF: Implement change trash state computation
-
- Resolved
-
- is required by
-
NXS-4527 NOS: Trash Management Support
-
- Resolved
-