Compare commits

...

68 Commits

Author SHA1 Message Date
a09ff435a7 Merge branch 'release/2.0' into 'main'
Release/2.0 -> Main-2.0

See merge request r-d-technique/tiers/tdi-connector!22
2025-12-18 08:12:22 +00:00
bf4f470038 Release 2.0.21+1 2025-12-18 09:04:45 +01:00
d3c8f8d143 Merge branch 'ftl-for-version-1.12' into 'release/2.0'
Ftl for version 1.12

See merge request r-d-technique/tiers/tdi-connector!21
2025-12-18 07:50:12 +00:00
abb26db4ec Merge branch 'develop' into ftl-for-version-1.12
# Conflicts:
#	README.md
2025-12-18 08:31:38 +01:00
50e1d27af5 Release 2.0.20+1 2025-11-26 09:39:25 +01:00
a17961ce5a brand 2025-10-21 10:31:21 +02:00
f2e599bfba Hardis SC 2025-10-16 10:02:59 +02:00
80bf92b631 HARDIS SC NETWORK 2025-10-13 15:33:55 +02:00
d77f0e8ff6 Merge branch 'release/2.0' into 'main'
Release/2.0 -> Main-2.0

See merge request r-d-technique/tiers/tdi-connector!18
2025-08-26 14:43:30 +00:00
a121b9badb Release 2.0.19+1 2025-08-26 16:22:43 +02:00
6961ad4fe0 Merge branch 'v11-connector-2.0' into 'release/2.0'
v11-connector-2.0

See merge request r-d-technique/tiers/tdi-connector!17
2025-08-26 13:54:11 +00:00
4b26006fe0 Merge branch 'develop' into v11-connector-2.0
# Conflicts:
#	README.md
#	TDItoRP.ftl
#	VERSION
2025-08-26 15:46:27 +02:00
69a841f77b Release 2.0.18+1 2025-08-26 11:02:32 +02:00
cbf41cd4e0 update TrackingETA field 2025-08-18 10:48:43 +02:00
Labib Takouti
95675b3f30 Merge branch 'feature/auto-licence' into 'develop'
auto update licences

See merge request r-d-technique/tiers/tdi-connector!16
2025-07-07 11:42:32 +00:00
ltakouti
b86280b4f8 auto update licences 2025-07-07 11:28:44 +02:00
a6a004545f suppression fichier 2025-07-04 11:05:39 +02:00
1e77bbdaf6 SCPN1-9007 2025-07-04 10:47:44 +02:00
95f67c4c0c Modifs TDI LMO 2025-07-01 17:31:10 +02:00
4d5c2be5f2 modi 2025-07-01 11:32:16 +02:00
987892baae Test 2025-07-01 11:31:53 +02:00
c1eb45abb4 Merge branch 'release/2.0' into 'main'
MR->main

See merge request r-d-technique/tiers/tdi-connector!15
2025-04-19 21:42:08 +00:00
948fa7178d Release 2.0.17+1 2025-04-14 12:09:16 +02:00
5f41403857 Release 2.0.16+1 2025-04-14 12:08:41 +02:00
11188d132e Merge branch 'release/2.0' into 'main'
MR->main

See merge request r-d-technique/tiers/tdi-connector!14
2025-04-14 08:46:38 +00:00
1a84e1ae5f re revert pour la MR->Main 2025-04-11 15:47:16 +00:00
249a81ce7b SCPN1-8601
(cherry picked from commit ff72d30b18aa081287c94fd88f1a951c08721179)
2025-04-11 17:26:50 +02:00
c19f414cc5 revert suite au scpn1-8106 2025-04-11 14:58:36 +00:00
d9a3666dde Release 2.0.15+2 2025-04-11 16:55:37 +02:00
dfe1b74ab2 Edit VERSION for jira SCPN1-8601 2025-04-11 14:42:54 +00:00
9dfe72ee02 Merge branch 'SCPN1-8601' into 'release/2.0'
correction pour la v9 et v10 connecteur TDI

See merge request r-d-technique/tiers/tdi-connector!13
2025-04-11 14:02:06 +00:00
ff72d30b18 SCPN1-8601 2025-04-11 15:57:29 +02:00
6a9caba0e9 SCPN1-8601
(cherry picked from commit 9d16833c49095f9d6e5870c11d52df93f854169b)
2025-04-10 17:16:52 +02:00
9d16833c49 SCPN1-8601 2025-04-10 09:55:51 +02:00
02e5b9af0e Edit VERSION 2025-04-08 07:59:34 +00:00
c108498368 Snapshot tdi-connector 2.2.0-SNAPSHOT 2025-04-08 09:58:27 +02:00
c779c182a2 Release 2.0.16+1 2025-04-07 12:30:21 +02:00
7ca12ebd36 Merge branch 'to-visibilty-10' into 'release/2.0'
to v10

See merge request r-d-technique/tiers/tdi-connector!12
2025-04-07 09:33:33 +00:00
188e2e289d update URL in readme.md
(cherry picked from commit 2f24b0328d9f98cb4ae7a4e357eb9e8c83bf0ca6)
2025-03-12 16:39:50 +01:00
2f24b0328d update URL in readme.md 2025-03-12 16:39:01 +01:00
b60c69e148 Merge branch 'develop' into to-visibilty-10
# Conflicts:
#	TDItoRP.ftl
#	VERSION
2025-03-06 18:25:20 +01:00
c45291bc78 SCPN1-8341 2025-02-28 14:52:55 +01:00
006d5c48c3 SCPN1-8384
(cherry picked from commit 0fcf1f7ac05e333a7d3c64b9873e511fb33da29e)
2025-02-24 10:28:24 +01:00
322bb0df69 Merge branch 'release/2.0' into 'main'
MR->main

See merge request r-d-technique/tiers/tdi-connector!11
2025-02-18 10:08:26 +00:00
0e271167b7 Merge branch 'main' into 'release/2.0'
# Conflicts:
#   TDItoRP.ftl
2025-02-18 09:25:56 +00:00
9462439713 Release 2.0.15+1 2025-02-18 10:02:33 +01:00
dddee7e7b7 Merge branch 'SCPN1-8340' into 'release/2.0'
Resolve SCPN1-8340

See merge request r-d-technique/tiers/tdi-connector!10
2025-02-18 08:59:07 +00:00
bd7cf03026 SCPN1-8347
(cherry picked from commit 01914593ab52172d520b4e40661b0c62e003db83)
2025-02-17 17:48:15 +01:00
01914593ab SCPN1-8347 2025-02-17 17:22:44 +01:00
934463db19 SCPN1-8340 et SCPN1-8347
(cherry picked from commit cef7c9aeda733905d9fa271cb02a9fb707a49c72)
2025-02-17 14:32:08 +01:00
545f8002b5 SCPN1-8340 et SCPN1-8347
(cherry picked from commit cef7c9aeda733905d9fa271cb02a9fb707a49c72)
2025-02-17 14:29:35 +01:00
cef7c9aeda SCPN1-8340 et SCPN1-8347 2025-02-17 14:22:41 +01:00
547ba029c8 Merge branch 'release/2.0' into 'main'
MR->main

See merge request r-d-technique/tiers/tdi-connector!9
2025-02-06 17:14:37 +00:00
969d42ac4a Release 2.0.14+1 2025-02-06 15:57:14 +01:00
3be6f84bbb Merge branch 'SCPN1-8181' into 'release/2.0'
SCPN1-8181

See merge request r-d-technique/tiers/tdi-connector!8
2025-02-06 14:45:05 +00:00
ea068df3c0 SCPN1-8181
(cherry picked from commit a7b7decf78f9929ce378566a7ba98d0ac7e49f1b)
2025-01-20 15:54:41 +01:00
a7b7decf78 SCPN1-8181 2025-01-20 15:50:35 +01:00
ac66ef14f8 Merge branch 'release/2.0' into 'main'
Release/2.0

See merge request r-d-technique/tiers/tdi-connector!7
2024-12-15 11:21:01 +00:00
00cda1dcd8 Release 2.0.13+1 2024-12-13 15:33:51 +01:00
79f199e0b1 Release 2.0.12+1 2024-12-03 14:46:55 +01:00
b2c45ae6c0 Merge branch 'release/2.0' into 'main'
Release 2.0.10+1

See merge request r-d-technique/tiers/tdi-connector!6
2024-05-02 09:48:39 +00:00
92bd1de865 Merge branch 'release/2.0' into 'main'
Release/2.0

See merge request r-d-technique/tiers/tdi-connector!5
2024-04-06 07:27:07 +00:00
d1999bd81a reverted VERSION 2024-03-12 08:28:20 +00:00
c7389871de Snapshot tdi-connector 2.2.0-SNAPSHOT 2024-03-11 17:11:52 +01:00
d301169ca7 Merge branch 'release/2.0' into 'main'
Release 2.0.2+1

See merge request r-d-technique/tiers/tdi-connector!3
2023-11-23 09:27:18 +00:00
63643cdca8 Merge branch 'release/2.0' into 'main'
Release/2.0

See merge request r-d-technique/tiers/tdi-connector!2
2023-11-06 16:15:58 +00:00
587d6b0af9 Merge branch 'release/2.0' into 'main'
Release/2.0

See merge request r-d-technique/tiers/tdi-connector!1
2023-10-26 12:56:01 +00:00
29ee071a66 Snapshot tdi-connector 2.1.0-SNAPSHOT 2023-10-24 16:44:03 +02:00
7 changed files with 155 additions and 143 deletions

21
LICENCE Normal file
View File

@ -0,0 +1,21 @@
MIT License
Copyright (c) 2025 Hardis Supply Chain
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

View File

@ -1,92 +1,4 @@
# tdi-connector
You can find more info about tdi-connector in the HARDIS SC NETWORK documentation center : https://docs.viz.reflex-platform.com/connectivity/partnerapp/tdi-connector/
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://gitlab.hardis-group.com/r-d-technique/tiers/tdi-connector.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://gitlab.hardis-group.com/r-d-technique/tiers/tdi-connector/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

View File

@ -4,54 +4,34 @@
<#assign tdiEvent64b = JsonUtil.decodeBase64(tdiEventMsg.data) />
<#assign tdiEvent = JsonUtil.jsonToMap(tdiEvent64b)>
{"Header":
<#assign senderTag = tdiEventMsg.senderTag>
<#if tdiEvent.Target == 0 || (tdiEvent.Target == 1 && tdiEvent.ParcelNumber?? && tdiEvent.ParcelNumber == "")>
<#stop>
<#else>
[
{
"ProjectID": "${projectRP}"
},
"ID":
{
"RefID": "${tdiEvent.HUReference1}"
},
"Payload":
{"Events": [
<#-- {"Date": {"DateTime": "${tdiEvent.EventDate?datetime.iso?iso_utc}", -->
{"Date": {"DateTime": "${tdiEvent.EventDate}",
"AuthorTimeZone": "UTC"
},
<#if tdiEvent.EventCode?starts_with("T-") == true ||
tdiEvent.EventCode == "OK-COLLECTED" ||
tdiEvent.EventCode == "OK-IN-TRANST" ||
tdiEvent.EventCode == "OK-OUT-FOR-D" ||
tdiEvent.EventCode == "OK-WITHDRAWA" ||
tdiEvent.EventCode == "OK-EDI" >
"Code": "TRACKING_EVENT_IFTSTA_13", <#-- Acheminement conforme -->
<#else>
<#if tdiEvent.EventCode?starts_with("D-") == true ||
tdiEvent.EventCode == "OK-DELIVERED" >
"Code": "TRACKING_EVENT_IFTSTA_21", <#-- Livraison conforme -->
<#else>
<#if tdiEvent.EventCode?starts_with("DC") == true ||
tdiEvent.EventCode?starts_with("DN") == true ||
tdiEvent.EventCode?starts_with("DR") == true >
"Code": "TRACKING_EVENT_IFTSTA_56",<#-- Livraison non aboutiee -->
<#else>
<#if tdiEvent.EventCode?starts_with("TD") == true ||
tdiEvent.EventCode?starts_with("TA") == true >
"Code": "TRACKING_EVENT_IFTSTA_53",<#-- Acheminement non réalisé -->
<#else>
<#if tdiEvent.EventCode == "OK-IN-TRANST" >
"Code": "TRACKING_EVENT_IFTSTA_5",<#-- Acheminement en cours -->
<#else>
"Code": "TRACKING_EVENT_UNKNOWN",
</#if>
</#if>
</#if>
</#if>
</#if>
"Reason": "${tdiEvent.EventLabel}"
<#assign apiReflexPlatformID = ApiReflexPlatformID.TrackingNotified>
"apiReflexPlatformID" : "${apiReflexPlatformID}",
"datas" :
<#include "TDItoRP_TrackingNotified.ftl">
}
<#if tdiEvent.EstimatedDeliveryDate?? && tdiEvent.EstimatedDeliveryDate!="">
,
{
<#assign apiReflexPlatformID = ApiReflexPlatformID.TrackingETAUpdated>
"apiReflexPlatformID" : "${apiReflexPlatformID}",
"datas" :
<#include "TDItoRP_TrackingETAUpdated.ftl">
}
</#if>
<#if tdiEvent.TrackingUrl?? && tdiEvent.TrackingUrl!="">
,
{
<#assign apiReflexPlatformID = ApiReflexPlatformID.TrackingURLUpdated>
"apiReflexPlatformID" : "${apiReflexPlatformID}",
"datas" :
<#include "TDItoRP_TrackingURLUpdated.ftl">
}
</#if>
]
}
}
</#if>

View File

@ -0,0 +1,22 @@
[
{
"Header": {
"ProjectID": "${projectRP}"
},
"ID": {
"RefID": "${tdiEvent.ParcelNumber}"
},
"Payload": {
"TrackingETA": {
"EndETA": {
"AuthorTimeZone": "UTC",
"DateTime": "${tdiEvent.EstimatedDeliveryDate}"
},
"StartETA": {
"AuthorTimeZone": "UTC",
"DateTime": "${tdiEvent.EstimatedDeliveryDate}"
}
}
}
}
]

View File

@ -0,0 +1,64 @@
[
{
"Header":
{
"ProjectID": "${projectRP}"
},
"ID":
{
"RefID": "${tdiEvent.ParcelNumber}"
},
"Payload":
{
"Events": [
<#-- {"Date": {"DateTime": "${tdiEvent.EventDate?datetime.iso?iso_utc}", -->
{
"Date": {
"DateTime": "${tdiEvent.EventDate}",
"AuthorTimeZone": "UTC"
},
<#if tdiEvent.EventCode == "OK-COLLECTED" ||
tdiEvent.EventCode == "OK-EDI" ||
tdiEvent.EventCode == "OK-APPT-DATE" ||
tdiEvent.EventCode == "OK-APPT-NOTI" ||
tdiEvent.EventCode == "OK-APPT-NEED" ||
tdiEvent.EventCode == "ADM" ||
tdiEvent.EventCode == "RGP" >
"Code": "TRACKING_EVENT_IFTSTA_349", <#-- Handled by carrier -->
<#else>
<#if tdiEvent.EventCode?starts_with("TA") >
"Code": "TRACKING_EVENT_IFTSTA_56", <#-- Incomplete delivery -->
<#else>
<#if tdiEvent.EventCode?starts_with("T-") == true ||
tdiEvent.EventCode?starts_with("TD") == true ||
tdiEvent.EventCode == "OK-OUT-FOR-D" ||
tdiEvent.EventCode == "OK-IN-TRANST" >
"Code": "TRACKING_EVENT_IFTSTA_113",<#-- Delivery in progress -->
<#else>
<#if tdiEvent.EventCode?starts_with("D-") == true ||
tdiEvent.EventCode == "OK-DELIVERED" ||
tdiEvent.EventCode == "POD" ||
tdiEvent.EventCode == "FAC" ||
tdiEvent.EventCode == "OK-WITHDRAWA" >
"Code": "TRACKING_EVENT_IFTSTA_21",<#-- Process Completed -->
<#else>
<#if tdiEvent.EventCode?starts_with("DC") == true ||
tdiEvent.EventCode?starts_with("DN") == true ||
tdiEvent.EventCode?starts_with("DR") == true ||
tdiEvent.EventCode?starts_with("C-") == true ||
tdiEvent.EventCode == "SUP" ||
tdiEvent.EventCode == "NEX" >
"Code": "TRACKING_EVENT_IFTSTA_14",<#-- Delivery completed -->
<#else>
"Code": "TRACKING_EVENT_UNKNOWN",
</#if>
</#if>
</#if>
</#if>
</#if>
"Reason": "${tdiEvent.EventLabel}"
}
]
}
}
]

View File

@ -0,0 +1,13 @@
[
{
"Header": {
"ProjectID": "${projectRP}"
},
"ID": {
"RefID": "${tdiEvent.ParcelNumber}"
},
"Payload": {
"TrackingURL": "${tdiEvent.TrackingUrl}"
}
}
]

View File

@ -1 +1 @@
2.0.11+1
2.0.21+1