OpenText Active Community - Trading Grid - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between OpenText Active Community - Trading Grid and OpenText Core Signature

OpenText Active Community - Trading Grid and OpenText Core Signature complement each other well in enterprise workflows that require partner collaboration, controlled document exchange, and legally binding approvals. Trading Grid provides a shared environment for communication and issue resolution across trading partners, while Core Signature enables secure electronic signing of agreements and operational documents. Together, they support faster cycle times, better auditability, and reduced manual handling.

1. Trading partner agreement execution

Flow: OpenText Active Community - Trading Grid to OpenText Core Signature

When a new trading partner is onboarded or an existing relationship is updated, the partner agreement can be posted in the Trading Grid community for review and coordination, then routed to Core Signature for electronic signing by internal legal, procurement, and the external partner contact. Once signed, the executed agreement is returned to the Trading Grid community for shared visibility and reference.

• Reduces email-based contract handling
• Creates a clear approval and signature trail
• Improves onboarding speed for new partners

2. Exception resolution requiring formal approval

Flow: Bi-directional

When a dispute or transaction exception is discussed in Trading Grid, such as pricing variances, shipment discrepancies, or service credits, the resolution package can be assembled in Core Signature for formal approval. After signatures are completed, the approved resolution is posted back to the Trading Grid community so all relevant parties can act on the same finalized decision.

• Supports controlled exception handling
• Ensures approved outcomes are visible to all stakeholders
• Reduces delays caused by offline approvals

3. Contract amendment collaboration and execution

Flow: OpenText Active Community - Trading Grid to OpenText Core Signature

Trading Grid can be used to coordinate redlines, comments, and supporting documents for contract amendments with suppliers, distributors, or logistics partners. Once the amendment is finalized, Core Signature handles the legally binding signature workflow. The signed amendment is then shared back through Trading Grid for operational teams to reference during execution.

• Supports collaborative drafting with external partners
• Keeps amendment history organized and auditable
• Helps operations teams work from the latest signed version

4. Compliance acknowledgements for trading partners

Flow: OpenText Active Community - Trading Grid to OpenText Core Signature

Organizations often need trading partners to acknowledge updated policies, security requirements, code of conduct documents, or regulatory notices. Trading Grid can distribute the notice and track partner engagement, while Core Signature captures the formal acknowledgement signature. Signed acknowledgements are then stored or referenced in the community for compliance tracking.

• Improves compliance evidence collection
• Provides a consistent acknowledgement process across partners
• Reduces risk of missed policy updates

5. Supplier onboarding document package approval

Flow: Bi-directional

During supplier onboarding, Trading Grid can be used to exchange required documents such as tax forms, banking details, insurance certificates, and operational contacts. Once the onboarding package is complete, Core Signature can route the final onboarding agreement, NDA, or master service terms for signature. After execution, the signed documents and onboarding status can be shared back in Trading Grid to complete the partner setup process.

• Streamlines onboarding across procurement, finance, and legal
• Improves completeness of partner records
• Shortens time to first transaction

6. Change request approvals for B2B process updates

Flow: OpenText Active Community - Trading Grid to OpenText Core Signature

When a trading partner requests a change to shipping terms, service levels, order routing, or invoicing instructions, the request can be discussed and validated in Trading Grid. If the change requires formal approval, Core Signature can capture sign-off from the appropriate business owners and the partner. The approved change is then published back to Trading Grid for operational execution.

• Creates a controlled process for partner-driven changes
• Reduces miscommunication between business and operations teams
• Ensures only approved changes are implemented

7. Shared document review with final signature closure

Flow: OpenText Active Community - Trading Grid to OpenText Core Signature

Trading Grid can serve as the collaboration space for reviewing supporting documents such as statements of work, quality plans, or logistics procedures. After comments are resolved and the final version is agreed, Core Signature is used to obtain signatures from all required parties. The signed document is then retained in the community as the authoritative version for future reference.

• Separates collaboration from formal execution
• Improves version control and document governance
• Supports cross-functional review without losing auditability

Together, OpenText Active Community - Trading Grid and OpenText Core Signature enable a practical end-to-end workflow for partner collaboration, approval, and execution. Trading Grid manages the conversation and shared context, while Core Signature provides the formal legal closure needed for enterprise transactions.