Using external properties
External properties are ad-hoc properties that are not defined within the properties of a
case or task, but that can be rendered within their associated workflow views, for example, the
Properties widget. External properties are defined, retrieved, and persisted by using an external
data source such as a JAVA servlet, JSON file, or data service. The binding of external properties
is handled by the Properties area in the model layer.
General use case: Most organizations maintain several Systems of
Record data sources. These data sources often contain the most current single source of truth. Easy
access to this information helps case workers complete their goals. It is often necessary and
efficient to access this data live and not store a copy.
Scenario: While working a customer claim, an agent opens a case to
view the details of the case. In addition to claim-specific data, the agent can see the customer's
contact information, which is pulled live from the customer database. A list of past transactions
with the customer is also conveniently displayed, which saves the agent from having to access the
transaction system for this information.
This topic is shared by BAW, CP4BA. Last updated on 2025-03-13 12:15