Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: communicationRequest to edition File #71

Merged
merged 11 commits into from
Oct 25, 2024

Conversation

SimonDmz
Copy link
Contributor

No description provided.

@SimonDmz SimonDmz force-pushed the feature-generate-xml-from-communication-requests branch from 9639475 to 50d4265 Compare October 16, 2024 09:08
@@ -221,7 +222,7 @@ public BatchErrorCode handleCommunications() throws SynchronizationException, Mi
variables.setBarcode(barCode);

// Set InitAccuseReception based on some business logic
variables.setInitAccuseReception(template.isInitAccuseReception());
variables.setInitAccuseReception(template.isInitAccuseReception()?"oui":"non");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indent ?

Copy link

sonarcloud bot commented Oct 24, 2024

@SimonDmz SimonDmz merged commit d4fb67f into develop Oct 25, 2024
2 checks passed
SimonDmz added a commit that referenced this pull request Oct 25, 2024
* feat: communicationRequest to edition File

* feat: interviewer title synchro

* fix: back to javax.xml imports

* fix: resolve Jaxb Factory bug

* fix: resolve Jaxb Factory bug again

* fix: resolve Jaxb bug even more

* fix: person title mapping

* feat: allow natural splitting
fix: prevent "null" serialization in address fields

* fix: handle api call error and file move error independently

* fix: truncate overflowing L3 at 38 chars, don't include null as string in address

* fix: clean sql in string block, remove unused code
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.

3 participants