Article Details
Id: | 17989 |
Product: | finPOWER Connect |
Type: | NEW |
Version: | 3.04.00 |
Opened: | 26/03/2021 |
Closed: | 31/03/2021 |
Released: | 30/06/2021 |
Job: | J026232 |
finUpdateRequestUtilities.CreateUpdateRequestLog_AddressUpdates_FromAddressDetails() has now been implemented
finUpdateRequestUtilities.CreateUpdateRequestLog_AddressUpdates_FromAddressDetails() would previously immediately error stating that it had not yet been implemented. It has now been implemented and supports the individual processing of Physical and Postal addresses in the single Update Request Client Log.
The following update scenarios are supported.
- Add new Physical address
- Add new Postal address
- Add new Physical & Postal address (where they are the same)
- Add new Physical & Postal address (where they are different)
- Update existing Physical and / or Postal addresses
- Delete existing Physical and / or Postal addresses
- Convert previously different Physical & Postal addresses into a single Physical & Postal address
- This will mark the old Postal address record as historic
The function accepts a number of Parameters which dictate which action will be performed. Only the optional Parameters which define the action are mentioned below.
physicalClientContactAddressPk, postalClientContactAddressPk
- The Pks of existing Client Contact Addresses
- Only required if updating an existing value
physicalAddressDetails, postalAddressDetails
- The new address(es)
- Should be a initialised (but blank) object if deleting
postalAndPhysicalAddressSame
- Determines if the Physical address supplied should also be flagged as Postal
- If postalAddressDetails has been supplied and this value is set to "True" it will be ignored
newPhysicalContactMethodId, newPostalContactMethodId
- Contact Method Ids for new Client Contact Addresses
- Only required if adding new