The Search experience of the K2View Support Platform has been improved by introducing the following:
We have just released Fabric 6.5.1, which includes the following enhancements:
See the Release Notes for the full list.
We would like to share that we have just released Fabric 6.4.5 that which includes the following:
The full list can be found in the Release Notes.
Stay tuned for the next Developer Community Webinar that will take place after the summer vacations season!
The second K2View Development Community Webinar took place on July 12th where we discussed the news about the Next Generation Fabric and other interesting topics.
Welcome to our first K2View Development Community Webinar! We are happy to present you the 2021 product highlights & the roadmap.
Soft Deploy is Fabric's ability to exclude automatic processes from the LU deployment.
Soft Deploy is mostly useful for implementers working in a development environment and frequently changing their code, such as Broadway flows or Java functions. They can use the Soft Deploy option to deploy their changes without triggering automatic processes.
Fabric provides a set of built-in image manipulation Actors that allow to perform various activities, such as:
Let's check how it works by reviewing the example flow.
Fabric Studio provides an ability to view all active breakpoints. Check out a new panel that was added to the “Server / Activity Logs” area, which displays a list of the breakpoints in the open Fabric objects (currently only Broadway flows are supported), including the File name (flow name) and the ID (e.g. stage where the breakpoint is set).
Broadway offers a number of built-in Actors which address a wide range of predefined activities that can be added to Broadway flows. When your implementation requires business logic that is not supported by a built-in Actor and it is repeated across several flows, you can create your own Actor using an Actor Editor.
Need the ability to change the consistency level on WRITE and READ for DbLoad and DbCommand actors.
The consistency level is set via the Cassandra interface using the server connection string.If you need to change the consistency level during your flow, define an additional interface and use it on your actor.
How do I disable CDC on the local Fabric / Debug?
You can update the config.ini parameter of the local Fabric debug and set the CDC_PUBLISH_MODE parameter to OFF to avoid publishing CDC messages to this server. Alternatively, you can set this parameter to IF_SETUP (Studio Debug default) to publish the CDC message only if the CDC publisher has been configured in the config.ini file. Click to read CDC messages.
Why is there a note in the help section of Release statement saying the following:
Important: When there is a use case of multiple Get in a loop on the same Fabric session, it is recommended to use the Release command (without LU name) after each iteration.
It is recommended to use the Release command without the LU name only if you need to release the LUIs of all LUs in the session. If you need to release an LUI of a specific LU, you need to set the LU name in the release command.
When trying to save the Environments file from Studio, we sometimes get the error saying "Encryption error in environment
Why do we get this error? What's the reason behind this behavior?
We assume that on those cases you use "Fabric URL" option at the environment definitions and you switched from one to another, or you just start using "Fabric URL". In such cases re-key is required. Click to read about Fabric security interfaces.
In the past, we had a hard dependency on specific fabric version say fabric version 5.3 for TDM version 5.1, is it still the case with TDM7?TDM7 release notes mention fabric 6.4.1 but now 6.4.2 is available, wondering if its ok to go ahead with latest fabric versions TDM projects.
You can run TDM 7.0.1 either on Fabric 6.4.1 or Fabric 6.4.2. TDM 7.1 is based on Fabric 6.5.