Compliance middleware image review#20
Draft
volllly wants to merge 1 commit into
Draft
Conversation
| I think this one is kind of correct... maybe step 4 comes before step 3. | ||
| But I'm not sure this is still how we want to communicate it as we now have the accademy where most of that is tackled I think. | ||
| --> | ||
|
|
| The term that we use internally for those is "Secure Signature Creation Device" (SSCD). | ||
| SSCD is used in some [other graphics](https://docs.fiskaltrust.eu/docs/poscreators/middleware-doc/general/cash-register-integration/failure-scenarios#failure-scenarios) aswell if I remember correctly but it's maybe not quite self explanatory. | ||
| --> | ||
|
|
4 tasks
| The SCU that's shown here the "fiskaltrust.Middleware.SCU.DE.Fiskaly" has been deprecated replaced with the "fiskaltrust.Middleware.SCU.DE.FiskalyCertified". | ||
| Also we should probably not show an `-rc` version but a normal one with out a prerelease prefix. | ||
| --> | ||
|
|
| <!-- | ||
| We should also not show an `-rc` version here. | ||
| --> | ||
|
|
| The SCU that's shown here the "fiskaltrust.Middleware.SCU.DE.Fiskaly" has been deprecated replaced with the "fiskaltrust.Middleware.SCU.DE.FiskalyCertified". | ||
| Also we should probably not show an `-rc` version but a normal one with out a prerelease prefix. | ||
| --> | ||
|
|
| We should also not show an `-rc` version here. | ||
| --> | ||
|
|
||
|
|
| Under the menu item ``Configuration -> CashBox`` you will find the button to create a new CashBox. Press this button to get to the input form. After entering a short description (name) press the "Save" button. The CashBox has been created and now appears in the list. | ||
|
|
||
|  | ||
|
|
| This button is still valid in FR and AT but in all of the other market's there's a download button with a popup. | ||
| This download button and popup will also be enabled in AT and FR at some point in the maybe not so near future. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
| Should maybe say "SSCD communication failure". | ||
| Also what should be printed (last step) on the receipt depends on the market and is is returned by the queue in the response signatures. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
| "TSE" is mentioned again. | ||
| And I think the "list of requests that could not be signed by the TSE" is not applicable for all markets so we can probably remove it. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
| <!-- | ||
| What the POS has to do/print (last step) kind of depends on the market. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
|
|
||
| <!-- The receipt request flag presented here is the v1 flag. In v2 it's 0x0000000080000000. --> | ||
|
|
||
| ::: |
| That's all handled by the possystem api and the v2 tagging. | ||
| Also the mapping table below is obsolete when using the v2 tagging with the possystem api. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
n/a (this topic has been removed from the docs)
| Again an -rc version is shown. | ||
| We should probably show a rest url as that's the most commonly used option. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
|  | ||
|
|
||
| <!--Also correct but in reality/the future the PosSystem api digital receipt etc. wil probably also be a player here. --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
| I think this one needs to be reworked for v2 and with the digital receipt. | ||
| It's broadly correct but there's kind of more to it. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
| That's all handled by the possystem api and the v2 tagging. | ||
| Also the mapping table below is obsolete when using the v2 tagging with the possystem api. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
n/a - topic has been removed from the docs.
| Again an -rc version is shown. | ||
| We should probably show a rest url as that's the most commonly used option. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Updated image for review.
| Now in most markets (all except AT and FR) there is one download button that opens a popup with those options. | ||
| Actually, the whole content of this page is only correct for AT, FR and DE. As the new markets (will) also use the new launcher. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
Worked on the page content.
@volllly Please confirm: IT column should be removed from the table under Download of the Launcher section?
| <!-- | ||
| I think we should mention the cloudcashbox here as well. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
@volllly Do you mean mentioning Cloud CashBox as an example of an off-premise/private-cloud deployment, or adding it as a separate operation mode in the diagram?
| <!-- | ||
| Those four workflow diagrams are I guess technically correct but I don't know how helpful they are to understand what's going on. | ||
| --> | ||
|
|
Contributor
There was a problem hiding this comment.
@volllly the workflow under Workflow - regular operation has been updated.
For the other three (special receipts, failure of communication, and failure of the fiskaltrust.Middleware - timeout), do you suggest keeping them anyway? If so, I'd rework on the image quality.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Changes are being tracked under the PR #54 - @deboragracio