How to handle this replication scenario

[LinearGradient]

Hi,

Let's pretend an author deletes a page from a web site but does not want to immediately publish (deactivate) the deleted page from the publisher instance. After some more changes he finally decides to publish his changes.

How can the backend code deactivate the deleted pages, now that their respective nodes are deleted from the repository?

Thanks

[Sham_HC · Accepted solution]

Nothing out of the box and you can implement at project level by making use of listener.  You have to design & implement an concepts like Trash OR recycle.  

[LinearGradient]

Sham HC wrote...

Nothing out of the box and you can implement at project level by making use of listener.  You have to design & implement an concepts like Trash OR recycle.  

How does Touch UI handle this scenario? In the following screen:

[img]Screen Shot 2014-07-25 at 1.47.47 am.png[/img]

What happens when the user deletes the page? Is it also immediately deactivated?

[Sham_HC]

LinearGradient wrote...

What happens when the user deletes the page? Is it also immediately deactivated?

yes will deactivate