Process Extentions for Crystal Reports 2013

Question

The administrator guide says there is an API document that explains how to use and develop processing extentions.  This is suppose to be a method to row restrict Crystal Reports documents.  Can anyone point me to the API document on how to build a process extension and then how to build a crystal report to leverage that extension (is it as simple as referencing a parameter)?  If anyone has any information on this works I would appreciate just general information too.
thanks,
Bob

Answer 1

Thanks Dell and Ludek!
I was able to also stumble upon the same documentation as you guys have shared and agree with your assessment that there is lack of various details.
At my current company, we are using a processing extension that has been carried over from a long time ago and it is a C++ based DLL. I should've been more elaborate with my question in the earlier post but what I am looking for is as as following: (We are going through an upgrade form 3.1 to 4.1)
Is Crystal Reports Processing Extension API still supported in 4.1?
Is there an alternative to this API with 4.1?
Based on the Dell's response (and Bob's original post), since this API is still part of the 4.1 SDK documentation I would tend to think it is still supported. Even further, I was able to look in 4.1 CMC and Extensions registration menus are still available. During our report conversion from 3.1 to 4.1 (using the Upgrade Manager Tool), our reports kept their references to the DLL. Only thing we need to do is to load the DLL in 4.1 environment using CMC which is fairly straight forward.
However, I am more interested in finding out if SAP has a recommendation on alternatives? In our case we are using this extension for following: (likely suitable for its own post)
When creating a recurring Schedule our Crystal Reports has a Time frame parameter. Values for this parameter are "Last 7 days, Last 10 day, Last 30 days, Last Quarter....". This parameter then gets mapped to two BW query parameters (start and end dates). Every week when a schedule executes the report, we intercept the request and check the Time frame parameter value, calculate the start and end dates and set those values in report. So the processing extension is to intercept the request and to set the report parameters based on the original parameter. Our current solution is working and it seems we can carry it over with us to 4.1.
Another requirement of Row Level Security has come up. Processing API documentation suggests Processing Extensions as one potential solution for this. So before investing time further into API, I wanted to make sure that the Processing Extension is the only way to plug in custom processing into a Crystal Reports.
Best regards,
Adnan