Configurable Status to Action Mapping for Claim Payments

This setup enables claim adjusters to perform context-aware actions on financial items. Admins map dynamic picklist values of Claim Coverage Payment Detail Status to static enum values such as Draft, Paid, Canceled, and Deleted. They enable logic-driven actions such as Pay and Cancel that depend on a standardized, static Payment Status, regardless of custom dynamic values. The system supports configurable business actions, including standard ones such as Pay and Delete, as well as custom flow-based actions tailored to customer needs. This approach provides a flexible, low-code setup for mapping and future-proofing claim workflows without hardcoding logic.

Admins can map multiple dynamic enums to a single static enum-based status and set one value as the default. This mapping enables the system to use the dynamic status to drive both UI and API behavior. Admins can also configure actions for a given status. By linking a flow to a dynamic status value, the flow appears as an action in the UI for any record with that status.

• Configure Static to Dynamic Status Mapping
  Map predefined static values for the status of a claim coverage payment detail record to dynamic values based on your organization’s needs. Make sure that you map at least one dynamic value for each static value.
• Edit Static to Dynamic Status Mapping
  You can add a new dynamic value to an already mapped static value or change the default dynamic status value.
• Configure Manageable Actions
  Configure the actions that an adjuster can take based on the payment status of a claim coverage payment detail record. For example, enable the Edit, Pay, Delete, and Pay Ex Gratia actions when the payment status is Draft. Some statuses have preconfigured default actions. For example, the Paid status has a default Cancel Payment action.