Daybreak¶
Aunalytics is excited to announce the May 2021 Daybreak release to our clients. This release will provide clients with model and site enhancement information along with any fixes to existing functionality we have included.
Context Selector¶
Users of Daybreak have always been able to access more than one Daybreak datamart through the use of separate solution URLs communicated to clients. This month, a change to the login screen user experience now allows all users to access Daybreak through a single URL and select the Daybreak datamarts they would like to access from a context selector screen displayed after successfully authenticating with the platform.
Context selection enhances the Daybreak login experience and simplifies the way clients access Daybreak from a single, memorable URL. Moreover, context selection enables users who subscribe to more than one Daybreak instance to easily switch between instances without navigating to a separate site and authenticating again.
Natural Language Answers Model Updates¶
In April, Aunalytics released Daybreak™ Natural Language Answers, a natural language processing model that generates structured queries from questions in natural language. This model is developed by Aunalytics’ Innovation Lab and is updated to support changes to the underlying data model used to power our Daybreak datamarts. This month, Innovation Lab will release a new model version trained to better recognize answers that involve external relationship fields—Smart Features™ generated by reading through a customer’s transaction data to detect financial products they may have with external entities (other financial institutions, auto dealerships, etc.) After release, Natural Language Answers will be able to understand questions about customers with external relationships by answering questions like:
- “Give me a list of customers who have an external mortgage and don’t have a HELOC.”
- “Show customers who have external brokerage accounts”
- “Customers born between 1950 – 1955"
- “Customers who are millennials with active checking accounts”
- “Number of accounts created in the last year”
These natural language phrases are supported by retraining the model with data to support the following fields:
Customer_HasExternalCarLeaseCustomer_HasExternalCarPaymentCustomer_HasExternalCreditCardCustomer_HasExternalDealerPaymentCustomer_HasExternalInvestmentCustomer_HasExternalMerchantProcessingCustomer_HasExternalMortgageCustomer_DateofBirthCustomer_Generation
Additionally, the model also understands “create” to be synonymous with “opened” in the context of financial institution accounts.
Daybreak™ for Financial Services Version 2.2 Patch¶
This month Daybreak for Financial Services users on version 2 of the data model will receive a patch update with several minor changes. Clients should be aware, however, that some user impact should be expected, particularly for Tableau users.
One change with no negative impact are that certain fields now support negative integer values:
Lend_AmountPastDueLend_BookBalanceLend_FASBCostLend_NetDeferredFees
This change should not negatively impact users, but will enhance the analytical value of these fields.
One change with possible impact to users is that the data type of Lend_ParticipationStatus has been changed from integer to string.
Tableau users using this field in dashboards have likely used casting operations to display this field's values correctly. However, now that the underlying data type has changed, those casting operations will cause an error in the dashboard that can easily be resolved by simply removing the casting operation and treating the field as a string.
Finally, two spelling errors in the names of fields have been corrected:
Lend_CurrentAmoritizationPeriodcorrected toLend_CurrentAmortizationPeriodLend_LeinPositioncorrected toLend_LienPosition
While this correction should not confuse users, clients should be made aware that may impact field references in Tableau dashboards. Any dashboards referencing these fields will need to be updated to use the corrected field names.
Aunsight™ Golden Record¶
Aunalytics is excited to announce also the May 2021 Aunsight Golden Record data integration platform release to our clients. This release will provide users with enhancements, new features, as well as any fixes to existing functionality we have included.
Agent Notifications¶
Last month AuGR introduced a new notifications framework to enable better communication with system operators. This month, AuGR agent notifications have been released, enabling system operators to receive email notifications when there are failures with an AuGR agent deployment.
AuGR agent notifications will enable those who support AuGR agents to monitor the health of these deployments and take action should there be a failure.
<<<<<<< HEAD
Destination Timing Options for Transactional Workflows¶
Earlier this year, Aunalytics released transactional workflows (TXWF) for the AuGR data integration platform. Transactional workflows are managed workloads that intermittently query a data source from the cloud to see if data on the source has changed, and to request that new data in order maintain data in sync across a connection. TXWFs normally waits a small amount of time for the source system's to report itself in an idle state (idle time sync) before it initiates a transfer of new data. The purpose of this idle time waiting period is to allow the source system to commit all changes to its journal before syncing.
However, to better accommodate source systems that may experience long periods of active change without falling out of sync, TXWFs now support a max sync interval setting that defines the maximum amount of time AuGR will wait for the source system to go idle before it requests a transfer of new data. Max time sync therefore represents the maximum amount of time AuGR will wait before requesting new data, even if the data source is still processing new changes to the data. This enables data pipeline creators to better anticipate how much time could pass between syncs and decrease the tendency for high-load systems to remain out of sync with AuGR for long periods of time during periods of high-load.¶
Release Contents¶
| Issue ID | Description |
|---|---|
| ILT-136 | Replace error message for erroneous input |
| DATAINT-547 | Disable operator from setting feature flags. |
| DATAINT-546 | API Request - Add option to trigger input job reads |
| DATAINT-535 | Add paging component to Pending/Failed WB queues |
| DATAINT-523 | Support CIFI 3.0 Change log Format |
| DATAINT-513 | AuGR Microservice Consolidation: Merge Dataflow into Nucleus |
| DATAINT-498 | Short-circuit read if bad record ratio is too high |
| DATAINT-487 | Update UI to validate schemas in draft if connection settings is changed |
| DATAINT-447 | Text Area version storage |
| AUN-14980 | Martin's UI changes |
| AUN-14928 | Getting rid of 'is not a recognized counter' logs in dataflows |
| AUN-14914 | Datamarts: Load from DSV |
| AUN-14892 | Add pagination for Exasol in Daybreak v2 |
| AUN-14779 | Add a system info page to webapps that show library versions |
| AUN-14734 | Show Org/Workflow Names in Workflow Notification Emails |
| AUN-14733 | Workflow: "validate_schema" option in copy |
| AUN-14715 | add EAI_AGAIN to the list of connection retries |
| AUN-14649 | Add whitelist of cases where workflow retries immediately fail |
| AUN-14647 | "validate_schema" option for Copy |
| AUN-14435 | Remove the gl2_message_id key from logs |
| AUN-14415 | Create "load datamart" workflow component |
| AUN-14406 | Update UI to accept batched queries |
| AUN-14402 | Update query service to use lib-query v2 |
| AUN-14307 | Metric service failure handling |
Bug Fixes¶
| Issue ID | Description |
|---|---|
| DATAINT-554 | mdm notifications not working for tep |
| DATAINT-550 | Dataflow Statistics API is returning 0 for the current month when it should have data. |
| DATAINT-548 | Hide lookup shapes in Monitor UI |
| DATAINT-541 | Test Exact Match on Hashed Property |
| DATAINT-538 | Matching breaks on data type 'Decimal' |
| DATAINT-526 | UI Session Expiration not being enforced |
| DATAINT-505 | Matching failure not apparent in UI |
| DATAINT-503 | Do not auto-discover on Input edit |
| DATAINT-495 | Auto-provisioning should set the UI host suffix specific to the cluster. |
| DATAINT-494 | UI logging doesn't seem to be logging errors to Graylog |
| DATAINT-491 | Update charts with correct logging variables |
| DATAINT-152 | Scheduled Read Jobs getting stuck / not running correctly |
| AUN-14953 | Workflow Trace Info - Child job links in WF jobs can be overwhelming |
| AUN-14931 | Notifications count fetch even when user is logged out |
| AUN-14918 | Difference between row count shown in the data results page and an Insights summary card for number of records |
| AUN-14802 | While editing details of a fixture, hitting enter refreshes the page and loses changes |
| AUN-14756 | Unable to run stored queries through lib_aunsight_py |
| AUN-14714 | Workflow Builder disabled components should disable required fields |
| AUN-14426 | GraphQL WF References should point to specific job types not TrackerJob |
| AUN-14276 | Formations Updating Roles is not working as expected. |
| >>>>>>> 1887fff... last minute release note changes to add screencap and remove TXWF timing |