Fixed Defects
The following tables list the defects fixed in this release:
Fixed Defects in 26.1.0.IF02
| Issue ID | Description |
|---|---|
| HMA-419204 | On the pipeline canvas, new Reminders or Milestones saved from their configuration panel didn't appear in the Action node's block until you clicked Save as Draft. |
| HMA-419202 | You could save more than one Reminder or Milestone with the same name in a single Action-based Event pipeline. |
| HMA-419141 | Built-in enrichment functions, such as
get_last_five_activities and the
get_list_* functions, didn't work out of the
box. Their required functional parameter attributes weren't set up
by default. |
| HMA-419062 | An expression-based derived attribute that used a profile
attribute (for example, profile.age > 5) caused a
NullPointerException in the Detect Engine. The
engine skipped the attribute, even though the UI said the enrichment
was saved successfully. |
| HMA-419036 | On the Pipeline Report page for Action-based events, the Events Matched and Sent chart counted downstream events (Reminders, Milestones, Fulfillment) as well as primary triggers. This made the "Events Sent" count too high. |
| HMA-418909 | When a pipeline was submitted for approval, an error in a Time-based Reminder produced a message that called it a "Milestone reminder". |
| HMA-418798 | The Detect Engine hit a NullPointerException
while checking activity transitions for a deployed trigger, so
incoming transactions for that pipeline were dropped. |
| HMA-418028 | For Aggregated Attributes with the Minute unit,
Window Length was a free-text field. It didn't show how
values relate to the configured sub-hour minutes setting, which led
to setup mistakes. |
| HMA-417434 | When the session expired, the screen filled with repeated "Internal Server Error" messages, and the UI did not go to the login page until the browser was refreshed. |
| HMA-417432 | Opening a dropdown in the Detect UI sometimes took 2–3 seconds the first time in a session or after the UI had been idle. |
| HMA-417428 | After a pipeline was duplicated or its Feed Application was switched, some trigger condition rows sometimes showed tuple attributes from a different feed instead of the one currently selected. |
| HMA-417425 | Send for Approval failed with the error "Invalid profile attribute" when attributes from a secondary (non-Master) profile were selected in the pipeline destination. |
| HMA-417399 | Transaction processing failed with a
NullPointerException when a pipeline used
attributes from a secondary (non-Master) profile mapped in the
feed. |
| HMA-417297 | Derived attribute expressions that used list-type profile
attributes (for example, [profile.city,
profile.country]) failed to save with a parsing
error. |
| HMA-417296 | Retained tuple attributes used in a List(String)
expression failed type checking with the error "expected
'List(String)' type, but was of the 'unknown' type". |
| HMA-417247 | In the Contact Policy section, the tooltips for Total Triggers Limit and Per User Limit said "pipelines" where they should have said "events". |
| HMA-417214 | In Trigger Conditions, the operator dropdown stayed empty when a
list-type tuple attribute was selected
(List(String), List(Int),
List(Double), or List(Long)).
The condition could not be saved. |
| HMA-417136 | Deploying a pipeline failed with the error "Failed to generate backend expression" when the trigger feed's attributes were not mapped to a Profile and the pipeline used a Common / All-Inclusive Audience. |
| HMA-416809 | In Feed Mapping, adding an attribute beyond the page limit (the 11th row) put the new row on the next page while the view stayed on Page 1. Users had to go to the next page manually to fill in the new row. |
| HMA-416805 | The Detect Engine ignored the Key Attribute set in Feed
Mapping (for example, mobileNumber) and matched
transactions on the primary key (AUDIENCE_KEY)
instead. |
| HMA-416398 | When a pipeline had triggers from more than one feed, the destination payload included tuple attributes from the other feeds with empty values, instead of only the attributes from the feed that triggered the event. |
| HMA-416181 | After the Source Data Format of a DateTime attribute was changed
in Feed Mapping, processing incoming transactions caused a
NullPointerException in
TriggerEvaluatorFlow during batch
evaluation. |
| HMA-416178 | The Feed Engine failed to parse incoming date and time values
with a DateTimeParseException, even when they
matched the Source Data Format set in Feed Mapping (for example,
dd/MM/yyyy HH:mm:ss). The new format took
effect only after the Detect engine was restarted. |
| HMA-415409 | The Total Recharges label on the Dashboard page was cut off. |
Fixed Defects in 26.1.0.IF01
| Issue ID | Description |
|---|---|
| HMA-406192 | Now, profile attributes in a trigger configuration are working fine. |
| HMA-412300 | Client ID and Secret generated by the installer for the CLI tool and the Engine can be used directly. |
| HMA-410653 | On Dashboard charts, the Total Events Sent and Overall Trends data labels are displayed within the chart container when values reach the Y-axis maximum. |
| HMA-409273 | Now, duplicating pipeline will include all the configurations and settings from the source pipeline. |
| HMA-409200 | Changing the enrichment timing from preAggregation to postAggregation works fine. |
| HMA-412329 | In the pipeline configuration canvas, mindmap connector lines are aligned while you configure nested condition blocks. |
| HMA-412330 | Fixed the text on the Cancel button to display the full text on the Enrichment Configuration page. |
| HMA-412772 | Now you can disable the Feeds in the UI. |
| HMA-412907 | Now, the pipelines triggers when a list(bool)
transformed attribute is created as a retained enrichment attribute
along with lookup and derived attributes. |
| HMA-412984 | You can save an enrichment configuration that uses a
function-based derived attribute with
get_last_five_activities. |
Fixed Defects in 26.1.0
The following table lists the defects fixed in the 26.1.0 release:
| Issue ID | Description |
|---|---|
| HMA-392934 | The "Entitlement Consumed" column in the consumption tracking system now correctly updates to reflect the latest count when the MHS Pushed Detect Consumption Count process runs. |
| HMA-392543 | MaxAI now correctly transfers Insight information to the chat window after the user selects "Continue to Chat." |
| HMA-392378 | MaxAI now displays the correct Event Report time period start time in the Insights view. |
| HMA-392030 | The MaxAI pop-up screen now correctly displays the Event ID when viewing an event sent by that ID. |
| HMA-391993 | For the Dashboard and Report tabs, the MaxAI popup displays a warning message when a search yields an empty result set. |
| HMA-391963 | MaxAI pop-up screen now correctly displays the actual report count. |
| HMA-391892 | The Chatbot's conversation history is correctly cleared when new information is pulled from the MaxAI Insights pop-up window with the most relevant and current data. |