> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/appian/smart-services/wv-smart-services.md).

# Apryse WebViewer Smart Services

Learn how to use the Apryse SDK to interact with the WebViewer component in Appian. Convert Base64 strings to documents or document versions effortlessly with WebViewer Smart Services. Appian WebViewe

## Overview

The Apryse SDK provides a set of smart services that can be used to interact with the WebViewer component in Appian. These smart services allow you to perform various operations such as converting a Base64 string to a document or document version. They aim to help assist you in the interaction between your documents in Appian and WebViewer.

## Available WebViewer Smart Services

### Base64 to Document

This smart service converts a Base64 string to a document. This is useful when WebViewer provides the document data as a base64 string and you want to convert it to a document in Appian.

**Input Parameters**

| Parameter Name     | Type   | Required | Multiple | Description                                        |
| ------------------ | ------ | -------- | -------- | -------------------------------------------------- |
| `Base64 Data`      | Text   | Yes      | No       | The base64 string to convert to a document.        |
| `Upload Folder ID` | Folder | Yes      | No       | The folder where the document will be uploaded to. |
| `Filename`         | Text   | Yes      | No       | The filename of the document.                      |
| `Extension`        | Text   | Yes      | No       | The extension of the document.                     |

**Output Parameters**

| Parameter Name       | Type     | Description                                 |
| -------------------- | -------- | ------------------------------------------- |
| `Error Message`      | Text     | The error message if the conversion failed. |
| `Has Error`          | Boolean  | Whether the conversion failed.              |
| `Output Document ID` | Document | The saved document.                         |

### Base64 to Document Version

This smart service converts a Base64 string to a document version. This is useful when WebViewer provides the document data as a base64 string and you want to convert it to a document version in Appian.

**Input Parameters**

| Parameter Name | Type     | Required | Multiple | Description                                         |
| -------------- | -------- | -------- | -------- | --------------------------------------------------- |
| `Base64 Data`  | Text     | Yes      | No       | The base64 string to convert to a document version. |
| `Document ID`  | Document | Yes      | No       | The document to add the version to.                 |

**Output Parameters**

| Parameter Name       | Type     | Description                                 |
| -------------------- | -------- | ------------------------------------------- |
| `Error Message`      | Text     | The error message if the conversion failed. |
| `Has Error`          | Boolean  | Whether the conversion failed.              |
| `Output Document ID` | Document | The saved document version.                 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/appian/smart-services/wv-smart-services.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.