ESB-33088-On-Prem changes toInventory message publisher to correct the bug for UAP DC inventory updates
ESB-32444-[Inv-Message-Publisher] Suppress Fields in Pub/Sub Message which are not part of incoming message
ESB-32369 - Updated code to map empty string for part description when null value is passed from source
ESB-32369 - Updated code to trim product code and product number before publishing inventory records to pubsub
ESB-32369 - Map timestamp from header in absence of part level data as of timestamp
ESB-32347 - Updated code to publish inventory data only to useast-4 regional endpoint
ESB-32267 - Updated code to stop publishing inventory data for store and dc that doesn't belong to US and CA
ESB-32247 - Added functionality to add country code for Altrom files
ESB-32226 - made code changes to accept Single value as an array value
ESB-32200 - Enhanced code to publish messages to pubsub in asynchronous manner
ESB-32073 - Removed logic of log4j configurator initialization
ESB-32073 - Added logic to translate "UAP DC Number" to "DC Abbreviation Code" in InventoryEvent location mapping for FES DC inventory requests
ESB-31774 - Added isLogToFileEnabled property to enable/disable logging faile/succes records. Also, added annotation to treat single value as an array
ESB-31774 - Updated code to write failed and success inventory records to file
ESB-31253 - Disabled Spring auto configuration by updating property
ESB-31253 - Added property gcp-service-account and remove gcp cloud credentials location property
ESB-31253 - Removed property gcp-service-account and added gcp cloud credentials location
ESB-31253 - Updated DCInventory request model
ESB-31253 - Added arrayList type for Responder
ESB-31253 - Modified incorrect datatype for orderSupspenseCode and removed arrayList types on RequestorIdentifier, ResponderIdentifier and Responder
ESB-31253 - Made code changes to authenticate gcp project with service account
ESB-31253 - Refactored code and added unit test cases
ESB-31253 - Added unit test cases
Got a suggestion or an issue? Discuss it in our forums or visit our support website for other options.