Results for “ams_dlg_flow_comps_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_DLG_FLOW_COMPS_VL is a Marketing (AMS) module view that exposes the language-translated definition of dialog flow components used by Oracle Marketing's one-to-one and multi-step dialog/campaign execution engine. A "flow component" represents an individual step within a dialog — such as sending a deliverable, evaluating an identify rule, branching, or presenting an iPage — and this view presents each component together with its user-facing name and description resolved to the session language. It is a "_VL" (view with translation) object, meaning it joins the base entity table to its translation table and applies the USERENV('LANG') filter so that reporting and integration layers see only the rows relevant to the logged-in user's language.

The view plays a supporting role in ETRM reporting: it is intended for read-only queries that enumerate the components belonging to a dialog and their configured behavior, rather than for transactional maintenance. In the documented reference, the object is noted as "Not implemented in this database," indicating that its availability depends on whether the Marketing dialog-flow functionality (and its underlying tables) has been installed and seeded in the given environment.

Underlying Base Objects

Although the ETRM metadata records no separately documented base objects, the view text itself makes the dependency explicit. It is defined over two tables:

• AMS_DLG_FLOW_COMPS_B — the base detail table holding all component rows, including foreign keys, descriptive flexfield attributes, and the SKIP_FLAG indicator.
• AMS_DLG_FLOW_COMPS_TL — the translation table supplying NAME and DESCRIPTION per language.

The join is performed on B.FLOW_COMPONENT_ID = T.FLOW_COMPONENT_ID, filtered by T.LANGUAGE = USERENV('LANG'). Because the join is an equi-join without an outer clause, a component appears only when a translation row exists for the current language. Note also that B.ROWID is aliased as ROW_ID, which is a common pattern used to make the view updateable in the Form/BC4J layer.

Key Columns

• FLOW_COMPONENT_ID — Primary key uniquely identifying a flow component; the join key to the translation table.
• DIALOG_ID — The parent dialog to which the component belongs.
• COMPONENT_TYPE_ID / COMPONENT_TYPE_CODE — Classifies the step (for example, deliverable, rule, or iPage).
• SKIP_FLAG — Controls whether the component is bypassed during dialog execution; of particular interest to users searching for this term.
• DELIVERABLE_ID, IDENTIFY_RULE_ID, IPAGE_ID, DISPLAY_TEMPLATE_ID — Pointers to the specific artifact executed at this step.
• CREATE_NEW_USER_FLAG, CREATE_LEAD_NOW_FLAG — Flags governing user/lead creation behavior at the step.
• INTEREST_TYPE_ID, PRIMARY_INTEREST_CODE_ID, SECONDARY_INTEREST_CODE_ID, COUNTRY_ID — Interest and geography context attributes.
• NAME, DESCRIPTION — Translated label and description for the component.
• Standard WHO and framework columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER, plus ATTRIBUTE_CATEGORY/ATTRIBUTE1–15 and COMPONENT_ATTRIBUTE_CATEGORY/COMPONENT_ATTRIBUTE1–15 descriptive flexfields.

Common Use Cases and Queries

Typical usage centers on auditing dialog configuration and identifying components that are intentionally bypassed. To list all non-skipped components for a dialog with their translated names:

• SELECT flow_component_id, name, component_type_code FROM ams_dlg_flow_comps_vl WHERE dialog_id = :p_dialog_id AND NVL(skip_flag,'N') = 'N' ORDER BY flow_component_id;
• To isolate skipped steps: SELECT flow_component_id, name, description FROM ams_dlg_flow_comps_vl WHERE skip_flag = 'Y' AND dialog_id = :p_dialog_id;
• To enumerate all components of a given type: SELECT dialog_id, flow_component_id, name FROM ams_dlg_flow_comps_vl WHERE component_type_code = :p_type;

Because the view applies the session-language filter, queries return names in the language set by USERENV('LANG'), making it convenient for localized reporting and integration extracts.