-
Notifications
You must be signed in to change notification settings - Fork 0
2.3 Functionalities ‐ Diarynotes
ℹ️ Only transactions of transactiontype "Diarynote" can be used for input. Any other transactiontype will be ignored.
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 Diarynote transactions within a kmehrmessage does not have an EVS REF yet, an EVS REF will be generated.
This action will export the contents of the vault that belong to transactiontype "Diarynote", without any change to the vault itself. EVS will do this action once for each dropped file, without parsing this file.
This action will generate an EVS REF for each Diarynote transaction currently in the vault.
- If an EVS REF exists already in the Diarynote transaction, no new EVS REF will be generated.
- If no EVS REF exists, the new EVS REF is put in the first Text or TextWithLayout field. If none of these exists, a new TextWithLayout field is created.
This action will update the transactions that belong to transactiontype "Diarynote" identified by the EVS REF in the input file.