Changes for page Import Tool

Last modified by Rayaan Ahmed on 2026/04/07 10:25

From version 6.1
edited by Rayaan Ahmed
on 2026/04/07 10:25
Change comment: There is no comment for this version
To version 5.1
edited by Admin User
on 2025/06/27 12:14
Change comment: Migrated property [stableId] from class [Confluence.Code.ConfluencePageClass]

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rayaan
1 +XWiki.admin
Content
... ... @@ -61,30 +61,4 @@
61 61  
62 62  Jobs can hang for a number of reasons. Most of the time it's transient, one of the servers it is talking to has a problem... there's various reasons. It doesn't happen too frequently, and when it does, the job processes correctly the second time and the customer doesn't notice. This doesn't happen if a job takes a long time, only if it stops processing for some reason.
63 63  
64 -
65 -=== **Note on Source Code Handling in Import** ===
66 -
67 -For **import transaction types**, the source code is determined as follows:
68 -
69 -1. **Mapped Source Code in DExTr Mapper**
70 -1*. If a source code is mapped in the DExTr mapper, the system will import and assign the source code based on that mapping.
71 -1. **No Mapping, but Source Code Field Present**
72 -1*. If no source code is mapped, but the source code field is included in the mapper:
73 -1**. The import job will read the source code from the file.
74 -1**. If the source code does not already exist in the system, a new source code will be created and assigned to the record.
75 -1. **Null or Empty Source Code in File**
76 -1*. If the source code field in the import file is null or empty:
77 -1**. The system will assign the **default source code** to the transaction which is assigned on Import Tool.
78 -
79 -=== **Note on Promo Code Handling in Import** ===
80 -
81 -For **import transaction types**, the promo code is determined as follows:
82 -
83 -1. **Mapped Promo Code in DExTr Mapper**
84 -1*. If a promo code is mapped in the DExTr mapper, the system will import and assign the promo code based on that mapping.
85 -1. **No Mapping, but Promo Code Field Present**
86 -1*. If no promo code is mapped, but the promo code field is included in the mapper:
87 -1**. The import job will read the promo code from the file.
88 -1**. If the promo code does not already exist in the system, a new promo code will be created and assigned to the record.
89 -1. **Null or Empty Promo Code in File**
90 -1*. If the promo code field in the import file is null or empty than that transaction will be imported with empty promo code.
64 +