Transformation Configuration Setup

This pages provides instructions on what transform code should be added to a script manifest file to transform Postscript data into the Unified Notification Schema (UNS)


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 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 section of our Help documentation to familiarize yourself with our workflow engine and script manifest files.

Script Manifest File (YML)

Upstream Transformation Dependencies

This code is dependent on the following integration being installed:

  • Postscript

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

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:

      - postscript
      - "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"

Unified Notification Schema

Code to populate the UNS tables:

Last updated