SmartFormRecognizer

Author: Yaminisrisf4389

Document-Processing/SmartDataExtractor/NET/SmartFormRecognizer/recognize-forms .md

@@ -150,42 +150,30 @@ public  async void Button_Click(object sender, RoutedEventArgs e)
 
 ## Async variants with CancellationToken
 
-The async overloads accept an optional `CancellationToken` to cancel long-running operations:
+The async overloads accept an optional `CancellationToken` to cancel long-running operations.Initially cancellationToken value in default.Based on our requirement we can optimize the cancellationToken value.
 
 - `Task<PdfLoadedDocument> RecognizeFormAsPdfDocumentAsync(Stream inputStream, CancellationToken cancellationToken = default)`
 - `Task<Stream> RecognizeFormAsPdfStreamAsync(Stream inputStream, CancellationToken cancellationToken = default)`
 - `Task<string> RecognizeFormAsJsonAsync(Stream inputStream, CancellationToken cancellationToken = default)`
 
 Example with cancellation token (PDF stream):
 
-```csharp
-public async Task RecognizeWithCancellationAsync(CancellationToken token)
+{% tabs %}
+{% highlight c# tabtitle="C#" %}
+
+public async Task RecognizeWithCancellationAsync()
 {
     FormRecognizer recognizer = new FormRecognizer();
 
     using FileStream inputStream = new FileStream("Input.pdf", FileMode.Open, FileAccess.Read);
-
+    CancellationTokenSource cts = new CancellationTokenSource();
+    cts.CancelAfter(TimeSpan.FromSeconds(5)); // cancel in 5 seconds
+    CancellationToken token = cts.Token;
     using Stream resultStream = await recognizer.RecognizeFormAsPdfStreamAsync(inputStream, token);
 
     using FileStream fileStream = File.Create("Output.pdf");
     await resultStream.CopyToAsync(fileStream, token);
 }
-```
-
-Notes:
-- Always forward cancellation tokens to I/O methods when available.
-
----
-
-## Common corrections and best practices shown in the examples
-
-- Use `using` (or `await using` for IAsyncDisposable) to ensure streams are disposed.
-- Use `FileAccess.Read` when only reading input files.
-- Do not reuse mismatched variable names (e.g., `smartFormRecognizer` vs `recognizer`) — pick one consistent name.
-- Prefer `async`/`await` in UI event handlers but avoid `async void` except for top-level event handlers; prefer `async Task` where possible for testability.
 
----
-
-If you want, I can also:
-- Add a short snippet showing how to handle `FormRecognizeOptions` with these calls.
-- Add a unit test or a small console app sample demonstrating each method.
+{% endhighlight %}
+{% endtabs %}

Document-Processing/SmartDataExtractor/NET/SmartFormRecognizer/working-with-recognize-option.md

@@ -50,7 +50,7 @@ recognizer.FormRecognizeOptions.DetectCheckboxes = true;
 {% endtabs %}
 
 ### DetectRadioButtons
-`DetectRadioButtons` is a boolean property in FormRecognizeOptions that specifies whether the form recognizer should detect radio button elements in the document. When enabled (default: true), the recognizer identifies circular selection controls. Turning this option off can streamline processing, reduce unnecessary output, and improve performance when radio buttons are not relevant to the form you are analyzing.
+`DetectRadioButtons` is a boolean property in FormRecognizeOptions that specifies whether the form recognizer should detect radio button elements in the document. When enabled (default: true), the recognizer identifies circular objects in images or in the Pdf documnets then add radio buttons in that identified locations.
 
 {% tabs %}
 {% highlight c# tabtitle="C#" %}
@@ -68,7 +68,7 @@ recognizer.FormRecognizeOptions.DetectRadioButtons = true;
 {% endtabs %}
 
 ### DetectSignatures
-`DetectSignatures` is a boolean property in FormRecognizeOptions that controls whether the form recognizer should identify signature fields within a document. When enabled (default: true), the recognizer scans for handwritten-style areas, signature lines, or regions typically used for signing, and includes these detected signature blocks in the structured output. 
+`DetectSignatures` is a boolean property in FormRecognizeOptions that controls whether the form recognizer should identify signature fields within a document. When enabled (default: true), the recognizer scans for handwritten-style areas, signature lines, or regions typically used for signing, and includes these detected signature blocks in the output. 
 
 {% tabs %}
 {% highlight c# tabtitle="C#" %}
@@ -101,14 +101,17 @@ recognizer.FormRecognizeOptions.ConfidenceThreshold = 0.9;
 {% endtabs %}
 
 ### PageRange
-`PageRange` is an optional int[,]? property in FormRecognizeOptions that allows you to control exactly which pages of a document the form recognizer should process. Each row in this 2‑dimensional array represents a 1‑based inclusive range in the form [start, end], the recognizer processes all pages in the document. Defining page ranges helps improve performance, reduce unnecessary processing, and target only the sections of the document relevant to your extraction workflow.
+`PageRange` is an optional int[,]? property in FormRecognizeOptions that allows you to control exactly which pages of a document the form recognizer should process. Each row in this 2‑dimensional array represents a 1‑based inclusive range in the form [start, end], the recognizer processes all pages in the document. Defining page ranges helps improve performance, reduce unnecessary processing, and target only the sections of the document relevant to your extraction workflow.We can also provide values in single page.Also If we provide values in decending order it will consider as ascending order and perform detection.
 
 {% tabs %}
 {% highlight c# tabtitle="C#" %}
 
 FormRecognizer recognizer = new FormRecognizer();
 
-// Set a page range
+// Set a page range single
+recognizer.FormRecognizeOptions.PageRange = new int[,] { { 3 } };
+
+// Set a page range 2D
 recognizer.FormRecognizeOptions.PageRange = new int[,] { { 3, 3 } };
 
 {% endhighlight %}