Hidden fields with pushButton widget become visible when using FlattenFormFields method to flatten fields.

Workaround: do not flatten fields if the IsHidden property of any of its Widget's is set to True:

 var fieldsList = formFields.ToList();
 for (int i = 0; i < fieldsList.Count; i++)
 {
     var field = fieldsList[i];
     bool flattenCurrentField = true;
     if (field.FieldType == FormFieldType.PushButton)
     {
         PushButtonField pushButtonField = (PushButtonField)field;
         PushButtonWidget[] widgets = pushButtonField.Widgets.ToArray();

         foreach (var widget in widgets)
         {
             var baseType = typeof(PushButtonWidget).BaseType.BaseType.BaseType;
             PropertyInfo[] properties = baseType.GetProperties(BindingFlags.NonPublic | BindingFlags.Instance);
             PropertyInfo isHidden = properties.FirstOrDefault(p => p.Name == "IsHidden");
             bool value = (bool)isHidden.GetValue(widget);
             if (value == true)
             {
                 flattenCurrentField = false;
                 break;
             }
         }
     }

     if (flattenCurrentField)
     {
         document.AcroForm.FlattenFormField(field);
     }
 }

Allow table spiting to be done on whole rows instead of splitting the content of the rows.

Attached is a small project that shows a possible workaround.

The table border styles are not imported correctly with a specific document.

Workaropund:

RtfFormatProvider provider = new RtfFormatProvider();
RadFlowDocument document = provider.Import(File.ReadAllText(@"..\..\test.rtf"));
 
PdfFormatProvider pdfProvider = new PdfFormatProvider();
var tables = document.EnumerateChildrenOfType<Table>();

foreach (var table in tables)
{
    table.Borders = new TableBorders(new Border(BorderStyle.None));
}


using (FileStream stream = File.OpenWrite(@"..\..\result.pdf"))
{
    pdfProvider.Export(document, stream);
}

Images could have orientation set in their metadata:

Workaround: Rotate the image before inserting it into the RadFixedPage (check the attached project).

Currently, signature flags, represented by the 'SigFlags' optional entry, are not imported and exported, and there is no API for setting them.
As a result, documents signed with RadPdfProcessing (or with RadPdfViewer) appear in Adobe Reader without the blue document message bar at the top (the analogue of the RadPdfViewer's SignaturePanel).

If the API is supported, setting the flag to 1 or 3 would ensure that the message bar would be visualized in Adobe Reader.

With the current implementation when exporting a Stitching function all the containing functions are exported as Sampled functions even if they originally have been imported as Exponential interpolation functions, which leads to an increase in the size of the document.

More information can be found in the PDF Specification.

Splitting a row leads to copying all rows below it. During that operation, the information for the row height is lost, when the previous row has a cell spanning on the split one, leading to a missing row in the exported document.

The issue is a regression introduced in R1 2021.

According to PDF specification, all fonts should be embedded except from 14 Standard PDF fonts. This guarantees that the PDF file is self-contained and will be rendered successfully on different devices and operation systems.

However, some clients prefer not to embed fonts in order to reduce file size. That is why we may provide such API.