Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

To view the release notes, please click on the corresponding links, which will display them in detail.

If you would like to see the complete overview of the release notes, you can use the "print" function of this page. This way you do not have to expand the release notes individually.

 24.1.2 (2024-06-06)

Required Transfer Client version: 24.0.1.498

Required Portal version: 23.02.01

TicketCategoryDialogRelease InformationPatch 
GTC-422ReportingOthers
In the Reports area, the entry "Own reports" has been renamed to"Reporting engine".
-
GTC-736Others-

The Excel export has been adapted. Additional information such as company and period are now also displayed.

The PDF export has been adapted so that no representations are cut off and the dialogue is always represented completely

-
GTC-3658Master DataPeriods

Situation:

For technical reasons, the drop-down list of periods for the "Calculation bases" field is no longer displayed. The calculation basis must now be entered directly.

Solution:

The latest available calculation base is displayed as proposed value. When creating new periods, the latest calculation base is always used. If a period is copied, this also applies to the "Calculation base" field.

-
GTC-3654CompanyStatus

Situation:

The pop-up for copying transaction data could not be accessed.

Solution:

The authorisation check has been corrected so that it can be opened again.

-
GTC-3683Authorisation-

Situation:

In some dialogues, the authorisation checks do not work correctly. The following dialogues were affected by this in certain constellations and have now been corrected:

1) 8b Subjects - Import
2) Development of losses carried forward
3) Trade tax decomposition - export
4) Master data / CoA companies
5) Basis data / notification of tax structures
6) Period transfer - import
7) Master data / Toolbox

-
GTC-3686CompanyBasis data

Situation:

The prior-year values for tax rates are no longer displayed in the basis data.

Solution:

The issue has been corrected.

-
 24.1.1 (2024-05-15)

Required Transfer Client version: 24.0.1.498

Required Portal version: 23.02.01

TicketCategoryDialogRelease InformationPatch 
AMP-7932Portal-

Situation:

In newly installed environments, the behaviour occurs that it is not possible to switch from the Income Taxes module to the Portal module. The same behaviour occurs when a newly created user works with the system.

Solution:

The connection between the Portal and Income Taxes modules works properly in both directions.

-
AMP-6556CompanyMilestone

Situation:

To close all milestones (" finished"), the user must save the dialogues in the correct order and close the milestones one after the other. If the "Deferred taxes" milestone is set to "Completed", the "Reconciliation" milestone always remains in the "In progress" status, even if the status is plausible in theory. The milestone status only changes to "plausible" after the TRR dialogue has been saved. Only then is it possible to close the dialogue.

Solution:

If the "Deferred taxes" milestone is closed, the TRR dialogue is recalculated directly in the background. The "Reconciliation" milestone is automatically set to the "plausible" status according to the validation calculated from it or remains in the "in progress" status.

-
AMP-5753ImportImport Suite

Situation:

The "Import Suite" dialogue enables the import of values from module Tax Balance.

The import process can currently be started on this page. However, the user must then call up the dialogue manually to update the page. If the import takes longer, this process may have to be repeated several times until the Tax Balance processing is complete. Only then the import result is displayed and can be saved by the user.

Solution:

After starting the import, the page refreshes automatically. As long as the import is running, a corresponding message appears. As soon as the import is finished, the import log is displayed.

The page can also be exited during the import.

-
AMP-6111InterfacesImport

Situation:

Direct imports (import from database table TIMPORTBS) were only available in combination with the standard mapping (direction: "Import").

Solution:

Direct imports (import from database table TIMPORTBS) can also be used in combination with the mapping engine (direction: "Import (enhanced)"). A corresponding is maintained in dialogue "Import mapping".

-
AMP-7002Master DataPeriodsThe maximum size for uploaded files can be configured with the FILEUPLOAD_MAX_SIZE_IN_BYTES flag. The default value is set to 50MB.-
AMP-4941InterfacesImport Suite

Situation:

Dialogue "Import Suite" (reading data from Tax Balance) cannot be used in combination with the mapping engine.

Solution:

In dialog "Import Suite" (reading data from Tax Balance) an interface structure of the mapping engine with source "Direct import" can be used.

-
AMP-5740Master DataRoles

Situation:

Role changes and assignments done in the portal might be out of sync with the data stored in the Income Taxes database (eg because of a network error). Note that the only possible error concerns deletions of roles and role assignments.

Solution:

Roles and role assignments are synchronised with the portal during startup of the Income Taxes Tomcat and during user login.

-
AMP-4943OthersPopups

Situation:

In some dialogues the confirmation popup for deleting an entry (eg: § 8b KStG) does not display any details about the selected item.

Solution:

The confirmation popup for deleting an entry shows significant details about the selected item.

-
AMP-6995Master DataRolesRole allocations weren't able to be transfered to IncomeTaxes if a role, that isn't known to IncomeTaxes, was part of the allocations to be saved. (F.e. if that role has no accessrights of IncomeTaxes)
The contexts selectboxes for IncomeTaxes in Portal - Role allocation (Companies, Reporting Dimensions and Countries) have been restored to be multiselectboxes.
-
GTC-639ImportMapping

Situation:

If an internal row (Typ '---' in mapping, "alias") is processed, the column number is not correctly displayed when an error occurs during evaluation or validation of a mapping field (eg: because of a syntax error).

Solution:

The column number is correctly specified in an error message.

-
  • No labels