---
title: "Example of a dox42 SkribbleAction"
slug: "screen-shots-of-a-sample-application"
description: "Manage document lifecycles with Skribble: seal, sign, and verify signatures easily. Retrieve signed PDFs and ensure compliance with validation tools."
tags: ["concept", "SkribbleAction"]
updated: 2025-05-22T10:45:14Z
published: 2025-07-01T07:23:12Z
canonical: "help.dox42.com/screen-shots-of-a-sample-application"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.dox42.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Example of a dox42 SkribbleAction

You can put the different placeholders into the body of your document template.

![Document layout showing multiple signature placeholders and a seal for validation.](https://cdn.document360.io/3acc69da-1de2-431d-95a6-08ae83717b4a/Images/Documentation/screen-shots-of-a-sample-application-image-vqr0wic5.png)

Signature placeholders in document template

During the generation process, depending on the action you choose, the different placeholder positions are identified, and then the text fragments are removed.

After that, the document is sent to Skribble platform:

- If the action is set to `seal` : The document is sent to Skribble and when sealed, the sealed document URL is given back in the result as per below:

```xml
<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body>

<GenerateDocumentResponse xmlns="http://www.dox42.com/">

<GenerateDocumentResult>

<GeneratedDocs />

<SavedDocs>

<SavedDocInfo>

<Index>0</Index>

<OutputAction>DigitalSigningCOA.Skribble</OutputAction>

<URL>https://api.skribble.com/v1/documents/88de7466-d50c-b171-3feb-f1374e02695c/content</URL>

</SavedDocInfo>

</SavedDocs>

<ResultMessage>OK</ResultMessage>

</GenerateDocumentResult>

</GenerateDocumentResponse>

</soap:Body>

</soap:Envelope>
```
- If the action is set to `signature` : The document is sent to Skribble and as it is signed per each signer, the `callbackUpdate` and `callbackSuccess` are used to manage the document lifecycle. When succeeded, the whole signed document can be retrieved based on the information available in the callback.
- If the action is set to `seal+signature` : The document is sent to Skribble and when sealed, the sealed document URL is given back in the result.

In the same time frame, the sealed document is sent to Skribble and as it is signed per each signer, the `callbackUpdate` and `callbackSuccess` are used to manage the document lifecycle. When succeeded, the whole signed document can be retrieved based on the information available in the callback

## Result

The seal and the signature places are visible through a thin line rectangle. When a signature is missing, the rectangle is empty.

![Document showing multiple signatures and a sample seal for verification purposes.](https://cdn.document360.io/3acc69da-1de2-431d-95a6-08ae83717b4a/Images/Documentation/screen-shots-of-a-sample-application-image-hfof2phl.jpg)

Signed PDF document

Signatures can be verified via a signature validator or directly in Adobe Acrobat Reader:

![Document showing multiple signatures with validation details and a certification seal.](https://cdn.document360.io/3acc69da-1de2-431d-95a6-08ae83717b4a/Images/Documentation/screen-shots-of-a-sample-application-image-3giem2xf.jpg)

Signature validation in Adobe Acrobat Reader