This topic provides a list of Frequently Asked Questions (FAQs).

Yes and No. The former names for the scripting language—RIFL, djBasic, and EZscript are the same and all functions are still supported. Many functions have new parameters and there may be a few new functions. Also, due to many changes, the process object methods are exposed through scripting language for the power users.

Yes. The same operations are exposed and documented for use with the version 12 engine. Version 9 artifacts will still load and run in the current GUI but you will not be able to create new v9 artifacts.

No. We have upgraded the IDE and the engine to use 64-bit OS functionality as there was minimal impact on a few connectors, where the client drivers such as ODBC and MS Access must be updated. Furthermore, COM is no longer supported.

Java 11 LTS is the embedded Java version for the engine and IDE. All Actian DataConnect Java-based components, connectors and SDKs require Java 11.

Yes. Process workflows are designed to execute multiple parallel threads.

Yes. This feature is re-implemented in version 12 as the IDE is a desktop application and can leverage the embedded DataConnect engine.

Yes. The execution profiler provides a graphical representation of events, actions, and scripting that occurs in maps and processes. This allows quick identification of performance bottlenecks. Outliers can be spotted and remediated in the design environment before ever reaching production.

The integrations can be run and tested from the design environment before porting to another environment. Deployment on a production runtime environment can be a stand-alone engine, DataCloud, Actian Hybrid Integration Manager, on-premise via djengine CLI, or within a custom application which utilizes one of the available SDKs. Also, the the on-premise deployments can be managed within Docker containers.

Yes. All events and actions supported in version 9 are restored. This includes the OnDataChange event management and leading or trailing options for v9 artifacts. The v10 event model that DataConnect v12 uses is different from v9 and does not include ChangeSource and ChangeTarget events. This is because v10 style artifacts can support multiple sources and targets and the event model accommodates doing the equivalent. Furthermore, many new events were added to allow firing your own events, doing aggregation and other tasks that could only be done before through scripting. Joins, Lookups and Temp Targets are now additional sources/targets.

Yes. XML (for v9 artifacts), JSON (for v10 artifacts) and Text editing are included in the IDE so that you can use the artifacts as a typical “resource” on the file system. However, it is recommended to back up the artifacts first as there is no support for the changes that are done through these included editors.

Yes. The document schema designer features are integrated with the IDE. Hence, a separate application is not required. Also, the usability has improved as the schema have their own editors specific to the document type.

Yes. The Developer Community portal is https://communities.actian.com/s/.

Yes, but not integrated firmly. We use an open metadata repository that leverages the file system so other tools (such as GitHub) can more easily be used to manage the artifacts.

Artifacts that are created or updated within Actian DataConnect are automatically tagged with major and minor version properties. This version information can be viewed and edited from an artifact’s Properties tab. Every time an artifact is saved, the minor version of the artifact is increased automatically. After the artifact has changed significantly, you may manually change the major version property as desired. You can create deployable packages with differently versioned artifacts based on these properties.

You can also use version control systems like Git or SVN. This will help you to collaborate and track your changes better and also allow you to go back and restore previous versions.

No, it is not supported.

Yes, there is an Extract Designer that procures the CXL which will run with the engine using the Actian Extract connector.