Agent That Is Configured With a Custom Event Mapped to a Object Column, Does Not Trigger When the Object Column Is Updated Using Direct SQL Update (DSU).
(Doc ID 2602403.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management Cloud Service - Version 6.3.4 and laterOracle Transportation Management - Version 4.0 and later
Oracle Global Trade Management Cloud Service - Version 6.3.4 and later
Oracle Global Trade Management - Version 6.1.0 and later
Information in this document applies to any platform.
Symptoms
OTM does not trigger an Order Release Agent that is configured with a Custom Event Mapped to an ATTRIBUTE column, when the ATTRIBUTE column is updated using a Direct SQL Update (DSU) agent action.
EXAMPLE:
-------------
01. Custom Event:
Agent Event ID: CUSTOM_EVENT
Data Query Type: ORDER RELEASE
Contact Notification ID: ORDER - MODIFIED
Modification Event: Y
User-defined Event: Y
Agent Event Table Mappings
Table Name: ORDER_RELEASE
Column Name: ATTRIBUTE1
Event Type: CUSTOM
Business Object: Order
02. Agent
Agent ID: CUSTOM_EVENT_AGENT
Agent Type: ORDER RELEASE
Agent Event: CUSTOM_EVENT: INTERNAL or USER
03. Custom ORDER_RELEASE screen set/manager layout that is configured with an ATTRIBUTE1 field.
04. Order: ORDER_RELEASE
Edit the order > added value '1' in the 'ATTRIBUTE1' field > Finished.
NOTE: Agent ID (CUSTOM_EVENT_AGENT) got trigger.
05. Agent (created to update the Order Attribute1)
Agent ID: AGENT_Update_ATTRIBUTE1
Agent Type: ORDER RELEASE
Agent Event: ORDER - MODIFIED: INTERNAL or USER
Agent Action: DIRECT SQL UPDATE
UPDATE ORDER_RELEASE ORE SET ORE.ATTRIBUTE1='RELEASE' WHERE
ORDER_RELEASE_GID=$GID
06. Modify anything on the order.
NOTE: The Order's Attrubute1 is updated successfully.
NOTE: That did not trigger Agent ID: CUSTOM_EVENT_AGENT.
-------------
01. Custom Event:
Agent Event ID: CUSTOM_EVENT
Data Query Type: ORDER RELEASE
Contact Notification ID: ORDER - MODIFIED
Modification Event: Y
User-defined Event: Y
Agent Event Table Mappings
Table Name: ORDER_RELEASE
Column Name: ATTRIBUTE1
Event Type: CUSTOM
Business Object: Order
02. Agent
Agent ID: CUSTOM_EVENT_AGENT
Agent Type: ORDER RELEASE
Agent Event: CUSTOM_EVENT: INTERNAL or USER
03. Custom ORDER_RELEASE screen set/manager layout that is configured with an ATTRIBUTE1 field.
04. Order: ORDER_RELEASE
Edit the order > added value '1' in the 'ATTRIBUTE1' field > Finished.
NOTE: Agent ID (CUSTOM_EVENT_AGENT) got trigger.
05. Agent (created to update the Order Attribute1)
Agent ID: AGENT_Update_ATTRIBUTE1
Agent Type: ORDER RELEASE
Agent Event: ORDER - MODIFIED: INTERNAL or USER
Agent Action: DIRECT SQL UPDATE
UPDATE ORDER_RELEASE ORE SET ORE.ATTRIBUTE1='RELEASE' WHERE
ORDER_RELEASE_GID=$GID
06. Modify anything on the order.
NOTE: The Order's Attrubute1 is updated successfully.
NOTE: That did not trigger Agent ID: CUSTOM_EVENT_AGENT.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |