Eric | Posts: 3

Document Visibility on closed transaction

0 votes

Hi everybody!

I am using the "Document Visibility" feature according to the following documentation according to the documentation in the link below and it works at the moment the signers are signing the document(s) (when they receive the emails indicating that they have a document (s) to be signed) but when the documents are finished being signed and the email arrives indicating that the transaction has been completed, all the documents of the transaction are attached and any signer can open and view the documents even if a specific visibility has been configured for each document.

How can I solve this?


Duo_Liang | Posts: 3776

Reply to: Document Visibility on closed transaction

0 votes

Hi Eric,

 

Thanks for your post! With a quick test, the attachments delivered via Email should be applied with the document visibility. Could you share the package ID of this transaction so that I can look closer into the issue?

 

Duo


Eric | Posts: 3

Reply to: Document Visibility on closed transaction

0 votes

Hello Duo_Liang

Thank you very much for your answer but doing more detailed tests I am observing that even when the package is in the process of signing the signers that have specific visibility can see all the documents :(, I share the following code fragment (using Java JDK) where I configure the visibility and some captures where it is observed that a signer who only has permission to see a document can see all the documents:

 

Code:

EslClient eslClient = eslClientManager.createEslClient(securityData);
            
            List<DocumentVisibilityConfiguration> configurations = new ArrayList<>();
            
            for(com.bbva.seiri.onespan.connector.dto.Document document : documentPackage.getDocuments()) {
                if(document.getViewers() != null) {
                    configurations.add(DocumentVisibilityConfigurationBuilder
                            .newDocumentVisibilityConfiguration(document.getId())
                            .withSignerIds(document.getViewers())
                            .build());
                }
            }
            
            if(!configurations.isEmpty()) {
                eslClient.configureDocumentVisibility(packageId, DocumentVisibilityBuilder
                        .newDocumentVisibility()
                        .withConfigurations(configurations).build());
            }
            
            eslClient.sendPackage(packageId);


Attachments
Duo_Liang | Posts: 3776

Reply to: Document Visibility on closed transaction

0 votes

Hi Eric,

 

Thanks for the sharing! I used the code base you provided above and the code works well. I attached the code I was testing with, and the outbound payload looks like below:

{
  "configurations": [
    {
      "documentUid": "default-consent",
      "roleUids": [
        "a82823f5-f22b-47f8-9604-1e7f5e4bc6ef",
        "e6f40361-1db7-498e-bfe6-475fd22f6778"
      ]
    },
    {
      "documentUid": "879932eb98a30a675e5440940a686b6b0bf1b9c06709b81e",
      "roleUids": [
        "a82823f5-f22b-47f8-9604-1e7f5e4bc6ef"
      ]
    },
    {
      "documentUid": "095b106a8039145ba67688dfbec97a3c715064e499ed9464",
      "roleUids": [
        "e6f40361-1db7-498e-bfe6-475fd22f6778"
      ]
    }
  ]
}

Which is expected with this code:
        List<Document> documents = new ArrayList<>();
        documents.add(new Document("default-consent",Arrays.asList("a82823f5-f22b-47f8-9604-1e7f5e4bc6ef","e6f40361-1db7-498e-bfe6-475fd22f6778")));
        documents.add(new Document("879932eb98a30a675e5440940a686b6b0bf1b9c06709b81e",Arrays.asList("a82823f5-f22b-47f8-9604-1e7f5e4bc6ef")));
        documents.add(new Document("095b106a8039145ba67688dfbec97a3c715064e499ed9464",Arrays.asList("e6f40361-1db7-498e-bfe6-475fd22f6778")));
        

Quick question - can you debug the document.getViewers() list and see if the signers have correct visibility in your local dto?

 

Duo


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off