简体   繁体   English

Docusign SDK - 为什么在创建 SignHere 标签时会忽略 document_id?

[英]Docusign SDK - Why document_id are ignored when creating a SignHere tag?

I use docusign-esign SDK for Python, version 3.3.0.我使用 docusign-esign SDK for Python,版本 3.3.0。

Let's suppose that I have two differents documents in the same envelope, and the same Signatory have to sign them both.假设我在同一个信封里有两个不同的文件,并且同一个签字人必须同时签署它们。

I declare following entities, which is a simplified version of my code :我声明以下实体,这是我的代码的简化版本:


documents = await build_docusign_documents() # A list of instances that modelise my documents that needs be signed on Docusign
john = database.users.get_john() # My user model instance.

signer = InPersonSigner(
            signer_email=john.mail,
            signer_name=f"{john.first_name} {john.last_name}",
            recipient_id=1,
            routing_order=1,
            host_name=f"{representative.first_name} {representative.last_name}",
            host_email=representative.mail,
            tabs=Tabs(sign_here_tabs=[], date_signed_tabs=[]),
        )


tabs = [
    SignHere(
        recipient_id=1,
        document_id=document.id,
        tab_label="SignHereTab",
        anchor_string="DS_USER_SIGNING",
    )
    for document in documents
]

signer.tabs = Tabs(sign_here_tabs=tabs)


The snippet abose is supposed to declare two "sign here" tabs on two differents documents.代码片段 abose 应该在两个不同的文档上声明两个“在此处签名”选项卡。
What happens in Docusign interface is quite different, both tabs are duplicated. Docusign 界面中发生的事情完全不同,两个选项卡都是重复的。 (2 pack of 2 superposed tabs) (2 包 2 个重叠标签)
Which means that the two SignHere instances are triggered on both documents by the anchor_tag , regardless on the document_id that are provided.这意味着两个SignHere情况下被触发由两个文件anchor_tag ,无论在document_id提供的。
To solve the issue, I removed the document_id key, and only declaring a single SignHere tab for a user, regardless of the number of tabs needed.为了解决这个问题,我删除了document_id键,并且只为用户声明了一个SignHere选项卡,而不管需要多少选项卡。
This is not what I understand from the docs : https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/tabs/这不是我从文档中理解的: https : //developers.docusign.com/docs/esign-rest-api/esign101/concepts/tabs/

When tabs are added with anchor tagging, DocuSign searches the document for instances of an anchorString property that you provide.添加带有锚标记的选项卡时,DocuSign 会在文档中搜索您提供的 anchorString 属性的实例。 For each found instance, it places a tab of the specified type for the designated recipient.对于每个找到的实例,它会为指定的收件人放置一个指定类型的选项卡。 Tab positions in relation to the string instances can be set by providing x and y offsets.可以通过提供 x 和 y 偏移量来设置与字符串实例相关的选项卡位置。

The docs says that the scan is perfomed for a whole document not a whole envelope.文档说扫描是针对整个文档而不是整个信封执行的。

It works, but I don't understand why and I'm not confortable with this.它有效,但我不明白为什么,我对此感到不舒服。

Thanks谢谢

There is a global setting of "Anchor Population Scope" for your account that determines the scope of anchor tags.您的帐户有一个“锚点人口范围”的全局设置,用于确定锚点标签的范围。 It can either be for a specific document, or the entire envelope.它可以用于特定文档,也可以用于整个信封。 Yours must be set the other way.你的必须以另一种方式设置。 Unfortunately changing this settings requires you contact DocuSign support.不幸的是,更改此设置需要您联系 DocuSign 支持。 This settings is for all your envelopes, so you need to figure out if changing it is what you need, and if so - make the request by going to support.docusign.com此设置适用于您的所有信封,因此您需要确定是否需要更改它,如果需要,请访问 support.docusign.com 提出请求

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM