Runs 100% on Atlassian Forge Zero External Data Egress Confluence & Jira Cloud

SpecSync v3.0 Product Documentation & CI Webhook Guide

Accelerate SAP NetWeaver PI 7.5 / PO 2027 Sunset migrations, automate SAP Cloud Integration (.iflw) governance and 1-click remediation, run offline payload simulations, and enforce release gates natively inside Confluence and Jira Cloud.

PI/PO 2027 Migration Factory

Convert legacy SAP PI/PO Integrated Configurations (.tpz / ICO XML) and ESR Java UDFs into SAP Cloud Integration BPMN2 .iflw bundles and Groovy 4.0 scripts with zero per-object fees.

18-Rule Governance & Auto-Fix

Audit authentication, TLS, CSRF, Edge Integration Cell readiness, and Script Collection reuse, then remediate vulnerable .iflw XML in one click.

Offline Simulator & JUnit 5

Simulate Content Modifiers and XPath/Simple Router branches without live tenant credentials, and export standalone Maven + Groovy 4 + JUnit 5 CI test suites.

CAB Matrix & Drift Guard

Compare DEV / QA / PROD externalized parameters, map cross-flow ProcessDirect and JMS blast radius, and auto-open Jira alerts on breaking schema drift.

1. Quickstart Installation & Macro Usage

SpecSync v3.0 installs directly from the Atlassian Marketplace into your Confluence Cloud and Jira Cloud site with zero external VMs, zero third-party subprocessors, and zero outbound firewall rules.

  1. Install from Atlassian Marketplace: Select Try it free on the SpecSync v3.0 Marketplace listing and choose your Standard or Advanced Edition plan.
  2. Embed the Confluence Macro: Open any Confluence Cloud page, type /SpecSync, and insert SpecSync Integration Contract & Drift Guard (or select Sync Integration Package from the page actions menu).
  3. Inspect or Migrate Artifacts: Upload a SAP PI/PO .tpz or ICO .xml archive, single .iflw, multi-flow SAP Cloud Integration .zip package, OpenAPI 3.x JSON specification, or WSDL 1.1/2.0 service contract.
  4. Publish Native ADF Specifications: Click Sync to Confluence Page to write clean Atlassian Document Format (ADF v1) architecture specifications directly into your Confluence page and store a structural SHA-256 baseline in Forge encrypted app storage.
Zero-Egress Guarantee: Every parser, Java UDF transpiler, governance rule, and diff engine executes strictly inside Atlassian's isolated Forge Node.js 22 runtime. No integration archive, Groovy script, or API contract ever leaves your Atlassian Cloud boundary.

2. Standard vs. Advanced Edition Capabilities

SpecSync v3.0 supports Atlassian Marketplace Editions under Paid via Atlassian billing so teams can choose documentation-only governance or the full 2027 PI/PO migration and DevOps suite.

Capability Standard Edition Advanced Edition
Single & Multi-iFlow (.iflw / .zip), OpenAPI 3.x & WSDL 1.1/2.0 Confluence ADF Docs Included Included
Structural SHA-256 Fingerprinting & Breaking-Drift Jira Issue Creation Included Included
Commit-Time CI/CD Webtrigger (specsync-ci-webhook) with HMAC-SHA256 Verification Included Included
SAP PI/PO 2027 Sunset Migration Factory (ICO & ESR Java UDF to CPI .iflw & Groovy 4.0) — Unlimited ($0 / object)
18-Rule Enterprise CPILint, Edge Integration Cell Audit & 1-Click .iflw XML Auto-Fix — Included
Offline Payload Simulator & Standalone Maven + Groovy 4 + JUnit 5 Exporter — Included
DEV / QA / PROD CAB Transport Matrix & Cross-Flow Blast-Radius Analyzer — Included

3. Automated CI/CD Webtrigger Setup (GitHub Actions, GitLab CI & cTMS)

SpecSync exposes an authenticated Atlassian Forge webtrigger (specsync-ci-webhook) so your CI/CD pipeline can publish updated Confluence specifications and raise Jira release-blocker tickets automatically whenever an integration package changes.

Step A: Provision Your Tenant Webtrigger URL & Signing Secret

Administrators generate the tenant-scoped Atlassian Forge HTTPS trigger URL and configure an optional HMAC-SHA256 signing secret stored under specsync:config:webhookSecret inside encrypted Forge app storage. When configured, SpecSync verifies the x-specsync-signature header in constant time before processing any payload.

Step B: Example GitHub Actions Workflow

name: Sync CPI Package to Confluence & Jira
on:
  push:
    branches: [ main ]
    paths: [ 'packages/**/*.zip', 'contracts/**/*.json' ]

jobs:
  specsync-publish:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Encode Integration Bundle & Sign Payload
        env:
          SPECSYNC_WEBHOOK_URL: ${{ secrets.SPECSYNC_WEBHOOK_URL }}
          SPECSYNC_WEBHOOK_SECRET: ${{ secrets.SPECSYNC_WEBHOOK_SECRET }}
        run: |
          B64_PKG=$(base64 -w 0 packages/S4_Orders_Bundle.zip)
          BODY=$(jq -n \
            --arg content "$B64_PKG" \
            --arg pageId "774102" \
            --arg jiraKey "INTGOV" \
            '{encoding:"base64", fileName:"S4_Orders_Bundle.zip", content:$content, confluencePageId:$pageId, jiraProjectKey:$jiraKey}')
          SIG=$(printf "%s" "$BODY" | openssl dgst -sha256 -hmac "$SPECSYNC_WEBHOOK_SECRET" -hex | awk '{print $2}')
          curl -fsSL -X POST "$SPECSYNC_WEBHOOK_URL" \
            -H "Content-Type: application/json" \
            -H "x-specsync-signature: $SIG" \
            -d "$BODY"

4. Enterprise Support & Contact

SyncForge Cloud provides dedicated support for enterprise SAP integration architects, Confluence administrators, and security review teams.