I would like to add that it is for content replacement (text in paragraf or title and sometimes metadata-fields). For example when in the content is used the term 'X' but due to changes the term should be changed to 'Y'. A confirmation (you want to change this text?')  is also part of this request.

We've implemented similar a number of times for clients (using the coreserive) and the devil is always in the details. In your experience, is this required often - and if so - does your client use labels/server-side replace also?

We've implemented similar a number of times for clients (using the coreserive) and the devil is always in the details. In your experience, is this required often - and if so - does your client use labels/server-side replace also?

Find and replace is currently available in Experience Space for RTF-fields but this doesn't cover the other fields yet. I'm also interested in the answer to Mark's question. 

Find and replace is indeed available n RTF fields, however, this is within a single component itselff. What Frank Alta is looking for is finding and replacing across the components.