Foundation Y26H2 - UK

Response when calling a webhook

This has been changed so that a response can now be sent back to the caller of the webhook.

Embedded files on receipt

Via setup it is now possible to unpack multiple embedded files on different keywords in the XML/json.

Stylesheet version 2 (XSLT 2.0) is now supported

Going forward, it is possible to use stylesheet version 2. Using stylesheet V2 gives access to more functions in the stylesheet.

Among other things, V2 also makes it possible to split the in-house XML file into several outgoing XML files. The destinations rest service, FTP, IFS and mail currently support this option.

OCR - find partner via SQL

If AI can find multiple IBAN numbers, all IBAN numbers (in the relevant setup) can now be read.

The definition has also been corrected so that you can write FINDCREDITOR* and thereby find all SQL with that name from o243-

FTP test connection

When using FTP via the batch server, it is now possible to test the connection in ABC via a button on both the document destination and the ABC profile.
In other words, it is possible to test whether the connection configuration works.

Version 2 stylesheet validation

When using stylesheet version 2, validation has become stricter, and therefore "Stylesheet version" in the ABC system setup is set to V1.
This can subsequently be changed to V2 when you are ready to switch to stylesheet version 2.
In appl. 0361 (on 5250 emulation) it is possible to test all stylesheets (F18 option I).
This test will find all stylesheets on destinations, partners, profiles and EDIFACT setups and test them.
The result is written to a spreadsheet, which is sent by e-mail.

FTP send/receive via the batch server

The batch server has grown into a central and important server in ASPECT4, used for many things in connection with ABC and elsewhere.
For example when stylesheets are used, DMS, conversion of spreadsheets, integration to payment solutions, etc.
Via setup, it can be selected on the profile and the destination that sending and receiving should in future go via the batch server (instead of via the DocManager).
If you choose to send via the batch server, it may be advantageous to change the number of threads (jobs) that process requests. The default is 10 threads. In appl. 0653 Java synchronous services, add THREADS(20) so that it reads Command . . . . . . . . . . . . > EG0JVSZS THREADS(20).
On the FTP destination, things have been moved around a little so that the fields are displayed in a better way.
On receipt, the 0654 job only finishes once it has fetched the files (as the transfer no longer takes place asynchronously via DocManager).
Speed has been improved, as processing starts immediately.
On sending, the ABC job still goes to status 80 and the file status is set when the files have been sent or have failed.
A queue can also be specified here. There is no validation of the queue name. The field is used if you want to ensure the order.
With this release it is still a choice whether FTP sending should continue to run as before via DocManager, or whether it should run via the batch server.
In the long term, the option of using DocManager to send/receive via FTP will be discontinued.

Incoming json

If the received json file does not contain data to be received, no document will be created going forward.
(This can happen if an empty file is sent, or just a single keyword is returned)

Explanatory text

The table has been extended so that an explanatory text is shown for the key value.
This could for example be the name of the customer, supplier, user or similar.

Application 0365 Attachments - show system category

In application 0365 it is possible to display selected/all manually archived Attachments.
If you also want to see automatically archived Attachments (called system category), you must press F8.
The next time the application is selected, only manually archived Attachments will be shown again.
Users who constantly/often work with automatically archived Attachments now have the option to have both manually and automatically archived Attachments shown every time they enter application 0365.
Via a code (in application 0110 on application 0365) it can be controlled that the system should remember whether F8 has been pressed.

Support for unicode in Attachments
Attachment has been improved so that it can now handle files containing unicode characters. This means that attachments with unicode can also be sent as e-mails in later flows.

Application 0365 Attachments

In the list you can now choose the period for which Attachments should be shown (based on the creation date).
The default is 'The last 3 months'.
This change has been made to optimise the speed of the application.

New DAWA address directory

Previously, ASPECT4 used dataforsyningen.dk for automatic completion of addresses.
This has been replaced with adressevaelger.dk

New and more secure login experience with OAuth

With Y26H2, ASPECT4 introduces support for OAuth, a modern and future-proof standard for authentication. This gives companies the opportunity to strengthen security around user login while creating a better foundation for future integration and identity solutions.
This release delivers the first phase of the solution, which makes it possible to use the new login method in ASPECT4. At the same time, the foundation is laid for the next phase, where authentication is moved to a dedicated identity platform based on Keycloak. In upcoming versions, this will open up further possibilities within central user administration and modern security principles.
Companies wishing to adopt OAuth now should be aware that a few configuration changes and setup activities are required. The solution does not support environments that use Single Sign-On (SSO).
OAuth can also be used in connection with REST web services from this release.
If you want to get started with OAuth, EG can help with planning, setup and implementation. This assistance is delivered as a paid consultancy service.
Why is this interesting?

• Strengthens security around user login.
• Introduces a modern authentication standard.
• Creates the foundation for future identity and access solutions.
• Supports a more standardised approach to integrations and web services.
• Prepares ASPECT4 for upcoming technological possibilities within access management and security.

Colour schemes in Windows
In the new ASPECT4 look, which is now available (activated under Settings/Colour scheme), each user can choose that ASPECT4 should follow the same colour scheme as Windows.
(See the description of 'New look' at the top of the document)

Audit

In the audit list (application 0323), the timestamp of the audit being worked on is now shown.
In the white list (application 0324), the timestamp of the audit being worked on is now shown.
Via a button, all whitelisting made for the audit can be deleted.

Java 21

The portal has been changed so that it now uses Java 21 (instead of Java 17).
It is a requirement that the licensed program for Java 21 is installed on the server (IBM i).
No other manual actions are required.

Deactivated users

The application 'Whitelisting' (0323) has been changed so that only active users are shown going forward.

Table with stepping stone link per program/screen

The use of AS4ALKT1 was replaced by the table AS4ALKT2 in release 6.
The table AS4ALKT1 is discontinued in this release.

Special characters in ABC

When data is received via e-mail in ABC, a file is automatically created on the IFS.
This file must not contain special characters.
The program has been changed so that files with special characters are saved with a valid name.

Enrichment

A check is now made that the enrichment program actually exists.

Date fields
When hovering the mouse over a date field, it is now displayed a little more neatly than before (in the tooltip). Example: Monday 31 August 2026

Audit list/whitelist

In the audit list (application 0323) and the white list (application 0324), the timestamp of the most recent audit is now shown. Previously, whitelist information from the previous audit timestamp was shown if all whitelists were deleted.

Java 21

Java 21 must be installed

Console screen

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

Receiving the software

Sign on with your own user and run 'Install ASPECT4 software' (application 0590). Run with 'Receive' (option 1).

EGSERVER or VAP subsystem

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

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

(when loading into test it is not necessary to end EGSERVER, but make sure that everything is shut down in the test environment. Once EGSERVER has been restarted during the night, the test environment can be used again. Alternatively, everything can be restarted via appl. 0653)

Installation

When EGSERVER has been stopped (check 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 to be updated.

Start EGSERVER (or VAP)

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

NOTE! With this update it is important (in order to activate data history on general registers) that the STRSBS command is run in a slightly different way than usual. From the 5250 emulation, on the Sign on screen, after the user and password have been entered, fill in the field 'Program/procedure' with the text qcmd. Then press Enter, and on the command line that appears, run STRSBS.

(If other updates need to be installed that require EGSERVER not to be started, wait with this step until later).

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

Citrix/Terminal servers

If the ASPECT4 client is installed on a Citrix/terminal server, it 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 run, the server name etc. must be exactly as in the jnlp file.

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

Robots

Note – when updating, there is no guarantee that applications used in the company's robots are unchanged. Robots that access changed applications may fail – and must therefore be re-recorded. It is in any case a general condition for Robotics products that after a software update it is important to test the robots that are used/critical.