<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aura – </title>
    <link>/docs/aura-releases/youngblood/changelog/</link>
    <description>Recent content on Aura</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
	  <atom:link href="/docs/aura-releases/youngblood/changelog/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-system-components-version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-system-components-version/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-system-components-versions&#34;&gt;Aura system components versions&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Updated versions of Aura system components for the current Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;components-versions&#34;&gt;Components versions&lt;/h2&gt;
&lt;p&gt;All components in the table below run over &lt;strong&gt;AKS cluster version 1.26.&lt;/strong&gt;&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;th&gt;Namespace&lt;/th&gt;
&lt;th&gt;Image deployed&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;alertmanager&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/alertmanager:v0.23.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;elastic-operator&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;docker.elastic.co/eck/eck-operator:2.7.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;elasticsearch-es-aura&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/elasticsearch:8.7.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;elasticsearch-exporter&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/elasticsearch_exporter:v1.5.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;fluent-bit-aggregator&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/fluent-bit:1.7.7&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;grafana&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/grafana:8.5.21&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;kibana-kb&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;docker.elastic.co/kibana/kibana:8.7.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;prometheus&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/prom/prometheus:v2.32.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;mongodb&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/mongo:4.4.18&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;mongodb-atlas-operator&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/mongodb-atlas-kubernetes-operator:1.5.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;redis-exporter&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/redis-exporter:1.6.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;redis&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/redis:6.0.19&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;thanos-store-gateway&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/thanos:v0.24.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;atlas-logger&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/atlas-logger:1.0.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;azure-logger&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/azure-logger:1.3.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;pushgateway&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/pushgateway:v1.4.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;thanos-querier&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/thanos:v0.24.0&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id=&#34;additional-information&#34;&gt;Additional information&lt;/h2&gt;
&lt;p&gt;Information regarding Aura system components end-of-life (EOL) and next updates is included in the document &lt;em&gt;&lt;strong&gt;Scheduled updates in Aura components&lt;/strong&gt;&lt;/em&gt;. Find it in the &lt;a href=&#34;../../../../docs/aura-releases/&#34;&gt;Aura releases&lt;/a&gt; section
of your corresponding release.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-authentication-api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-authentication-api/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-authentication-api-changelog&#34;&gt;Aura Authentication API changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Authentication API component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-02---update-aura-authentication-docker-image-to-the-latest-node-18-version&#34;&gt;2023-11-02 - Update Aura Authentication docker image to the latest node 18 version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Update to &lt;a href=&#34;https://nodejs.org/en/blog/release/v18.18.2&#34;&gt;nodejs 18.18.2 version&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-authentication-api&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;aura-tac-api&lt;/strong&gt;&lt;/em&gt; docker images.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-13---status-that-are-not-http-status-codes-should-not-logged-as-status&#34;&gt;2023-11-13 - Status that are not HTTP status codes should not logged as status&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Elastic parsers are configured to handle and index the &lt;code&gt;status&lt;/code&gt; field of logs, but it only works properly if &lt;code&gt;status&lt;/code&gt; is an integer value or if it is a string parseable to integer. As we were logging some &lt;code&gt;status&lt;/code&gt; that were not integer values, Elastic parsing was broken.&lt;/li&gt;
&lt;li&gt;In &lt;a href=&#34;../../../../docs/components/aura-authentication-api/api-definition/terms-and-conditions-api/&#34;&gt;&lt;em&gt;&lt;strong&gt;Terms and Conditions API&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;, within &lt;code&gt;service&lt;/code&gt;, we are logging the status of the consent in the database, that is a string not parseable to integer, as &lt;code&gt;status&lt;/code&gt; has been changed to &lt;code&gt;tac.status&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---use-correct-drt-value-in-logs&#34;&gt;2023-11-13 - Use correct drt value in logs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The field &lt;code&gt;drt&lt;/code&gt; should be an integer value containing the number of milliseconds that the request took to be processed, but in some cases it was a float value.&lt;/li&gt;
&lt;li&gt;This fix ensures that the &lt;code&gt;drt&lt;/code&gt; field is always an integer value.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-bot/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-bot/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-bot-changelog&#34;&gt;Aura bot changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Bot component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-02---update-aura-bot-docker-image-to-the-latest-node-18-version&#34;&gt;2023-11-02 - Update Aura Bot docker image to the latest node 18 version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Update to &lt;a href=&#34;https://nodejs.org/en/blog/release/v18.18.2&#34;&gt;nodejs 18.18.2 version&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-bot&lt;/strong&gt;&lt;/em&gt;, &lt;em&gt;&lt;strong&gt;aura-mini-bot&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;aura-configuration-updater&lt;/strong&gt;&lt;/em&gt; docker images.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-13---fix-correlator-value-in-several-aura-bot-logs&#34;&gt;2023-11-13 - Fix correlator value in several &lt;em&gt;&lt;strong&gt;aura-bot&lt;/strong&gt;&lt;/em&gt; logs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;aura-storage-file-manager&lt;/code&gt; now uses &lt;code&gt;aura-system&lt;/code&gt; as correlator value in the logs.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;aura-session-manager&lt;/code&gt; now uses the correlator of the request in the logs.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;channel-data-utils&lt;/code&gt; now uses the correlator of the request in the logs.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;aura-cache-management&lt;/code&gt; now uses the correlator of the request in the logs.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;aura-authentication&lt;/code&gt; now uses the correlator of the request in the logs.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;aura-cache-management&lt;/code&gt; now uses the correlator of the request in the logs.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---remove-by-default-settings-of-aura-bot-common-library&#34;&gt;2023-11-13 - Remove by default settings of &lt;em&gt;&lt;strong&gt;aura-bot-common-library&lt;/strong&gt;&lt;/em&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;By default, &lt;code&gt;dialog-config.json&lt;/code&gt; file assured that all smalltalk intents were available in all channels, unless a different configuration was specified in the &lt;code&gt;dialog-config&lt;/code&gt; file specific for a country.&lt;/li&gt;
&lt;li&gt;Currently, this default behavior is no longer needed, so the default configuration has been removed from &lt;em&gt;&lt;strong&gt;aura-bot-common-library&lt;/strong&gt;&lt;/em&gt;. Now, if a country does not specify a configuration for smalltalk intents, they will not be available in the channels.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---status-that-are-not-http-status-codes-should-not-logged-as-status&#34;&gt;2023-11-13 - Status that are not HTTP status codes should not logged as status&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Elastic parsers are configured to handle and index the &lt;code&gt;status&lt;/code&gt; field of logs, but it only works properly if &lt;code&gt;status&lt;/code&gt; is an integer value or if it is a string parseable to integer. As we were logging some &lt;code&gt;status&lt;/code&gt; that were not integer values, Elastic parsing was broken.&lt;/li&gt;
&lt;li&gt;In &lt;code&gt;channel-data-utils&lt;/code&gt; we are logging the status of the response, that is an object, as &lt;code&gt;status&lt;/code&gt; has been changed to &lt;code&gt;activityStatus&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---aura-bot-was-blocked-for-a-long-time-when-aura-bot-mocks-library-configuration-was-refreshed&#34;&gt;2023-11-13 - &lt;em&gt;&lt;strong&gt;Aura Bot&lt;/strong&gt;&lt;/em&gt; was blocked for a long time when &lt;em&gt;&lt;strong&gt;aura-bot-mocks-library&lt;/strong&gt;&lt;/em&gt; configuration was refreshed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;aura-bot-mocks-library&lt;/strong&gt;&lt;/em&gt; configuration is stored in &lt;strong&gt;Azure Storage&lt;/strong&gt; and was downloaded every 2 minutes to assure that the mock dialog sent the right answer.&lt;/li&gt;
&lt;li&gt;As the files are quite big, the download process could take a long time, and during that time, the bot was blocked and could not answer any request. Moreover, some of the requests being processed were stuck and not answered until the download process had finished.&lt;/li&gt;
&lt;li&gt;Besides, the responses of the mock are never changed, so the download process is not needed. We have changed the default configuration to once a day to avoid the download process and the bot blocking.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---iscached-field-has-now-a-correct-value-for-anonymous-users-in-aura-bot-kpi-user-entity-files&#34;&gt;2023-11-13 - &lt;code&gt;isCached&lt;/code&gt; field has now a correct value for anonymous users in &lt;em&gt;&lt;strong&gt;Aura Bot&lt;/strong&gt;&lt;/em&gt; KPI USER entity files&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;isCached&lt;/code&gt; field is used to know if the information of a user has been read from the users&amp;rsquo; cache or not. But for anonymous users, the value of this field was always &lt;code&gt;false&lt;/code&gt;, even if the user was cached.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---avoid-skipping-tc-for-recently-logged-users&#34;&gt;2023-11-13 - Avoid skipping T&amp;amp;C for recently logged users&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;With shared caches for anonymous and authenticated users, in some cases T&amp;amp;C could be skipped in recently authenticated users.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-bridge/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-bridge/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-bridge-changelog&#34;&gt;Aura bridge changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura bridge component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-02---update-aura-bridge-docker-image-to-the-latest-node-18-version&#34;&gt;2023-11-02 - Update Aura Bridge docker image to the latest node 18 version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Update to &lt;a href=&#34;https://nodejs.org/en/blog/release/v18.18.2&#34;&gt;nodejs 18.18.2 version&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;aura-bridge-outbound&lt;/strong&gt;&lt;/em&gt; docker images.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-16---updated-environment-variables-information&#34;&gt;2023-11-16 - Updated environment variables information&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new column is added in &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; environment variables documentation to mark if the value of each variable in the &lt;code&gt;config-map&lt;/code&gt; of the inbound and outbound &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; must be the same or not, taking into account that they both work together and require a consistent configuration.&lt;/li&gt;
&lt;li&gt;Remember that the inbound and outbound &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; are the very same component, but they are deployed separately. In the deployment &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; handles the requests coming to Aura and &lt;em&gt;&lt;strong&gt;aura-bridge-outbound&lt;/strong&gt;&lt;/em&gt; handles the responses produced by Aura.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/bridge-components/aura-bridge-outbound/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-bridge-outbound&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/environment-variables/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; environment variables&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-07---unify-the-conversationid-regardless-of-the-phone-number-format-in-br&#34;&gt;2023-11-07 - Unify the conversationId regardless of the phone number format in BR&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; now unifies the conversationId regardless of the phone number format in BR. This change applied to the &lt;em&gt;&lt;strong&gt;aurapush-incoming-processor&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;whatsapp-incoming-processor&lt;/strong&gt;&lt;/em&gt; plugins. Both plugins now use the &lt;strong&gt;getUnifiedConversationId&lt;/strong&gt; method to obtain the conversationId.&lt;/li&gt;
&lt;li&gt;New environment variables &lt;em&gt;&lt;strong&gt;AURA_PHONE_COUNTRY_CODE_NU&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;AURA_WHATSAPP_BR_UNIFIED_CONVID&lt;/strong&gt;&lt;/em&gt; are added to &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/environment-variables/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; environment variables&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/bridge-components/plugins/whatsapp-service-plugin&#34;&gt;&lt;em&gt;&lt;strong&gt;whatsapp-service&lt;/strong&gt;&lt;/em&gt; plugin&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-13---sibling-messages-are-no-longer-sent-when-a-non-retriable-error-is-received&#34;&gt;2023-11-13 - Sibling messages are no longer sent when a non-retriable error is received&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Until this fix, when a non-retriable error was received, the sibling messages were sent to the user, although a previous message within the response had already failed.&lt;/li&gt;
&lt;li&gt;Now, when a non-retriable error is received, the sibling messages are not sent to the user, as was specified for &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---fix-extra-delay-when-multiple-bubbles-are-returned&#34;&gt;2023-11-13 - Fix extra delay when multiple bubbles are returned&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Until this fix, when multiple bubbles were returned within a response, an extra delay was added between each bubble.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---status-that-are-not-http-status-codes-should-not-logged-as-status&#34;&gt;2023-11-13 - Status that are not HTTP status codes should not logged as status&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Elastic parsers are configured to handle and index the &lt;code&gt;status&lt;/code&gt; field of logs, but it only works properly if &lt;code&gt;status&lt;/code&gt; is an integer value or if it is a string parseable to integer. As we were logging some &lt;code&gt;status&lt;/code&gt; that were not integer values, Elastic parsing was broken.&lt;/li&gt;
&lt;li&gt;In &lt;code&gt;message-sync-manager-redis&lt;/code&gt; we are logging the status of the message in the queue, that is a string not parseable to integer, as &lt;code&gt;status&lt;/code&gt; has been changed to &lt;code&gt;messageStatus&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---avoid-delay-in-the-delivery-of-the-messages-when-the-communication-between-aura-bridge-and-aura-groot-fails&#34;&gt;2023-11-13 - Avoid delay in the delivery of the messages when the communication between &lt;em&gt;&lt;strong&gt;Aura Bridge&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;Aura Groot&lt;/strong&gt;&lt;/em&gt; fails&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The common system of handling the flows within &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt;, &lt;code&gt;aura-bridge-flow&lt;/code&gt;, has been changed so the system is now able to register the information of each message when it is needed and to remove it in the happening of a non-recoverable error.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---do-not-return-options-list-header-when-the-uc-returns-a-message-without-text&#34;&gt;2023-11-13 - Do not return options list header when the UC returns a message without text&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Until this fix the options title was being added if any option existed, although those titles were empty.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;directline-to-whatsapp-converter&lt;/code&gt; has been updated so the title is only added if there is information of any of the options, so the titles are not empty.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-13---avoid-duplicates-in-error-messages-after-receiving-a-retrievable-error&#34;&gt;2023-11-13 - Avoid duplicates in error messages after receiving a retrievable error&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Until this fix after receiving a retrievable error several times, the error message was being duplicated.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-10-31---avoid-duplicates-in-outgoing-messages-tequila-801&#34;&gt;2023-10-31 - Avoid duplicates in outgoing messages (Tequila 8.0.1.)&lt;/h3&gt;
&lt;p&gt;Modified the execution of &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; queues to avoid duplicating output messages.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-channels/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-channels/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-channels-changelog&#34;&gt;Aura Channels changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Channels component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-07---updated-aura-channel-model-documentation&#34;&gt;2023-11-07 - Updated Aura channel model documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Aura channel model documentation has been completed, with the addition of key information:
&lt;ul&gt;
&lt;li&gt;Update of specific parameters and values&lt;/li&gt;
&lt;li&gt;Information related to requirements for the registration of a channel in Aura in two different scenarios:
&lt;ul&gt;
&lt;li&gt;Registration of a channel that will work against &lt;em&gt;&lt;strong&gt;aura-bot&lt;/strong&gt;&lt;/em&gt; &lt;strong&gt;skill&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Registration of a channel that will work against a &lt;strong&gt;third-party skill&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;New column indicating which are the Aura Platform components affected by a specific property.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/channels/current-channel-model&#34;&gt;Aura channel model&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-13---review-textconvert-setting-in-the-channels-configuration&#34;&gt;2023-11-13 - Review &lt;code&gt;textConvert&lt;/code&gt; setting in the channels configuration&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;In U2 release, &lt;code&gt;textConvert&lt;/code&gt; option was moved from WhatsApp settings to &lt;code&gt;responseOptions&lt;/code&gt; but Brazil local channels were not updated. With this fix, channels are created with the correct configuration.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/channels/current-channel-model/&#34;&gt;Current channel configuration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-configuration-api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-configuration-api/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-configuration-api-changelog&#34;&gt;Aura Configuration API changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Configuration API component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-02---update-aura-configuration-api-docker-image-to-the-latest-node-18-version&#34;&gt;2023-11-02 - Update Aura Configuration API docker image to the latest node 18 version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Update to &lt;a href=&#34;https://nodejs.org/en/blog/release/v18.18.2&#34;&gt;nodejs 18.18.2 version&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-configuration-api&lt;/strong&gt;&lt;/em&gt; docker image.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: Aura deployment changelog</title>
      <link>/docs/aura-releases/youngblood/changelog/aura-deployment/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-deployment/</guid>
      <description>
        
        
        &lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2023-10-07---new-obs-specific-configuration-section&#34;&gt;2023-10-07 - New OBs specific configuration section&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added a new section with specific configurations for OBs.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/deployment/installer/#obconfigurations&#34;&gt;Installer aurak8s: Specific OB configuration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-10-07---added-aurapush-sendfeedback-service-configuration-variables-for-br&#34;&gt;2023-10-07 - Added &lt;em&gt;&lt;strong&gt;aurapush-sendfeedback-service&lt;/strong&gt;&lt;/em&gt; configuration variables for BR&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added configuration variables for &lt;em&gt;&lt;strong&gt;aurapush-sendfeedback-service&lt;/strong&gt;&lt;/em&gt; endpoint and subscription key.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/deployment/installer/#aurapushfeedback&#34;&gt;Installer aurak8s: Configure &lt;em&gt;&lt;strong&gt;aurapush-sendfeedback-service&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-file-manager/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-file-manager/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-file-manager-changelog&#34;&gt;Aura File Manager changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura File Manager component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-02---update-aura-file-manager-docker-image-to-the-latest-node-18-version&#34;&gt;2023-11-02 - Update Aura File Manager docker image to the latest node 18 version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Update to &lt;a href=&#34;https://nodejs.org/en/blog/release/v18.18.2&#34;&gt;nodejs 18.18.2 version&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-file-manager&lt;/strong&gt;&lt;/em&gt; docker image.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-13---review-aura-file-manager-indexes&#34;&gt;2023-11-13 - Review Aura File Manager indexes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Included all the needed indexes in the database to improve performance.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-gateway-api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-gateway-api/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-gateway-api-service-changelog&#34;&gt;Aura Gateway API service changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Gateway API service for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2023-10-27---aura-gateway-api-service&#34;&gt;2023-10-27 - Aura Gateway API service&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;New component in Aura: &lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; service, composed by several plugins. This component receives a request from a channel or a external service, validates it and, in upcoming releases, will be able to send the request to &lt;strong&gt;OpenAI&lt;/strong&gt; for the autogeneration of answers.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-gateway-api/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; service description&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-gateway-api/environment-variables/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; service environment variables&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-gateway-api/api-definition/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; service APIs&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-02---guidelines-for-working-with-aura-gateway-api-service&#34;&gt;2023-11-02 - Guidelines for working with Aura Gateway API service&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Guidelines including the process for accessing &lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; service and working with it. In the current Aura Platform release, YoungBlood, the implementation is mocked, only intended for basic integration purposes.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/operations/install-configure/gateway-api/&#34;&gt;Guidelines for accessing &lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-groot/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-groot/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-groot-changelog&#34;&gt;Aura groot changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura groot component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-02---update-aura-groot-docker-image-to-the-latest-node-18-version&#34;&gt;2023-11-02 - Update Aura Groot docker image to the latest node 18 version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Update to &lt;a href=&#34;https://nodejs.org/en/blog/release/v18.18.2&#34;&gt;nodejs 18.18.2 version&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-groot&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;aura-mini-groot&lt;/strong&gt;&lt;/em&gt; docker images.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-13---aura-groot-is-now-able-to-handle-requests-from-microsoft-facebook-adapter&#34;&gt;2023-11-13 - &lt;em&gt;&lt;strong&gt;Aura Groot&lt;/strong&gt;&lt;/em&gt; is now able to handle requests from Microsoft Facebook adapter&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;Aura Groot&lt;/strong&gt;&lt;/em&gt; is now able to get the channel from the field &lt;code&gt;activity.channel&lt;/code&gt;, that is set to &lt;code&gt;facebook&lt;/code&gt; by the Microsoft Facebook adapter.&lt;/li&gt;
&lt;li&gt;The limitation with this solution is that it can only handle a single &lt;code&gt;facebook&lt;/code&gt; channel per &lt;em&gt;&lt;strong&gt;aura-groot&lt;/strong&gt;&lt;/em&gt; instance. To be able to handle more, it should take into account the information regarding the specific Facebook page that is sent in the request.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-kpis/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-kpis/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-kpis-changelog&#34;&gt;Aura KPIs changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura KPIs component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-07---add-timezone-indication-in-the-kpis-entities&#34;&gt;2023-11-07 - Add timezone indication in the KPIs entities&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Modified the definition of all &lt;em&gt;&lt;strong&gt;aura-kpis-entities&lt;/strong&gt;&lt;/em&gt; to include the UTC timezone of date-related fields.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/api-request/&#34;&gt;&lt;em&gt;&lt;strong&gt;API request&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/dimensions/&#34;&gt;&lt;em&gt;&lt;strong&gt;Dimensions&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/extended-message&#34;&gt;&lt;em&gt;&lt;strong&gt;Extended Message&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/groot-message&#34;&gt;&lt;em&gt;&lt;strong&gt;Groot Message&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/message&#34;&gt;&lt;em&gt;&lt;strong&gt;Message&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/recognizer&#34;&gt;&lt;em&gt;&lt;strong&gt;Recognizer&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/suggestion&#34;&gt;&lt;em&gt;&lt;strong&gt;Suggestion&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/kpi-entities/aura-entities-definition/user&#34;&gt;&lt;em&gt;&lt;strong&gt;User&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-kpis-uploader/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-kpis-uploader/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-kpis-uploader-changelog&#34;&gt;Aura KPIs Uploader changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura KPIs Uploader component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-02---update-aura-kpis-uploader-docker-image-to-the-latest-node-18-version&#34;&gt;2023-11-02 - Update Aura KPIs Uploader docker image to the latest node 18 version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Update to &lt;a href=&#34;https://nodejs.org/en/blog/release/v18.18.2&#34;&gt;nodejs 18.18.2 version&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-kpis-uploader&lt;/strong&gt;&lt;/em&gt; docker image.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-nlp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-nlp/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-nlp-changelog&#34;&gt;Aura NLP changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura NLP component for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2023-10-23---new-normalization-stage-wrappers&#34;&gt;2023-10-23 - New normalization stage wrappers&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added a new normalization stage wrapper that identifies stop words from a customized database: &amp;ldquo;StopWordsFromFileNormalizerWrapper&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Added a new normalization stage wrapper that exchanges words in an utterance: &amp;ldquo;WordReplacerFromFileNormalizerWrapper&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Affected Documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-stages/nlp-normalizers/#stop-words-from-file&#34;&gt;Stop words from file&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-stages/nlp-normalizers/#word-replacer-from-file&#34;&gt;Word replacer from file&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-10-23---new-normalization-pipelines&#34;&gt;2023-10-23 - New normalization pipelines&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added two new normalization pipelines &amp;ldquo;Niseko&amp;rdquo; and &amp;ldquo;Norikura&amp;rdquo;, that integrate the above-mentioned normalization stages.&lt;/li&gt;
&lt;li&gt;Affected Documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-normalization-pipelines/niseko/&#34;&gt;Niseko normalization pipeline&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-normalization-pipelines/norikura/&#34;&gt;Norikura normalization pipeline&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2023-10-23---improved-stop-words-normalizer-internal-behavior&#34;&gt;2023-10-23 - Improved stop words normalizer internal behavior&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Fix in the internal behavior of the &lt;strong&gt;stop words normalizer&lt;/strong&gt; to solve potential problems in the recognition of entities. Internally, the recognizer is now able to work with phrase variations without normalizing them in order to preserve certain information that is useful for the recognition process.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-10-23---improved-gazetteer-ner-internal-behavior-with-annotated-entities&#34;&gt;2023-10-23 - Improved Gazetteer NER internal behavior with annotated entities&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Fix in the internal management of annotated entities by the &lt;strong&gt;Gazetteer NER recognition stage&lt;/strong&gt; when working with phrases with more than one entity to ensure that the annotation process is made in the right order, thus avoiding collisions between different annotations.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-10---refactor-of-aura-nlp-swagger&#34;&gt;2023-11-10 - Refactor of Aura NLP swagger&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Refactor of the &lt;em&gt;&lt;strong&gt;aura-nlp&lt;/strong&gt;&lt;/em&gt; swagger&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-nlp/api-definition/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-nlp&lt;/strong&gt;&lt;/em&gt; API swagger&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-utilities/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-utilities/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-utilities-changelog&#34;&gt;Aura utilities changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura utilities for Youngblood Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-15---aura-redis-handler-utility&#34;&gt;2023-11-15 - aura-redis-handler utility&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Certain changes over &lt;em&gt;&lt;strong&gt;aura-redis-handler&lt;/strong&gt;&lt;/em&gt; utility related to its methods are documented.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/operations/develop-features/aura-utilities/aura-redis-handler/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-redis-handler&lt;/strong&gt;&lt;/em&gt; utility&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/youngblood/changelog/aura-documentation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/youngblood/changelog/aura-documentation/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-documentation-changelog&#34;&gt;Aura documentation changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Documentation for Youngblood Aura Platform release.&lt;/p&gt;
&lt;p&gt;The current section:&lt;/p&gt;
&lt;p&gt;&amp;#x2705; Includes changes that exclusively affect to the &lt;strong&gt;improvement of Aura documentation&lt;/strong&gt; (writing style, structure, format, fixing typos, etc.)&lt;/p&gt;
&lt;p&gt;&amp;#x26d4;  Does not include &lt;strong&gt;technical corrections&lt;/strong&gt; in documents or modifications derived from &lt;strong&gt;changes over a specific Aura component&lt;/strong&gt;. These ones will be included in their corresponding section within the release changelog.&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;updated&#34;&gt;Updated&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-13---updated-aura-logging-utility-documentation&#34;&gt;2023-11-13 - Updated aura-logging utility documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;em&gt;&lt;strong&gt;aura-logging&lt;/strong&gt;&lt;/em&gt; utility documentation has been updated to include the correct format of the logs and remove deprecated and incorrect information.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/operations/develop-features/aura-utilities/aura-logging-utility/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-logging&lt;/strong&gt;&lt;/em&gt; utility&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2023-11-14---update-of-hugo-and-docsy-versions-and-website-improvements&#34;&gt;2023-11-14 - Update of Hugo and Docsy versions and website improvements&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Hugo&lt;/strong&gt;, the website framework upon which Aura technical documentation website is built, has been updated to 0.120.4 version.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Docsy&lt;/strong&gt;, the prefigured Hugo&amp;rsquo;s theme used as template for Aura documentation has been updated to 0.7.1 version.&lt;/li&gt;
&lt;li&gt;Moreover, consistent with this update, certain optimization tasks have been implemented to enhance the usability of the website and improve the overall users&amp;rsquo; experience:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;New section menu&lt;/strong&gt;
A drop-down section menu is enabled, which is initially folded until the user clicks the arrow to the right of a specific section. This feature makes easier to identify the document hierarchy and to determine if a specific document contains sub-documents or not.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Print Tool&lt;/strong&gt;
The behavior of the tool that allows printing entire sections of the documentation has been corrected and optimized. Now you can generate a document, together with its child pages and sections, in a format suited to printing, with a complete table of contents for the section.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Corporate image&lt;/strong&gt;
Aura technical documentation website style, images and colors are updated to use corporate ones.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-01---adaptation-of-contents-to-aura-distributed-architecture&#34;&gt;2023-11-01 - Adaptation of contents to Aura distributed architecture&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Documentation of key Aura components have been updated to include modifications related to the introduction of the new distributed architecture in Aura. Basically, references to &lt;em&gt;&lt;strong&gt;aura-groot&lt;/strong&gt;&lt;/em&gt; and components&amp;rsquo; flowcharts have been modified. This task will continue in the following Aura Platform release until all the components documentation is updated.&lt;/li&gt;
&lt;li&gt;Affected documents:&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-07---new-location-for-the-documentation-related-to-aura-request-response-model&#34;&gt;2023-11-07 - New location for the documentation related to Aura request-response model&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;In Aura&amp;rsquo;s distributed architecture, the Aura request-response semantic model is used not only by channels but also by skills to communicate with &lt;em&gt;&lt;strong&gt;aura-root&lt;/strong&gt;&lt;/em&gt;. In this framework:
&lt;ul&gt;
&lt;li&gt;Documentation has been moved out from the channels section and included directly into the components/ section.&lt;/li&gt;
&lt;li&gt;Contents have been adapted to this new scenario, together with the addition of fields related to the communication with skills.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/request-response-model/&#34;&gt;Aura request-response semantic model&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2023-11-14---documents-fixes-and-corrections&#34;&gt;2023-11-14 - Documents fixes and corrections&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Throughout the website, different links, styles and typos have been corrected, for a continuous improvement of Aura Platform documentation.
Moreover, the README.md document, that contains detailed instructions for documentation makers and collaborators, has been completed.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
  </channel>
</rss>
