Linx version 2.4.762.1232

Please note that Linx version 2.4.762.1232 is ready for download. Please see the release notes for a complete list of changes. Some of the new features / changes include:

• Support for .NET 4. If you want to install this version, please ensure that you have .NET Framework 4 installed as well.
• Add an export link to the Log tab on the server. Using this link, it is now possible to save all the the log entries on the server to a .csv file.
• Display the web service URL for a process on the server. If you right-click on a process on the server, there is a "Display process URL" option that will display the web service address for the process. It will also prepopulate a list of all the required parameters necessary to execute the process.

Since there were numerous changes to the Linx installation to improve the future maintainability, as well as to fix some bugs, it is recommended that you do a clean installation (not an upgrade). If you want to perform an upgrade or manual installation, please contact me for more information.

The next piece of work will revolve around the architecture of Linx processes - see the roadmap for more details.

Unused Linx components

As part of our usage data analysis, we also went through an exercise to determine which Linx components do not appear in any production solutions. The following table lists the unused components:

Component Name
Formz.Linx.SignatureRectangle
Linx.AtalasoftBarcode.AtalasoftBarcodeReader
Linx.CATS.CATSAuditData
Linx.CATS.CATSAuditReader
Linx.CATS.CATSAuditWriter
Linx.CATS.CATSData
Linx.CATS.CATSReader
Linx.CATS.CATSUnpaidsData
Linx.CATS.CATSUnpaidsReader
Linx.CATS.CATSUnpaidsWriter
Linx.CATS.CATSWriter
Linx.FinancialServices.BondCalculator
Linx.FinancialServices.BondDirtyMarketValue
Linx.FinancialServices.BondRateConverter
Linx.LinxSilica.SilicaData
LinxCDV.LinxCDV
LinxEMX.EMXData
LinxEMX.EMXReader
LinxEMX.EMXWriter
LinxExcel.ExcelPrint
LinxFixNet.FixNetEndOfDay
LinxFixNet.FixNetSendMessage
LinxFixNet.FixNetSessionState
LinxFixNet.FixNetStartSession
LinxFixNet.FixNetStopSession
LinxFTP.FTPSFileUpload
LinxHiport.HiportParse
LinxInternet.Autodial
LinxInternet.AutodialHangup
LinxMQServer.MQServerReader
LinxMSMQ.MSMQReceive
LinxMSMQ.MSMQSend
LinxPDF.PDFJavaScriptRead
LinxPDF.PDFJavaScriptWrite
LinxPDF.PDFReadFormFields
LinxPDF.PDFWriteFormFields
LinxPowerpoint.Scripting
LinxRightFax.RightFaxPrinterSend
LinxStandard.SolutionStructure
LinxStrings.StringConverter
LinxSwift.SwiftBuild
LinxSwift.SwiftData
LinxSwift.SwiftParse
LinxTCP.TCPReadText
LinxTCP.TCPWriteText
LinxTextFormat.TextBuild
LinxTextFormat.TextData
LinxWebService.REST.CallRESTWebService
LinxWord.WordPrint
LinxWord.WordRead
LinxWord.WordWrite
LinxXml.XmlFormatter
LinxZetaFax.ZetaFax

We are going to use this list to determine the future development and maintenance of certain Linx components. The items that are highlighted in red will definitely be removed in future versions of Linx, while we are considering removing the items in yellow. If you are using any of these highlighted components (red or yellow), please let me know as soon as possible. As previously stated, all the production files that were used in the analysis is available from me, so if you have any questions or concerns about these statistics, you are welcome to contact me.

Linx usage data

We recently performed an in-depth analysis of all the Linx solutions that are currently running in a production environment to assist us in our planning for future versions of Linx.

Some interesting patterns emerged during this excercise, some of which are highlighted below. If there are additional statistics that you would like to see, please let me know.

Solution version

This chart displays the Linx version that was used to save the solution in the designer. Note that this version does not necessarily translate to the version of the Linx server that is used to execute this solution.


Component usage

This chart displays the top 10 most commonly used components across all solutions. All additional components are grouped under the “Other Components” entry.



Service usage

This chart displays the different services used. Note that it does not distinguish between active and stopped services.


Most commonly used component name

The following table lists the 10 most commonly used component instance names:

Name	Instances
Declare	837
ExceptionHandler	667
Variables	562
EH-1	483
prc_CFErrorLog_insert	482
LogActivityError	460
ExceptionHandler1	429
prc_WOHistory_insert	373
Assign1	328
InsertWOHistory_Failed	326

Most components per process

The following table lists the 10 processes with the largest number of components per process:

Solution	Project	Process	Components
NitroFaxProcessingV1.16	Nitro	App_NAS30_FormzGenAppDetail_NBB	437
NitroFaxProcessingV1.16	Nitro	App_NAS30_FormzGenAppDetail_CM	246
T1.3_GL_ProductsProcessing	Products_AccPac_Integration	T1.3.3.4_Submit_GL_FC_ALL	234
NitroFaxProcessingV1.16	Nitro	PW_Formz_INCOMMING_Load	230
Nimitz-FormzGeneration	Nimitz-FormzGeneration	FormzGeneration - 2.ManualGenerateBIO	215
Nimitz-FormzGeneration	Nimitz-FormzGeneration	FormzGeneration - 1.GenerateBIO	214
NitroFaxProcessingV1.16	Nitro	App_NAS30_MailSending	159
NitroFaxProcessingV1.16	Nitro	App_NAS30_FormzGenAppDetailPerDocumentType	155
ABSA_Capital_FX_Onboarding	0.3_CASAClientForm	0.7_CASA_Email	149
iMALI_1.4	1.4	04_Escalations_CheckAndCreateForEscalations	137

Most processes per solution

The following table lists the 10 solutions with the largest number of processes per solution:

Solution	Processes
ValuationsDashboard	191
PrimaryBanker	167
NitroFaxProcessingV1.16	143
LinxBusinessBankingV1.30	130
iMALI_2.4	128
5.03IntegrationDataExtract	119
MultiManager-ElectronicSubmissions	85
iMALI_1.4	85
FC_STP_T1_259	84
iMALI_1.3	83

Most services per solution

The following table lists the 10 solutions with the largest number of services per solution:

Solution	Services
ValuationsDashboard	39
LinxBusinessBankingV1.30	26
NitroFaxProcessingV1.16	22
iMALI_2.4	19
PrimaryBanker	18
BankCodes	11
iMALI_1.3	11
iMALI_1.4	11
iMALI_1.2	10
FC_STP_T1_259	10

Linx 64-bit compatibility

We recently performed some tests to determine if there are any compatibility issues when running Linx in a true 64-bit environment. The results were very encouraging, with only a few components causing problems. You can see the full test report (and workarounds, where applicable) here.

The next step will be to determine the actual usage of these problematic (and other) components and then decide on a course of action to get it working in all environments.