Update Requests; "Group Id" added to finUpdateRequestBase to link multiple requests together

Previously, Update Requests could not be linked to one another, aside from being within the same Log. Some scenarios, such as replacing two separate addresses with one (e.g., 1 Postal and 1 Physical, combined into a new address), may require further linking options.

Group Id has been added to finUpdateRequestBase which allows Update Requests to be assigned a group. This provides a mechanism to link Update Requests at a more granular level rather than just being in the same Log.

The following helper functions have also been added to finUpdateRequestActions to allow approve / decline options by group:

• ExecuteActionGroup(groupId)
• ExecuteDeclineGroup(groupId)

Additionally, the following helper functions in finUpdateRequestUtilities have been enhanced to allow the Script to decline (see note below) related group items:

• ApproveDeclineAccountUpdateRequest
• ApproveDeclineClientUpdateRequest

Note: Initially, the option to also action related items is limited to declining Update Requests. Typically, only finPOWER Connect Users will be approving items, and this occurs through the form or HTML Widget. In this case each item should be processed individually via the interface. External Users / Clients should ideally only be able to decline requests (e.g., cancel an Address Update from a Portal) and therefore this functionality ensures that all related items are cancelled.

The new function, finUpdateRequestUtilities.CreateUpdateRequestLog_AddressUpdates_FromAddressDetails(), has been enhanced to set the Group Id to "PostalRetired" if it is retiring a Postal address when creating a new Physical & Postal address.