Hi mitpatoliya,
thanks for your answer.
It is not problem for me in which state is content during job execution. I have "problem" with default behavior of the content after job finishes. You are right I can add content on target server, edit it and delete it, but I can not edit, change metadata, delete content that was replicated from source server.
So my goal is to replicate content from source to destination and after that to use that content on destination (target) server normally (to edit it, delete it…). I don't want users to have experience that this content was replicated from another server at all, is that possible with replication jobs?
Thanks…