Skip to content

Create PosSystem migration guide#34

Open
deboragracio wants to merge 10 commits into
mainfrom
add-migration-documentation-for-v2
Open

Create PosSystem migration guide#34
deboragracio wants to merge 10 commits into
mainfrom
add-migration-documentation-for-v2

Conversation

@deboragracio
Copy link
Copy Markdown
Contributor

  • You've read the Contributor Guide and Code of Conduct.
  • You've included unit or integration tests for your change, where applicable.
  • You've included inline docs for your change, where applicable.
  • There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Description

Details can be found on https://github.com/fiskaltrust/engineering/issues/1116

@deboragracio deboragracio requested a review from a team as a code owner May 7, 2026 13:03
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 7, 2026

⚠️ CLA Signature Required

Thank you for your contribution! Before we can merge this PR, the following contributor(s) need to sign our Contributor License Agreement:

  • @Copilot

How to sign

Please read the CLA document and then comment on this PR with the following text:

I have read the CLA Document and I hereby sign the CLA

@deboragracio
Copy link
Copy Markdown
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@deboragracio deboragracio requested a review from LGuichet May 7, 2026 15:24
@LGuichet
Copy link
Copy Markdown
Contributor

LGuichet commented May 19, 2026

  • Review the content (bullet points) under the Introduction and Prerequisites sections for accuracy.

  • Under Prerequisites, confirm whether the caution note “Market availability” is correct and relevant here. If so, please confirm whether there is any constraints for Germany (DE).

  • 3. Confirm whether the Architecture Overview section is relevant here, as well as its content is accurate.

  • 4. Review the content of the Cloud CheckBox (base URL change) section.

  • 5. Review the content of the Case Values section. Before updating the v2 values used for ftReceiptCase, ftChargeItemCase, and ftPayItemCase, I want to confirm whether we should list them directly on this new page or simply refer the https://github.com/fiskaltrust/service-possystem-api/blob/main/doc/mapping-v2-v0/readme.md file. Note that if we decide to list them directly in the guide, we must keep them synchronized whenever updates are made to the .md file, and also make it public. This is the format I would use to display them on the docs page:

Image
Image
  • 6. In the .md file, I can see that ftSignatureType and ftStare are listed for each market. Should we include them under Case Values as well?

  • 7. Review the content of the following sections: ftReceiptCaseData Format, ReceiptRequest, ReceiptResponse, and Timestamps.

  • 8. Review the content of the Local CashBox section.

  • 9. Confirm whether the API changes section is relevant for this guide.

@arnaud-chentil
Copy link
Copy Markdown

I have read the CLA Document and I hereby sign the CLA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants