Nintex K2 connect for SAP release notes

• Nintex K2 connect for SAP 5.2 Installer (5.005.1000.2)

The following items were addressed in the .2 version of the installer:

1. Supports upgrading to Nintex K2 Five (5.5)

2. Added the ability to install Nintex K2 Connect Service Object Designer without having the Server component on the environment. In the K2 Setup Manager >Select components>Client Components screen, the option to install K2 Service Object Designer is now available.

• Nintex K2 connect for SAP 5.1 Installer (5.002.1000.0)

The following enhancements and bug fixes have been made in this release:

• When installing Nintex K2 Five when only the K2 4.7 Visual Studio component is present an error stating “required product not found” displayed

• Installing Nintex K2 connect database with a hyphen in the name caused issues

• Updated ERP Connect files

• Ability to install Nintex K2 connect with SQL Azure

• When using Nintex K2 connect with SSO (Single Sign On), if your credentials do not exist in the SSO store SmartForms will prompt you to sign in. Once the credentials are stored, if the credentials become invalid (because of a password change in SAP) then SmartForms will only provide an error message and no option to re-enter the credentials. The error message states "RfcOpenConnection failed(RFC_LOGON_FAILURE): Name or password is incorrect. Please re-enter".

The following enhancements have been made due to a Nintex K2 connect Service error after upgrade and a RFC_COMMUNICATION_FAILURE error due to Nintex K2 connect connection loss:

• Updated support for Sbyte type

• Added Communication Failure retries

• Multithreading ERPConnect implemented

Updated the ERPConnect version to ERPConnect 5

Updated Nintex K2 connect to use the new long format K2 licensing which is backward compatible with existing short keys.

After upgrading to Nintex K2 connect 4.7.1 it was not possible to publish service objects through Visual Studio due to a "Time out has expired" error. Nintex K2 has reduced the number of calls to SQL to populate Service Objects which resolves this issue.

When installing Nintex K2 connect in a Nintex K2 cluster configuration the local server name was used instead of the cluster FQDN

The following enhancements and bug fixes have been made in this release:

• Installing Nintex K2 connect database with a hyphen in the name caused issues.

• Updated ERP Connect files.

• Ability to install Nintex K2 connect with SQL Azure.

• When using Nintex K2 connect with SSO (Single Sign On), if your credentials do not exist in the SSO store SmartForms will prompt you to sign in. Once the credentials are stored, if the credentials become invalid (because of a password change in SAP) then SmartForms will only provide an error message and no option to re-enter the credentials. The error message states "RfcOpenConnection failed(RFC_LOGON_FAILURE): Name or password is incorrect. Please re-enter".

The following enhancements have been made due to a Nintex K2 connect Service error after upgrade and a RFC_COMMUNICATION_FAILURE error due to Nintex K2 connect connection loss:

• Updated support for Sbyte type

• Added Communication Failure retries

• Multithreading ERPConnect implemented

Updated the ERPConnect version to ERPConnect 5

Updated Nintex K2 connect to use the new long format K2 licensing which is backward compatible with existing short keys.

After upgrading to Nintex K2 connect 4.7.1 it was not possible to publish service objects through Visual Studio due to a "Time out has expired" error. Nintex K2 has reduced the number of calls to SQL to populate Service Objects which resolves this issue.

When installing Nintex K2 connect in a Nintex K2 cluster configuration the local server name was used instead of the cluster FQDN.

Added logging for destinations - When adding or modifying destinations in Nintex K2 connect you can set the LOGENABLED and LOGPATH fields. When enabled, tracing is activated and files are generated in the specified directory. Full RFC traces are generated.

Currency and Decimal Fields are not transferred correctly to and from SAP.

Nintex K2 Connect version 4.7 Test Cockpit throws an "Input String was not in a correct format" error.

Error occurred when generating SmartObjects. Service with name "" not found.

SmartObjects did not handle null-termination characters in string types returned from SAP.

This release includes the latest version of the ERPConnect assemblies (SAP NetWeaver RFC libraries) which are included and automatically installed by the Nintex K2 connect Setup Manager.

Caching of objects - When a service is executed the connection along with the object is cached and used on subsequent executions. The cache is only available during the runtime of K2 Server. The first execution takes the normal amount of time but subsequent executions are faster. If any errors occur or changes are made to the object the cache is invalidated. For steps on setting the caching see KB000881 - How to cache the connection for a Nintex K2 connect service instance.

An Error was received stating "K2 blackpearl Server and K2 connect Server names are not the same" when Nintex K2 was installed in a Farm environment.

Nintex K2 Connect is configured with predefined credentials for SAP destinations in the connection strings. All SAP calls were made using the corresponding users SSO credentials, but after upgrading to Nintex K2 connect 4.6.11, SAP calls used the predefined credentials from the connection string.

SAP NetWeaver RFC libraries handle connection strings differently to the previous LIBRFC32.dll resulting in multiple configured destinations to no longer function as previously.

The Connect service took a long time to start/restart when you had a large number of service objects published to the repository.

Minor memory usage enhancements have been made.

Changed from using SAP Classic RFC libraries to SAP Netweaver RFC libraries.

Static credentials are now preserved when publishing service objects.

In this release support for Microsoft Visual Studio 2015 and Windows 10 (Pro and Enterprise) has been added.

• SAP is ending support for the Classic RFC libraries on the 31 March 2016 after which SAP will only support the SAP NetWeaver RFC libraries. The new dlls are not redistributable from SourceCode Technology Holdings, Inc and must be obtained from services.sap.com. Once downloaded the new NetWeaver RFC libraries must be copied to the respective system folders. The zip files for each architecture (64 and 32 bit) will contain six files. All six files need to be copied.
  The 32bit files go to c:\Windows\SysWOW64
  The 64bit files go to c:\Windows\System32
  Now use the Nintex K2 connect 4.6.11 (4.10060.870.0) to upgrade your environment.

• In Nintex K2 connect 4.6.10 or later the installer includes the required ERPConnect dlls. For new installations it will no longer be required to install ERPConnect before installing Nintex K2 connect for SAP. For upgrades there is also no need to upgrade the ERPConnect software as the new Nintex K2 connect installer will automatically do this for you.

• The installer will update Nintex K2 connect 32-bit and 64-bit installations. One installer is used for new installations as well as upgrades. When performing an upgrade, the current Nintex K2 connect installation will be uninstalled and the new version will be installed. The existing settings will be retained such as the Nintex K2 connect license key, however it is important to select the correct database during the installation.

The following issues have been resolved in this release.

• When executing a large number of SmartObject events, the K2 service becomes unresponsive which will affect the response of other Nintex K2 components such as Workspace.

• Publishing a Service Object from Visual Studio in a cluster environment causes the Nintex K2 connect Service Instance name to revert back to the local server name.

• An error occurs stating: "Could not find element '[ELEMENT]'" when executing a BAPI using internal tables, from the Nintex K2 connect Test Cockpit.

• When executing a BAPI a "TABLE_NOT_ACTIVE" error occurs. This is now fixed with the ERPConnect dll being included in the Nintex K2 connect installation.

In this release ERPConnect has been included in the installer and it is no longer necessary to run the ERPConnect.exe

• Nintex K2 connect 4.6.10 installer now includes the required ERPConnect dlls. For new installations it will no longer be required to install ERPConnect before installing Nintex K2 connect for SAP. For upgrades there is also no need to upgrade the ERPConnect software as the new Nintex K2 connect installer will automatically do this for you.

• The installer will update Nintex K2 connect 32-bit and 64-bit installations. One installer is used for new installations as well as upgrades. When performing an upgrade, the current Nintex K2 connect installation will be uninstalled and the new version will be installed. The existing settings will be retained such as the Nintex K2 connect license key, however it is important to select the correct database during the installation.