I have an email from Dev team: We recently found that CoreLOG CIP Integration has an…
- User
I have an email from Dev team: We recently found that CoreLOG CIP Integration has an issue with how the address is synced from CIP to CoreLOG. Specifically, the latest active address is used but the type of address – Physical Address or Mail Address - is not checked. This can result in Mail Address from CIP being brought onto the CoreLOG account. Whether this is the problem can be determined by looking at the Address IDs of addresses – if active Mail Address has an Account ID bigger than the one on active Physical Address it will get used for CoreLOG account.
The fix for this is in the pipeline and we will be able to solve these issues after the next CoreLOG release. Until then, please let us know of any such tickets and we will keep a list to be updated (by re-linking) after next release once the issue is resolved.
Could you please simplify it so I could provide a reply to a non-technical person (regular user)
- Assistant
Certainly! Here’s a simplified version of the email you can share with a non-technical person:
Simplified Explanation:
We found a problem with how addresses are copied from one system (CIP) to another (CoreLOG). Right now, the system picks the most recent address but doesn’t check if it’s a physical address or a mailing address. Because of this, sometimes a mailing address is used where a physical address should be.
We have a fix planned and it will be included in the next CoreLOG update. Until then, if you notice any issues with addresses, please let us know. We will keep track of these and fix them after the update.
Would you like me to help you draft a reply based on this?
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.