When was 4.3 released

Source: SAP. Feature catch up and deprecated features for Web Intelligence in Business Intelligence 4. Deprecated features that no longer exist in 4. These packages are available from see SAP Note: :. Source: SAP Note Note: You will need a new license key. The most notable addition to the Relational Data Sources :. Source: Maintenance Schedule. For last 5plus years many of my clients has been seeking out for enhanced visualization, since the competitor are beating their drum loud and hard.

Their is a great potential in 3-party extensions market when it comes to visualization but it has proven to be rough road to convince clients. Please keep in-mind that the install of BI 4. You will need to request new BI 4. Indeed, this is already mentioned in this blog.

Great article. I think it's also worth stating that the Upgrade Management Tool is deprecated too. So far, testing on the new Webi front end has gone well, although I can definitely see some areas that SAP could tweak to improve usability - Collapsing sections vertically would help for example. Thank you for the feedback, you are correct. I have added it to the list of Deprecated Features. Love the article and I agree with Mohd that BusinessObjects from a reporting perspective is an amazing product.

We just need SAP to realize this and to invest in the platform, cloud is one perspective but not the only one. It has not been updated yet unfortunately.

Feature catchup in later patches. Am I right in understanding, that in this release the mix of 32Bit and 64Bit modules known from release 4. I do confirm! You have read it here in this blog for sure.

And I bet elsewhere too! A silly thing is that when installing BI 4. Can someone tell if the "Cascading Prompts" feature made it into the 4. Open GL ES 3. This means detail and speed in games is now massively enhanced, and will see a greater level of photorealism and effects.

Other features include background Wi-FI locations meaning the connectivity can be used for location even when turned off and a new and updated keyboard - stay tuned for more updates on that.

Android 4. The new Nexus 7 is the first device to officially ship with Android 4. Fixes in this patch are included in later patches. An issue with nesting referenced Flow Reference components no longer occurs. Fixed a memory leak in org. Applications now start correctly after the September patch update is applied. Caffeine cache now correctly processes large payloads with a VM queue.

The Scheduler component no longer causes intermittent deployment failures. October Patch release version: 4. Metadata now resolves correctly for components with multi-level keys. Applications now continue correctly when a dynamic flow reference resolves to non-existent flow. Applications that include the Dynamic Evaluate component in a sub-flow now deploy correctly. September Patch release version: 4. Fixed a race condition occuring during parallel deployments that caused deployments to fail.

Fixed a default error handling issue in the error handler. Mule now masks sensitive data and secure properties e. Fixed error conditions and messages for MUnit tests.

Closing the connection now works correctly if a timeout occurs when an empty payload is sent. When handling redirect responses, Mule no longer becomes unresponsive. August Patch release version: 4. Incorrect status codes and error descriptions no longer occur when using policies. DataWeave: Temporary files created during the Excel streaming process are now deleted.

DataWeave: Addresses the presence of big objects that are pending finalization. July Patch release version: 4. The Set Variable component now creates a variable when the value is null. DataWeave has improved error reporting for recursive imports. June The following notification applies to each patch release in June.

DataWeave: A StackOverflow error no longer occurs when concatenating arrays. The connector Reconnection Strategy is now correctly honored when running in debugging mode. Logging context entries are now propagated correctly to asynchronous SDK operations. Streams are no longer closed when consumed inside of a scope. Binary payloads are no longer corrupted when using VM queues. Logging now includes the original exception when managing reconnection scenarios.

The timestamp reported by XA Bitronix Transaction is now output correctly. Scheduler jobs no longer get stuck due to a race condition. Error propagation with certain error types when using Mule runtime cluster now works correctly.

Using the Java Module in a policy no longer prevents the policy from deploying successfully. The logs now include only one Back Pressure error per exception. The Transform Message component now loads resources using the correct encoding. Undeploying applications in a cluster with FIPS enabled no longer causes the process to hang. Clusters configured to use encrypted communication now work as expected. Closed sockets are now recovered correctly when an unexpected platform connection error occurs.

Event variables that are visible in a Try scope are now visible inside error handlers. April Patch release version: 4. Improved the performance of persistent object stores. The application did not resolve metadata correctly and failed when testing with MUnit. DataWeave: Fixed flat file handling of records with values of variable length.

March Patch release version: 4. Enhanced org. ReadyStatus to provide more information. DataWeave: Prevented an overflow exception by getting a binary token offset. DataWeave: Updated to use encoding when converting a string to a byte array. Fixed an issue in which MediaType did not correctly escape characters. Fixed an issue that caused a memory leak when using a try block. Resolved an issue that prevented opening a new cursor on a closed stream.

February Patch release version: 4. Added warning when the remove variable component tries to remove a non existing variable. MUnit is unable to dynamic lookup flow references. Resolved a problem in which the CloudHub scheduler got stuck intermittently. Added logger to BackPressureStrategySelector for better debugging and tracing.

Fixed an issue where plugins declared in domain could not load classes at application level. Fixed a ConcurrentModificationError on adding an startup listener while deploying an app.

Fixed unexpected error The mapper returned a null value. Fixed an issue that caused failures to deserialize file store based stream payload in batch.

DataWeave: NDJson was not working when being executed in parallel. DataWeave: Fixed an issue with property handling. DataWeave: Fixed an issue where FlatFile cannot write dw keys as values. DataWeave: Fixed an issue where stream batching did not work in deferred mode. January Patch release version: 4. Fixed an issue in running Batch jobs that caused the jobs to get stuck and never finish. Fixed a metaspace classloader leak that occurred during the redeployment of an application.

Fixed an issue that prevented the update operator from selecting attributes. Fixed an issue that prevented processing of XML documents when streaming mode was enabled.

Added an optional warning with information about when an event is dropped. November Patch release version: 4. Fixed multiple WARN log entries that occurred when using a caching strategy. Fixed an issue that occurred when an app transformed data using variables. Fixed an issue with the runtime logging that could cause out of memory issues. Corrected a memory leak referencing the following class in the runtime logs:.

Corrected a memory leak that occurred when using dynamic configurations. Fixed DataWeave attribute selector not dispatching to the correct implementation. Fixed DataWeave inferred types when the output is undefined storage to recalculate output. DataWeave now parses single key-value pairs correctly when mixed with conditionals.

The DataWeave Avro module now correctly converts logical types. Removed unnecessary log messages that appeared when using dynamic objects in DataWeave.

Upgraded the Object Store v2 plugin to version 4. Added support for escaped Char sequences on DataWeave settings. Fixed a problem that occurred when resolving DataWeave errors and processing the flow stack. Fixed an application deployment failure with the loops not allowed error.

Resolved a problem accessing flow. Fixed a serialization problem with policies using the 'Rate limit SLA' policy. Resolved a problem processing DataWeave date expressions when calculating year differences. Fixed an issue in which DataWeave nested dynamic objects skipped elements. Mule no longer creates a default policy manager for each applied policy. June Patch release version: 4.

Fixed an error that occurred when accessing Gatekeeper and Analytics policy templates. Fixed an error that occurred when an expression accessed a target-operation payload attribute.

A custom global error handler is no longer ignored when located after a failing flow. Optimized connection-pool validations to avoid excessive and costly checks. Batch job summary is no longer incorrectly logged twice. Optimized application deployments, resulting in performance improvements. Fixed an issue in which the Scheduler incorrectly ran twice. April 30, The initial 4. New Features and Enhancements Mule 4.

DataWeave DataWeave introduces the following:. Streaming features and enhancements: The XML reader now supports streaming. The JSON reader now supports streaming for more than arrays.

The new Types module enables type introspection at runtime. DataWeave also introduces a number of new functions in existing modules. Core Components The following Core components have new features in this release. Changes Threading Model The three main thread pools have been combined into one unique thread pool. You can still customize the thread pools' configuration if necessary. Performance updates Mule 4. Updated cipher suites for FIPS mode check tls-fips ParseTemplateProcessor Type Inconsistencies when setting target and target variable.

XmlSdkConfigurationInstance does not delegate methods. NPE in operations within dynamically invoked sub-flow. Error mappings not honored while running application on LazyInit. ArtifactAstDependencyGraph is not taking configRef parameters into account. Processed wrapped in a Mono should always recognize itself with a child context. Scatter Gather resulting in Exception reached PS subscriber for flow. XmlSdkConfigurationProvider does not propagate Lifecycle methods. Max Concurrency not honored in flow-ref.

Event modifications lost when setting a securityContext. Dynamic flow-ref must explicitly expect a String on the expressionLanguage.

Memory leak on transactional try with error handlers. Operation policies are not applied to requester when it is inside XML Connector. PlatformManaged connection providers do not inject the config name to its delegate. Extensions-client times out operations after 5 seconds.

When an Exception is raised from a non-blocking SDK operation, an unexpected error is thrown. Source not being intercepted when exception in smart connector.

Lazy init: Object store already defined with inline IdempotentRedeliveryPolicy. Pooled Platform Managed Connection Providers fail to be created. Flow stuck on JMS publish when connector trows an error. Flow source stopped event if it was not started because of a ComponentInitialStateManager. Processing strategy not propagated to chains of scopes in policies.

DefaultExecutionContext constructor has too much performance overhead. Subscription context not propagated to error handlers. Flow in initial state stopped is started when app is stopped and started. HttpPolicyPointcutParameters, only use the headers if a pointcut actually needs them. Fix reconnection for Paged Operations that fail after the first page. Spike: Use generated bytecode instead of reflection to invoke operations.

Make constants in AbstractComponent final. Error when logging error for component with special characters in password. Paging Provider is closed twice when it returns an empty page on the first call to getPage. Race condition when cloning a DefaultFlowCallStack. Connection is not closed during Connection Exceptions on Paged Operations. Operation considers applied policies regarding thread switches. PersistentXaTransactionContext poll not honoring timeout. Thread stucks when undeploying a failing operation policy.

Missing LegacyConnector class in the compatibility module. Error on returning a CoreEvent from Soapkit executor. Missing configuration for ConfigOverride parameter with implicit configuration. Policy execute-next throws error when inside transactional try. CursorProvider not resolved for Object type parameters. DataWeave EL should not be lazy when not in tooling mode. ParameterResolvers initialize a new AttributeEvaluator on each execution.

SDK Should not reject dynamic metadata resolution when an optional key is null. When smart connector in a policy has a parameter with an invalid DW, it hangs. ComponentLocationVisitor creates wrong Locations for Connections.

Infinite Loop when setting -Dmule. SourcePolicyContext is created and added even if no policies apply. Refresh Dance not executed after TokenExpiredException. Unneficient copying of variables and internal params in EventBuilder. Add a compile method on the ExpressionLanguage. Allow UTF-8 in disposition content headers for http request. Race condition on recursive check in flowRef with scatterGather.

Event context termination callbacks not called on some situations. LazyMuleArtifactContext is not disposing correctly components. OAuth 2 Client Credentials not resolving dynamic metadata. Optional ParameterGroups are required to be exported. An alternative version of this wiki is now operational and ready for use.

WoWWiki Explore. WoW info. Gathering Production Secondary. Allied races. Useful macros What are addons? More WoW info. Events Ongoing Seasonal Micro-holidays World. Instances Raids Scenarios Sanctuaries Worlds. Movie info. Explore Wikis Community Central. Register Don't have an account? Patch 4. Edit this page.