Form Exchange Process Flow Chart

Summarized end-to-end ERP Pro v9 Form Exchange workflow with standard and swimlane diagrams

Form Exchange Process Flow Chart

This page provides a concise, end-to-end view of the ERP Pro v9 Form Exchange process, including a basic flow chart and a swimlane version by role.

Summarized Steps

  1. Support (Cloudscape): Generate a request code and API key, and associate the request with Client Identifier (CID) and CRM case number.
  2. Support (ERP Pro v9): Paste the request code and API key into ERP Pro v9, then upload the source forms package/report files to S3.
  3. Support -> Forms Dev (CRM): Notify Forms Dev that the package is ready for editing, including the CRM case number.
  4. Forms Dev (Cloudscape): Navigate to Client -> Form Exchange and download the package.
  5. Forms Dev (Local): Extract, edit, and validate required form changes.
  6. Forms Dev (Cloudscape): Use the Ready to Upload tab to upload required edited files (individually) into the CID/CRM# path, typically under DONE.
  7. Forms Dev -> Support (CRM): Notify Support that forms are ready to be scheduled.
  8. Support (Cloudscape): Open Schedule File Push, review files, enter scheduling details, and choose immediate or scheduled deployment.
  9. Cloudscape Automation (EventBridge + Schedules): Poll pending schedules, read deployment metadata, and push files to the target cloud-hosted ERP Pro environment.
  10. System Status Tracking: Execution moves through PENDING -> IN_PROGRESS -> COMPLETED (or FAILED).

Basic Flow Chart

flowchart TD
    A1["Support in Cloudscape\nGenerate Request Code + API Key\nAssociate CID + CRM #"]
    A2["Support in ERP Pro v9\nPaste Request Code + API Key"]
    A3["Support in ERP Pro v9\nSelect files and upload package to S3"]
    A4["Support notifies Forms Dev via CRM\nInclude CRM #"]

    B1["Forms Dev in Cloudscape\nClient -> Form Exchange\nDownload package"]
    B2["Forms Dev edits files locally"]
    B3["Forms Dev in Cloudscape\nReady to Upload\nUpload required files to CID/CRM#/DONE"]
    B4["Forms Dev notifies Support via CRM\nForms ready to schedule"]

    C1["Support in Cloudscape\nSchedule File Push\nEnter details"]
    C2{"Push now or later?"}

    D1["EventBridge polls Schedules table"]
    D2["System reads metadata\n(target host/path/environment)"]
    D3["System pushes files to cloud-hosted ERP Pro environment"]
    D4["Status updates\nPENDING -> IN_PROGRESS -> COMPLETED/FAILED"]

    A1 --> A2 --> A3 --> A4 --> B1 --> B2 --> B3 --> B4 --> C1 --> C2
    C2 -->|Immediate| D1
    C2 -->|Scheduled| D1
    D1 --> D2 --> D3 --> D4

Swimlane Flow Chart (By Role)

flowchart LR
    subgraph S1[Support Rep]
        SR1[Generate request code and API key in Cloudscape\nAssociate CID + CRM #]
        SR2[Paste credentials in ERP Pro v9\nUpload source package to S3]
        SR3[Notify Forms Dev in CRM\nPackage ready]
        SR4[After Forms Dev handoff, schedule file push in Cloudscape\nImmediate or scheduled]
    end

    subgraph F1[Forms Developer]
        FD1[Open Client -> Form Exchange\nDownload package]
        FD2[Edit files locally and validate changes]
        FD3[Ready to Upload tab\nUpload required edited files to DONE]
        FD4[Notify Support in CRM\nForms ready to be scheduled]
    end

    subgraph C1[Cloudscape Automation]
        CA1[EventBridge checks pending schedules]
        CA2[Read metadata from Schedules table]
        CA3[Push files to target cloud-hosted ERP Pro environment]
        CA4[Update status: PENDING -> IN_PROGRESS -> COMPLETED/FAILED]
    end

    SR1 --> SR2 --> SR3 --> FD1 --> FD2 --> FD3 --> FD4 --> SR4 --> CA1 --> CA2 --> CA3 --> CA4

Notes

  • CRM handoffs are manual and happen at two key points: Support -> Forms Dev and Forms Dev -> Support.
  • Forms Dev can intentionally exclude files that should not be returned (for example, signature files).
  • Automated push behavior applies to cloud-hosted clients where deployment targets are known.