Known Issues

Below is a list of known issues that will be addressed in a future release:

• Trying to replace an Ad Hoc Group recipient with one of its members results in an error. (refs PB-113465)

• If one member of an ad hoc group accepts the e-consent document, the remaining members will not be presented with the e-consent document if they do not also have individual signatures. (refs PB-112544)

• If a recipient is both an individual signer and part of a Reviewer ad hoc group, they will receive the email invitation to sign as a reviewer instead of a signer. (refs PB-112225)

• When trying to confirm a document having a signature for an individual signer who is also a member of an ad hoc group having an accept-only signature on the same document, an error is thrown stating not all signatures are accepted. (refs PB-112293)

• Geolocation events are added to the Evidence Summary document for Ad Hoc Groups once the transaction is completed. (refs PB-113555)

• When an individual recipient, who has a field without a signature associated to them and is also a member of an ad hoc group having a signed signature, attempts to confirm their document, they will be presented with an error about a missing approval. (refs PB-1113797)

• You are able to remove a member of an ad hoc group from the API (only) even if the Ad Hoc Group has accepted/signed signatures as long as those signatures were not accepted/signed by the member you are removing.  The same is not possible from the sender interface. (refs PB-113353)

• It is not possible to replace an Ad Hoc Group with a Sender Group when the Ad Hoc Group account feature is disabled. (refs PB-113976)

• There is a misalignment between the Ad Hoc Group/Member recipient row and their respective More Actions button on smaller screens. (refs PB-113539)

• The out of office email shows the ad hoc group email instead of the member email. (refs PB-113771)

• The audit trail sometimes displays the incorrect member name when an account sender is added as an ad hoc member and their first name/last name is set to a different name. (refs PB-113749)

• Email validation is not performed as part of the pre-processing when adding multiple members to an ad hoc group (Groups call). As such if an error occurs with one entry, the saved members will not be removed. (refs PB-113748)

• It is possible to replace an individual recipient who is also a group member by the Myself recipient by typing in their information.  The individual recipient gets replaced, but the members do not. (refs PB-114060)

• Validation of supported languages is not performed for ad hoc group recipient when created from the API. (refs PB-114179)

• Accessibility is not fully implemented with Ad Hoc Groups within the Sender UI.

• After replacing an ad hoc group by a sender group using the Recipient Settings modal, if you try to update the signing order before refreshing the page an error appears. (refs PB-114662)

• Members of an ad hoc group that were replaced using the Recipient Settings modal will continue to appear within the Recipients section of the Transaction Edit until you refresh the page. (refs PB-114660)

• An error appears and the signing order is not enabled when replacing an Ad Hoc Group recipient (having a member) by a counter signer using the Recipient Settings modal. (refs PB-114669)

• There is a refresh issue with the signing order when replacing an Ad Hoc Group with a different recipient while signing order is enabled. (refs PB-114670)