Home | Connectors | OpenText Decision Service | OpenText Decision Service - OpenText Notifications Integration and Automation
Flow: OpenText Decision Service ? OpenText Notifications
When a decision rule approves, rejects, or routes a case for manual review, OpenText Decision Service can trigger a notification to the responsible team or user. This is useful in loan approvals, claims handling, onboarding, or compliance reviews where staff need immediate awareness of decision outcomes to continue processing without delay.
Business value: Reduces turnaround time, prevents cases from sitting idle, and improves process visibility across teams.
Flow: OpenText Decision Service ? OpenText Notifications
When business rules are updated in OpenText Decision Service, OpenText Notifications can inform affected stakeholders such as operations managers, customer service leads, or compliance officers. For example, a change in credit policy thresholds or eligibility criteria can be broadcast to users who rely on those rules in daily work.
Business value: Improves governance, reduces confusion caused by outdated decision criteria, and supports controlled rollout of rule changes.
Flow: OpenText Decision Service ? OpenText Notifications
If a decision cannot be made because required data is missing, a rule set is incomplete, or a threshold is exceeded, OpenText Decision Service can send an alert through OpenText Notifications to the support or operations team. This is especially valuable in high-volume environments where exceptions must be handled quickly to avoid service disruption.
Business value: Speeds exception handling, reduces manual investigation time, and helps maintain service continuity.
Flow: OpenText Decision Service ? OpenText Notifications
OpenText Decision Service can classify transactions or cases into review queues based on business rules, then OpenText Notifications can notify the assigned reviewer or team. For example, suspicious transactions, high-risk applications, or non-standard requests can be routed to specialists with immediate notification.
Business value: Ensures the right people are engaged quickly, improves control over high-risk decisions, and supports consistent triage across departments.
Flow: OpenText Decision Service ? OpenText Notifications
When a decision changes the status of a workflow, OpenText Notifications can send updates to internal users or downstream systems that need to act on the result. In customer onboarding or service request processing, this keeps sales, operations, and support teams aligned on whether a case is approved, pending, or declined.
Business value: Improves cross-team coordination, reduces status-checking overhead, and supports faster customer response times.
Flow: OpenText Decision Service ? OpenText Notifications
OpenText Decision Service can evaluate business conditions such as aging cases, overdue approvals, or policy exceptions and trigger notifications when SLA risk is detected. Managers and process owners can be alerted before deadlines are missed, allowing proactive intervention.
Business value: Helps teams meet service commitments, reduces compliance risk, and improves operational control.
Flow: OpenText Notifications ? OpenText Decision Service
Users receiving alerts about repeated exceptions, frequent manual overrides, or high volumes of pending cases can initiate a request to review or adjust decision rules. These feedback events can be captured and used to refine rule logic in OpenText Decision Service, especially in environments where business policies change often.
Business value: Creates a feedback loop between operations and rule management, improving decision accuracy and supporting continuous process improvement.