Hi Leonid.

Basically, you have two different options to achieve your end goal - supporting a set of properties as a re-usable property across content types.

Simple approach.
Episerver normally recommends to combine your shared set of properties via a BlockType and then use that as an in-line property on your ContentTypes. It would e.g. mean that you could do something like this:

[ContentType(DisplayName = "TeaserBlock", GUID = "38d57768-e09e-4da9-90df-54c73c61b270", Description = "Heading and image.")]
    public class TeaserBlock : BlockData
    {
         
                [CultureSpecific]
                [Display(
                    Name = "Heading",
                    Description = "Add a heading.",
                    GroupName = SystemTabNames.Content,
                    Order = 1)]
                public virtual String Heading { get; set; }
 
                 
                [Display(
                    Name = "Image", Description = "Add an image (optional)", 
                    GroupName = SystemTabNames.Content,
                    Order = 2)]
                public virtual ContentReference Image { get; set; } 
         
    }

 [ContentType(DisplayName = "ArticlePage", GUID = "b8fe8485-587d-4880-b485-a52430ea55de", Description = "Basic page type for creating articles.")]
    public class ArticlePage : PageData
    {
                [Display(
                    Name = "Teaser",
                    GroupName = SystemTabNames.Content,
                    Order = 10)]
                public virtual TeaserBlock Teaser { get; set; }
          
    }

As you can see, my block type "TeaserBlock" can be used when defining a PageData class. "TeaserBlock" would be your "Recurrence Settings". Be aware that your "Recurrence Settings" has to be BlockData and it will not be presented via a popup when editors are accessing the fields.

Advanced approach - which sounds like the approach you are taking as per your description
The other option you have is more complicated, as it requires you to create a custom PropertyData, EditorDescriptor and DOJO widget. It will enable you to fully customize how your type is persisted and authored. Doing these things has been covered by numourous blog posts and I can only recommend you to be inspired by e.g. my posts here: 

http://fellow.aagaardrasmussen.dk/2016/04/23/get-predictive-time-zones-in-datetime-properties/

http://fellow.aagaardrasmussen.dk/2016/05/03/categorization-of-content-in-episerver-commerce/  

They introduce you to creating a custom PropertyData, EditorDescriptor and DOJO widget. It though still requires some effort to tie the loose ends - e.g. create the pop-up driven widget for your specific need.
I hope the post about "Get predictive Time-zones in DateTime Properties" can help you with your question regarding how to pass the data back to Episerver. In short, its done via this._setValue(value);

Hope my answer helped you get further. I would normally go for the Simple approach and avoid extending Episerver unnecessarily. 

Casper Aagaard Rasmussen

Hello Casper,

Thanks for the reply, it would be interesting to know the additional methods.
I've solved the problem with my way - I transmits data via JSON to the controller where processes them as needed.

But in the future if I will have to do something similar, I'll use your method.

Regards,

Leonid Berman