Box - OpenText Decision Service Integration and Automation

Common Integration Use Cases Between Box and OpenText Decision Service

1. Contract and policy document review with automated approval routing

Data flow: Box ? OpenText Decision Service ? Box

When a new contract, policy, or regulated document is uploaded to Box, metadata and document attributes are sent to OpenText Decision Service to determine the required approval path. The rules engine can evaluate factors such as document type, contract value, jurisdiction, business unit, or risk level and return the appropriate routing decision. Box then uses the decision outcome to trigger the correct review workflow, assign approvers, and apply retention or access controls.

Business value: Speeds up approvals, reduces manual triage, and ensures consistent governance for high-risk content.

2. Sensitive content classification and handling based on business rules

Data flow: Box ? OpenText Decision Service ? Box

Box Shield or Box metadata can identify sensitive files such as HR records, patient documents, financial statements, or legal evidence. OpenText Decision Service evaluates the content classification against business rules and determines the required handling, such as restricting external sharing, enforcing additional approvals, or applying specific retention policies. The decision is then written back to Box to update permissions or workflow status.

Business value: Improves compliance and reduces the risk of inappropriate access or sharing of regulated content.

3. Case file intake and decision-based document collection

Data flow: OpenText Decision Service ? Box

In claims, investigations, onboarding, or dispute resolution processes, OpenText Decision Service can determine which documents are required based on case attributes such as customer type, claim amount, region, or exception status. Box is then used as the secure repository for collecting and organizing the required files. The decision service can update the case workflow with missing document requirements, while Box stores the submitted evidence and supporting records.

Business value: Reduces incomplete case submissions, improves process consistency, and shortens cycle times.

4. Exception handling for regulated approvals

Data flow: Box ? OpenText Decision Service ? Box

When a document in Box is flagged for exception handling, such as a non-standard contract clause, policy deviation, or compliance waiver, Box sends the relevant metadata to OpenText Decision Service. The rules engine evaluates whether the exception can be auto-approved, must be escalated, or requires legal or compliance review. The result is returned to Box to route the file into the correct exception workflow and notify the right stakeholders.

Business value: Standardizes exception management and ensures high-risk items receive the right level of review.

5. Retention and disposition decisions driven by business rules

Data flow: Box ? OpenText Decision Service

Box Governance can manage content lifecycle, while OpenText Decision Service determines retention actions based on business rules such as record type, legal hold status, customer relationship, or regulatory jurisdiction. For example, a document may be retained longer if it is tied to active litigation or disposed of earlier if it is a low-risk operational record. Box applies the retention or disposition action based on the decision returned by OpenText Decision Service.

Business value: Supports defensible records management and reduces the risk of premature deletion or over-retention.

6. External partner document sharing with policy-based controls

Data flow: Box ? OpenText Decision Service ? Box

Before a file is shared with an external partner, distributor, auditor, or regulator through Box, OpenText Decision Service can evaluate whether the recipient, document type, and business context meet sharing policy requirements. The decision service can approve the share, require redaction, mandate expiration dates, or block the action entirely. Box then enforces the decision through sharing settings and access controls.

Business value: Enables secure collaboration with third parties while maintaining policy compliance and auditability.

7. Automated escalation for high-risk workflow items

Data flow: Box ? OpenText Decision Service ? Box

Documents stored in Box can be part of workflows such as procurement, finance, legal, or healthcare operations. OpenText Decision Service can assess risk indicators from the document metadata and related case data, then decide whether the item can proceed normally or must be escalated to senior management, legal, or compliance. Box Relay can then route the item accordingly and keep the supporting documents attached to the workflow.

Business value: Improves control over high-risk transactions and ensures timely escalation of sensitive matters.

8. Policy updates without changing Box workflow logic

Data flow: OpenText Decision Service ? Box

Organizations often need to update approval thresholds, retention rules, sharing policies, or exception criteria as regulations and internal policies change. By externalizing these rules in OpenText Decision Service, Box workflows can remain stable while decision logic is updated centrally. Box continues to execute the workflow, but the decision service determines the current business outcome based on the latest rules.

Business value: Reduces IT rework, accelerates policy changes, and improves consistency across departments and regions.