This repository was archived by the owner on Feb 26, 2026. It is now read-only.
Users/aedler/appendix de cash register integration patches#146
Merged
TSchmiedlechner merged 10 commits intoJan 25, 2021
Merged
Conversation
DoxaPap
reviewed
Jan 14, 2021
| # Appendix: DE - KassSichV | ||
|
|
||
| This appendix expands on the information provided in the General Part by adding details specific to the German market. This additional information is provided only where applicable. The remaining chapters, for which there is no additional information required, were omitted. | ||
| This appendix expands on the General Part's information by adding details specific to the German market. This additional information is provided only where applicable. The remaining chapters, for which there is no further information required, were omitted. |
There was a problem hiding this comment.
I liked it better the way it was before :D so information provided in the General Part section.
DoxaPap
reviewed
Jan 14, 2021
DoxaPap
reviewed
Jan 14, 2021
DoxaPap
reviewed
Jan 14, 2021
| ### Receipt Creation Process | ||
|
|
||
| This chapter describes the general process of creating receipts with fiskaltrust.Middleware and its workflow, in accordance with the German law. It requires to give a scope to an ongoing action over time. This scope is named a transaction. Calls to fiskaltrust.Middleware are processed just in time and cannot be async over multiple minutes. Therefore and in accordance with German law, a single call is maybe not able to scope a complete transaction. To solve this, multiple calls are used, scoping the same transaction. | ||
| This chapter describes the general process of creating receipts with fiskaltrust.Middleware and its workflow, following German law. It requires to give a scope to an ongoing action over time. This scope is named a transaction. Calls to fiskaltrust.Middleware are processed just in time and cannot be async over multiple minutes. Therefore and in accordance with German law, a single call is maybe not able to scope a complete transaction. To solve this, multiple calls are used, scoping the same transaction. |
There was a problem hiding this comment.
This scope is named a transaction. Calls to fiskaltrust.Middleware are processed just in time and cannot be async over multiple minutes. >> I don understand, the name of the scope described is "transaction"?.
The part over multiple minutes is not very clear to me either. It meant that they cannot be processed asynchronously? If so, the "async over multiple minutes" could be replaced with "cannot be processed asynchronously". besides, async is not a verb or an adjective!
Contributor
Author
There was a problem hiding this comment.
i also do not understand this part...
DoxaPap
reviewed
Jan 14, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.