New pages
Jump to navigation
Jump to search
- 10:12, 24 November 2025 2025-11-24 ImportData Document (hist | edit) [5,912 bytes] Jammy (talk | contribs) (Created page with "= Process ImportData = == ProcessCsvFile == #Receive bucketName and fieldName. #Define the range, e.g. range = "bytes=0-5000". #Fetch data from S3 with:<syntaxhighlight lang="javascript"> { Bucket: 'izara-importdata', Key: 'csv/xxxx.csv', Range: 'bytes=0-5000' } </syntaxhighlight> #Take the importBatchId from the S3 metadata and use it to get ImportBatchMain to retrieve importConfigId. #Use the retrieved importConfigId to get CsvImportConfig. #Use the Cs...")
- 07:30, 20 November 2025 2025-11-20 IntegrationTest (hist | edit) [29,031 bytes] Mint (talk | contribs) (Created page with "= Event = eample value test")
- 00:00, 18 November 2025 Service - Delivery Method Pickup (hist | edit) [1,865 bytes] Sven the Barbarian (talk | contribs) (Created page with "= Overview = Handler service for basic pickup that use Service - Delivery Method Pickup Table for pricing and specifying pickup locations. = Repository = https://bitbucket.org/izara-market-products/izara-market-products-delivery-method-pickup = Object Schemas = ; Additional Information: Per Service Schemas == objType == === deliveryMethodPickup === * extends deliveryMethod * has versionData similar to deliveryMethodStandard to add costs and set value for...")
- 23:56, 17 November 2025 Service - Delivery Method Pickup Table (hist | edit) [2,395 bytes] Sven the Barbarian (talk | contribs) (Created page with "= Overview = Handler service for pickup location tables, works similar to rateTable, the same values can be used to calculate value for price ladder, each pickupTable instance has a list of locationIds which is where the order can be picked up from. This allows a seller with multiple branches to charge delivery fee depending on which branch the order gets picked up from. When doing deepPath search for matching locationIds use the buyer supplied locationIds to find all...")
- 13:20, 28 August 2025 2025-08-28 - Wrapping Awaiting Multiple Steps with Step (hist | edit) [1,093 bytes] Sven the Barbarian (talk | contribs) (Created page with "= Overview = Rule for Awaiting Multiple Steps (AMS) is we must save all AMS before sending any async requests (eg to other flows) to protect against the sent requests returning before saving all AMS causing a race condition where the parent task completes because it thinks all steps are complete but actually they have not been saved yet. This is not efficient for large scale processes such as ImportBatch. Solution is to add a special step into the main AMS group befor...")