Foundation Y26H1 - UK

DB2 files

On the destination for DB2 files, it is now possible to deselect the option allowing new rows to be created.

OCR

Instead of having to find a partner via a search list, it is now possible to find a partner via SQL, e.g. based on CVR number or bank account. Multiple different SQL search expressions can be created.

FTP and PDF file

When sending, it is now possible to change the filename of the PDF file, if there is only one file to be transferred.

Enrichment

Via the module EA0110RJ, it is now possible to convert image files from one type to another (e.g. from jpg to gif).

JSON and base64

It is now possible to convert JSON to base64 and embed it in a JSON file.

OCR

On DETAIL lines, table2 can be used. If table2 does not exist, it can now be overridden so that table1 can be used instead.

EDI – Optimisation regarding creation of partners

If there were many partners, creating a new one could take a long time. This has been improved so that the speed of creating partners is significantly faster.

Event and Exception Manager (EEM)

It is now also possible to deselect/opt out of receiving notifications for a system area.
Previously, it was only possible to opt in to areas.

REST service and JSON

For JSON, it is now possible to select a new method that converts JSON to XML before the ABC. The stylesheet can then be executed.
This method should be used for very large and complex JSON files.

ABI

In the ABI, it is now possible to limit triggering to a number of data export channels (instead of all export channels as before).
The command EG0655ZF has been enhanced with the ability to specify up to 5 export formats.
If none are specified, it works as before.

Attachments from Microsoft's new Outlook client

The new Outlook client has certain limitations.
One of them has previously been that it was not possible to drag and drop an email from it and insert it as an Attachment in ASPECT4.
An add-in for the new Outlook is now available. With this, it is possible to perform the action. The add-in can be downloaded here https://magicdragin.app/.

New integration platform based on Azure Service Bus

In this release, ASPECT4 introduces a new integration option based on Azure Service Bus.
The solution is implemented via a standardised connector in the Foundation layer and is now used by both ABC and ABI. In addition, customers can use ASPECT4 workflow management to send ad hoc messages to Azure Service Bus.

Why is this a good idea?

With Azure Service Bus as the integration platform, ASPECT4 gains a robust, scalable, and future-proof way to exchange data and events with other systems – both internal and external. This is a strong extension of the existing integration options.

Instead of tight point-to-point integrations, a loosely coupled, message-based architecture is introduced, providing far greater flexibility and stability in the integration landscape.

What does this mean for you as a customer?

The new integration opens up a number of concrete possibilities:

• Easy and secure integration with external systems
  Azure Service Bus is a proven cloud platform for reliable message exchange. This makes it easy to integrate ASPECT4 with, for example, other business systems, cloud services, data platforms, or specialised solutions – without ASPECT4 and the receiving system needing to know each other directly.

• Event-based business processes
  ASPECT4 can now send messages when something business-relevant occurs (e.g. creations, changes, or approvals). These events can be used to trigger processes in other systems – in real time or asynchronously.

• High operational reliability and scalability
  Azure Service Bus handles load, queue management, and error situations. This means that messages are not lost even if a receiving system is temporarily unavailable, and that the solution can scale in line with business needs.

• Less complexity – lower maintenance
  By consolidating the integration in the Foundation layer and using a standardised connector, the need for customer-specific integration code is reduced. This provides simpler solutions that are easier to maintain and develop further.

• Flexible ad hoc integrations via ASPECT4 workflow management
  With workflow management, messages can be set up and sent to Azure Service Bus without new development. This allows quick responses to new business requirements and the establishment of temporary or supplementary integrations.

A future-proof integration direction

Azure Service Bus is a central part of Microsoft's cloud ecosystem and supports modern integration patterns.
With this extension, ASPECT4 is well equipped for:

• increased use of cloud services
• integration across platforms
• more automated and event-driven processes

In short: a stronger, more flexible, and more scalable integration platform – to the benefit of both IT and the business.

Concretely, the extension consists of a couple of new configuration applications, in the form of the applications Azure applications (0268) and Azure messages (0269). With these two applications, it is possible to build the configuration needed for ASPECT4 to integrate with Azure Service Bus. Application 0268 is the starting point. Here, one or more Azure "applications" can be created. An application in this context refers to account information for an Azure account. From here, via application 0268, namespaces, data queues, and topics can be created and maintained. With the configuration in app 0268 in place, app 0269 can be used to configure "messages". A message here is a specific message type. A message can have one or more destinations. A destination is a reference to an application from 0268 including references to a namespace, data queue/topic.

ABI has been extended with a new data export destination, which can now be a message from app 0269. Similarly, ABC has been extended with a new destination type, which can also point to a message from app 0269.

In addition, a business module has been created that exposes, among other things, a function for sending a 0269 message to Azure Service Bus. As previously mentioned, this can be used from, among other things, workflow management.

With this release, the integration runs exclusively from ASPECT4 towards Azure Service Bus. It is not yet possible for ASPECT4 to receive messages from Azure Service Bus.

Use of the module requires a separate user key.

Layout administrator (0X03)

If you have named filters, column sets, pivots, and similar items, the name will now be displayed in the overview screen under Layout in application 0X03.
This makes it significantly easier to identify the individual setup.

Improved readability

When maintaining parameters in application 0128 or 0110, readability has been improved. It will now be easier to see which text belongs to which code.

Multi-factor authentication in ASPECT4 Client
With the implementation of Multi-factor Authentication (MFA) in ASPECT4 Client, it is possible to improve security.

Multi-factor authentication is enabled/disabled in the authorisation permission for the ASPECT4 client (application 0X00). This may be created personally, but most commonly the authorisation permission is created via application 0110/0128 per function group (e.g. sales, purchasing, warehouse, accounting, EG1, etc.)
If MFA is enabled, users belonging to the relevant function group will, the next time they start ASPECT4, be required to scan a QR code and save it in their Authenticator app.
In future, these users will, upon sign-on, be asked to enter a valid code generated in their Authenticator app. The code typically expires after 30 seconds.
In companies where MFA is not enabled by default (i.e. 'Apply Multi-factor Authentication' = 0 on the authorisation permission for application 0X00), individual users have the option to override this if they wish to increase security.
The personal override is created under the large A/Files/Settings/Server – click the 'Set up MFA' button and scan the code.

DocManager – new functions for use in calculations and conditions

PING
The function returns a single apostrophe ('). This is particularly useful when building calculations where you need to include ' in a string.

EXECCMD(<X>, <Y>, <Z>)
Executes a command <X> with parameters <Y>. With <Z>, you specify whether DocManager should wait for the command to complete before continuing.
Most often used as a report condition to have the command executed only once before the report is printed.

Example:
EXECCMD('C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe', '"Get-PrintJob -PrinterName ' + PING + 'Microsoft PCL6 Class Driver' + PING + ' | Remove-PrintJob"', TRUE)

This formula will execute powershell.exe with a command that clears the print queue for the printer Microsoft PCL6 Class Driver, and DocManager will wait for the command to complete.

OS V7R5M0

With Y26H1, the OS system requirement is raised to V7R5M0.

History on general registers

Data history is now applied to all relevant general register sections in Foundation.

Proxy security

In a previous release of ASPECT4, the so-called Proxy was introduced. The purpose was to make communication between the ASPECT4 Client and the server more robust, so that temporary network outages can, in most cases, be "survived". With this release, the option is now introduced to increase the security of communication between the client and the Proxy, by enabling encryption of network traffic.

To activate encryption, it is required to obtain a so-called certificate.

Workflow parameter definitions – use of uppercase

Via the setup in parameter information (application 0W00 Parameter definitions), it is now possible to select that only uppercase letters may be entered in string fields.
This is done by using the input type "String uppercase".

Tab in the task list with document

It is now possible to display attachments in the client task list.
This can be used to display documents (invoices and similar) during document approval (typically PDFs).

The prerequisite is that, in the parameter definition (application 0W00), the new input type 'Display attachments in task list' has been selected.

In the process definition, the content (value) in the parameter to be used for displaying a document MUST ALWAYS be the attachment ID.

When the task list is displayed, a tab will be shown for each parameter on the task that is defined with the input type 'Display in browser in task list'.
Only attachments with the file types PDF, EML, and TXT will be displayed as a tab in the task list. All other file types will be opened via the program associated with the file type.
When the task is displayed, focus will automatically be on the 1st document tab (this only applies if the task list is run as an application).

WebService

After calling a REST service, a file could be returned containing large amounts of data that were not needed.
In future, such large files will be stopped.

Excel to CSV

When converting from Excel to CSV, only 3 decimal places were included.
This has been extended to 9 decimal places.

Spreadsheet

If an Excel spreadsheet contained a text field (a cell) with a line break, this line break became a new line in the CSV file. This could cause data to be placed incorrectly.
This has been changed so that line breaks in a cell can now be handled.

Query/work with attachments (0365)

The application can now also display attachments saved on the DocManager form name.

Individual keystrokes disappear when typing quickly

When typing quickly in tables in QueryManager, it could happen that individual keystrokes were not registered in the client. This has now been fixed.

Counter on the Workflow icon

If you do not wish to see the small "counter" on the Workflow icon, you can disable it under properties by selecting 'No' for 'Show count on icon'.
A bug caused the last two parameters 'Show notifications' and 'Show count on icon' not to be saved.
This bug has been fixed.

Multi-factor authentication in CrossPad

CrossPad now also supports MFA for web users (0X99 users).

Renaming a Query

Previously, it was possible to accidentally overwrite a Query if, when renaming it, you gave it the same name as an existing one.
This will no longer be possible.

A couple of vulnerabilities eliminated in ASPECT4 Client for web

In the ASPECT4 client for web, a couple of vulnerabilities related to so-called Cross-site scripting have been removed.

Console screen

A console screen ('green screen') must be used for all installation activities mentioned here (the ASPECT4 Client must not be used).

Receipt of software

Sign on with your own user and perform 'Install ASPECT4 software' (application 0590). Carry out with 'Receipt' (option 1).

EGSERVER or VAP subsystem

The EGSERVER subsystem must be shut down. This is done with the command:

ENDSBS SBS(EGSERVER) DELAY(30) ENDSBSOPT(*NOJOBLOG).

(When loading in a test environment, it is not necessary to shut down EGSERVER, but make sure everything is shut down in the test environment. Once EGSERVER has been restarted overnight, the test environment will be available again. Alternatively, everything can be restarted via app. 0653.)

Installation

Once EGSERVER has been stopped (verified using WRKSBS), the update must be installed. This is done in application 0590 'Install ASPECT4 software'. Select option 2 'Install'.

Remember to sign off AFTER the update has been installed.

Conversion runs

Sign on again with your own user.

Select application 0690 'Conversion runs'. Select system 400. Start the conversion with F16.

It is important that the conversion takes place in the environment that is being updated.

Start EGSERVER (or VAP)

The EGSERVER subsystem must be started. On a command line, use the command STRSBS SBSD(EGSERVER). When EGSERVER is started, all servers listed in application 0653 are automatically started.

NOTE! For this update, it is important (in order to activate data history on general registers) that the STRSBS command is executed in a slightly different way than usual. From the 5250 emulator, on the Sign on screen, after entering the username and password, fill in the 'Program/procedure' field with the text qcmd. Then press Enter and on the command line that appears, execute STRSBS.

(If other updates that require EGSERVER not to be running need to be installed, defer this step until later.)

DocManager must be restarted on machines where it is already installed. (This can only be done once EGSERVER (or VAP) has been started.)

Citrix/Terminal servers

If the ASPECT4 client is installed on a Citrix/terminal server, this must be updated via an import command.

On EG's deployment page (e.g. http://SERVER:1045/client/), there are 3 large buttons. Under 'read more', there is a guide on how to update the cache. Remember that when the import command is executed, the server name etc. must be exactly as in the jnlp file.

In application 0361 'System level', you can use F16 'Client Information' to display which path the client can be imported from (and thus also how to access EG's deployment page).

Robots

Please note – When updating, there is no guarantee that applications used in your company's robots are unchanged. Robots that access changed applications may fail and will therefore need to be re-recorded. It is also a general condition for Robotics products that, after a software update, it is important to test the robots in use/critical robots.