2.2 Functionalities ‐ Sumehr

Which actions for Sumehr?

ℹ️ Only transactions of transactiontype "Sumehr" can be used for input. Any other transactiontype will be ignored.

Action "add"

This action will add a transaction to the vault for all transactions found in each Kmehrmessage found in all dropped files. If one of the Sumehr transactions within a kmehrmessage does not have an EVS REF yet, an EVS REF will be generated.

In the example below, 3 transactions are dropped in the add folder to be added to the vault:

Action "empty"

This action will remove all transactions from the vault that belong to transactiontype "Sumehr". EVS will do this action once for each dropped file, without any parsing.

In the example below, a newly created file will trigger emptying of the vault by removing all existing transactions of transactiontype "Sumehr":

Action "export"

This action will export the contents of the vault that belong to transactiontype "Sumehr", without any change to the vault itself. EVS will do this action once for each dropped file, without parsing this file.

In the example below, a newly created file will trigger an export of the contents of the vault of transactiontype "Sumehr":

Action "generateRef"

This action will generate an EVS REF for each Sumehr transaction currently in the vault.
ℹ️ The 'old' EVS, with Vitalink connector-integration, added the references to the input file, followed by putting this in the vault.

• If an EVS REF exists already in the Sumehr transaction, no new EVS REF will be generated.
• If no EVS REF exists, the new EVS REF is put in the first text field.

Action "removeRef"

This action will remove the transactions that belong to transactiontype "Sumehr" identified by the EVS REF in the input file from the vault.

Action "replace"

This action will replace the contents of the vault that belong to transactiontype "Sumehr" by all the transactions found in the input file. Be aware of the fact that dropping multiple files in the replace-folder will result in a vault with as contents the transactions of the last input file! If one of the Sumehr transactions within a file does not have an EVS REF yet, this will be generated.

In the next example, after processing the next 3 input files, the vault contains 4 transactions.

Action "updateRef"

This action will update the transactions that belong to transactiontype "Sumehr" identified by the EVS REF in the input file.