# Transformation Configuration Setup

## Overview

The Postscript extractor provides data on SMS activity. The Daasity transformation code maps data from the Postscript schema into the Unified Notifications Schema (UNS).

## Feature Dependencies

You must have enabled our [Code Repository](/technical-docs/transform-code/code-repository.md) feature in order to both access the Daasity transformation code as well as modify a Script Manifest File enabling this code to execute

We recommend you review the [Transformation Configuration](/technical-docs/workflows-and-scheduling/script-manifest-yaml-files.md) section of our Help documentation to familiarize yourself with our workflow engine and script manifest files.

## Script Manifest File (YML)

### Upstream Transformation Dependencies

{% hint style="danger" %}
This code is dependent on the following integration being installed:

* Postscript

This code block is dependent on the following upstream code blocks being implemented:

* [Initialization](/technical-docs/transform-code/transform-code/initialization-code.md)
  {% endhint %}

### Transformation Code Requirements

To enable the data transformation from the Postscript schema into UNS, the following code must be run in a workflow after[ the Initilization code block](/technical-docs/transform-code/transform-code/initialization-code.md):

{% code fullWidth="true" %}

```yaml
  uns_postscript:
    integrations:
      - postscript
    scripts:
      - "github://platform-sql-shared/scripts/base/1000_uns/postscript/1450_UNS_BAS_postscript_campaigns.sql"
      - "github://platform-sql-shared/scripts/base/1000_uns/postscript/1451_UNS_BAS_postscript_contacts.sql"
      - "github://platform-sql-shared/scripts/base/1000_uns/postscript/1452_UNS_BAS_postscript_lists.sql"
      - "github://platform-sql-shared/scripts/base/1000_uns/postscript/1453_UNS_BAS_postscript_contact_lists.sql"
      - "github://platform-sql-shared/scripts/base/1000_uns/postscript/1454_UNS_BAS_postscript_sends.sql"
      - "github://platform-sql-shared/scripts/base/1000_uns/postscript/1455_UNS_BAS_postscript_clicks.sql"
      - "github://platform-sql-shared/scripts/base/1000_uns/postscript/1456_UNS_BAS_postscript_unsubscribes.sql"
```

{% endcode %}

### Unified Notification Schema

Code to populate the UNS tables:

* <https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1000_uns/postscript/1450_UNS_BAS_postscript_campaigns.sql>
* <https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1000_uns/postscript/1451_UNS_BAS_postscript_contacts.sql>
* <https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1000_uns/postscript/1452_UNS_BAS_postscript_lists.sql>
* <https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1000_uns/postscript/1453_UNS_BAS_postscript_contact_lists.sql>
* <https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1000_uns/postscript/1454_UNS_BAS_postscript_sends.sql>
* <https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1000_uns/postscript/1455_UNS_BAS_postscript_clicks.sql>
* <https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1000_uns/postscript/1456_UNS_BAS_postscript_unsubscribes.sql>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.daasity.com/core-concepts/data-integrations/setup-guides/digital-integrations/postscript-beta/transformation-configuration-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.