适用于 Salesforce 的 Adobe Sign 发行说明

适用于 Salesforce 的 Adobe Sign 发行说明按以下顺序排列,最新版本排在最上面,向下滚动页面可逐渐前溯到更早版本。

注意:

强烈建议首先安装或升级到沙箱环境,以验证应用程序的所有方面能否按预期工作,并且不与任何其他自定义、设置或应用程序冲突。

v21.5.11 之前的版本升级的客户必须先升级到版本 21.5.11 包然后再升级到最新的包。

适用于 Salesforce 的 Adobe Sign 版本 23.x

Adobe Sign 图标的品牌重塑

整个应用程序中使用的 Adobe Sign 图标已更新为新品牌。


更新您的 Salesforce 组织以将 Files 用作文档的默认存储对象

适用于 Salesforce 的 Adobe Sign 包的版本 23 将存储文档的默认对象类型从旧版 Attachments 对象切换为相对较新的 Files 对象。

此更新增强了 Salesforce Lightning 体验,它仅支持 FilesSalesforce classic 体验支持 Files),并与许多常与 Adobe Sign 配对并以类似方式升级的第三方解决方案保持一致。

受影响的文档包括:

  • 协议文档
  • 数据映射
  • 协议模板
  • 协议更新
  • 大文件发送
  • 自定义设置
  • 推送协议

管理员此时无需执行任何操作,即可更新到此版本,因为现有存储对象已获准保留在组织中,从而确保操作可以继续而不中断。

但是,建议管理员调查如何迁移其组织以在 Attachments 被弃用之前使用 Files

注意:
  • 从版本低于 23.0 的适用于 Salesforce 的 Adobe Sign 更新后,将沿用现有存储对象(对于大多数客户,为 Attachments)。无需执行任何操作即可继续正常运行
  • 适用于 Salesforce 的 Adobe Sign 包的新安装将 Files 设置为默认存储对象,但可以手动切换到 Attachments
  • Salesforce 管理员可以使用控件在 FilesAttachments 之间切换存储对象


用于控制文档存储类型的新自定义设置

为支持文档存储类型的管理员控制,向自定义设置 > Adobe Sign 设置控件集添加了新控件。

此 UI 映射到自定义对象 Agreement_Document_Storage_Type__c

可行的设置值有:

  • {empty} - 如果值为空,则默认行为基于包的安装版本
    • 版本 23.0+ 将默认采用 Files 作为默认存储类型
    • 早于 23.0 的版本将默认采用 Attachments 作为默认存储类型
  • Files - 明确将 Files 定义为 Adobe Sign 文档的默认存储对象
  • Attachments - 明确将 Attachments 定义为 Adobe Sign 文档的默认存储对象
文档类型设置


分析设置

已添加可选的分析设置,以允许 Adobe Sign 收集使用情况数据来改进产品。此数据仅用于开发,而不用于营销。

通过单击右侧边栏中的分析设置链接,可以从 Adobe Sign 管理员选项卡控制此设置:

分析设置

对于大多数新客户安装,分析设置在默认情况下已启用

  • 加拿大和欧盟的客户在默认情况下将禁用分析
  • 升级客户在默认情况下将禁用该设置以匹配其当前体验。管理员可以在 Adobe Sign 管理员选项卡上随意启用该设置

启用后,会自动向您的 CSP 受信任站点添加 adobe.io 站点名称的记录:

添加了 Adobe.io 的 CSP 受信任站点

禁用分析设置会自动从 CSP 受信任站点页面中删除 adobe.io 记录。


已解决的问题

问题编号 更正的问题描述
15687 修复了从 Adobe Sign 管理页面删除的库模板仍可由 Salesforce 模板访问的问题
18890 修复了已取消协议状态的拼写不一致问题
20380 修复了日期的格式错误
20420 改进了自定义工具栏的菜单位置,使其不会在屏幕外打开
20436 修复了光标未在协议上将相关链接显示为可单击的问题
20631 修复了附加到协议的图像文件在浏览器选项卡中打开而不是下载的问题
20638 改进了取消原因字段,允许超过 255 个字符
20678 修复了 Salesforce 自定义主题在“Adobe Sign”选项卡上会丢失的问题
20972/21359 修复了在访问令牌过期时无法访问 Adobe Sign 库模板的问题
21126 修复了在自定义设置中禁用“电子邮件收件人”类型时,无法从收件人选项中删除该类型的问题
21426 更正了如果用户的库有非常大的库列表 (1000+),则可能阻止访问 Adobe Sign 库模板的问题
21512 改进了协议标题中文件扩展名的管理
注意:

适用于 Salesforce 的 Adobe Sign 包支持用于比当前主版本落后两个主版本的版本。

  • 当前版本为 23.0
  • 为版本 21+ 提供了支持

运行不受支持版本的客户面临的安全风险会有所提高,强烈建议这些客户升级到新软件包,以确保继续获得支持。

如果您有任何问题或在升级组织时需要帮助,请联系您的成功经理。


早期版本

Salesforce 协议模板现在具有挂接到 Adobe Sign 的自定义工作流程中的选项,从而允许您在 Adobe Sign 中映射复杂的签名流程,然后将该结构导入到 Salesforce 模板中:

Salesforce 模板中的工作流程

已解决的问题

对于希望在 Salesforce 和 Adobe Sign 即将推出的新安全框架(例如,升级的 API)下继续使用 Adobe Sign 的组织来说,适用于 Salesforce 的 Adobe Sign 21.5.11 是一个必要的安装点。

21.5.11 包将取消引用两个页面(MyEchoSign.pageAboutEchoSign.page),以便为彻底删除它们而扫清道路。

此软件包的特性功能或用户功能未进行更改,不过,有些问题已得到解决:


已解决的问题

问题编号

更正的问题描述

19681

改进了此软件包,以去除在禁用 Chatter 时阻止安装的 Chatter 要求

20013

更正了协议状态更新针对把 Adobe Sign 身份验证作为验证方法的协议不起作用的问题

20045

修复了 Lightning UI 配置的自定义设置仅适用于系统管理员的问题


支持 Salesforce“文件”作为“文件映射”中的存储对象

适用于 Salesforce 的 Adobe Sign 2019 年冬季版 (v21) 在为现有客户保留向后兼容性的同时,更新了该软件包的三个核心元素以支持新的部署:

此外,为了引入 Salesforce 体验,使之更好地与 Web 体验相配合。我们还进行了一些调整。基于上述目的,

通过“数据映射”流程映射文件存储时,新增了一个复选框,用于明确强制将存储作为一个附件。

如果未选中此选项,则将内容作为文件进行存储。

改进了协议更新流程

v21 更改了 Salesforce 中的协议更新流程。不同于向 Salesforce 推送更新,Adobe Sign 将通知 Salesforce 存在可用的更新,Salesforce 随后可以提取这些更新。这种方式有助于缓解此类僵局:Adobe Sign 推送更新时,Salesforce 处于脱机状态。

另外,协议现在采用异步更新方式,而先前的所有版本均采用同步更新方式。


新增的自定义设置部分:Adobe Sign 协议更新设置

为了支持新的更新流程,Salesforce 中的“自定义设置”区域新增了一个部分:Adobe Sign 协议更新设置

以往的五个现有设置已从“Adobe Sign 设置”部分迁移到这个类别:

Adobe Sign 设置

Adobe Sign 协议更新设置

将审计 PDF 添加到附件列表

添加审核报告

为推送的协议添加已签名的 PDF 链接

添加已签名的 PDF URL

为推送的协议添加已签名的 PDF

添加已签名的 PDF

将签名的 PDF 作为单独的附件添加

将签名的 PDF 作为单独的附件添加

向附件列表添加支持文件

添加支持文件

 

新增了三项设置:

  • 显示图像 – 启用后,协议 PDF 中的图像将显示在协议页面上
  • 更新协议事件 – 启用后,Salesforce 将在收到 Adobe Sign 的通知后更新协议事件
  • 更新协议状态 – 启用后,Salesforce 将在收到 Adobe Sign 通知后主动更新协议状态

当前,手动更新协议时,将会更新协议的所有元素(包括收件人、事件、图像等),而不仅仅是更新状态。

旧图像


重命名的自定义设置部分:“Adobe Sign 推送映射设置”现在更名为“Adobe Sign 协议收件人设置”

“推送映射设置”在经过重新设计后,可广泛应用于所有协议,为此,管理这些设置的相关自定义设置部分已重新命名,以更好地体现这些设置适用于所有协议的收件人,而并非仅适合推送协议的收件人。

另外,还新增了五项设置,以用来扩展更新协议相关收件人的功能:

  • 创建缺少的收件人(默认启用)- 启用该项设置后,可创建缺少的收件人
    • 如果是协议推送映射、更换签名者或委派签名者工作流程,则会创建新的收件人
  • 启用参与者集合 - 启用该项设置后,可以创建和更新参与者集合
  • 更新已委派的收件人(默认启用)- 启用该项设置后,如果收件人是由签名者或发件人委派的,则将相关的收件人标记为已委派
    • 协议视图页面,这些收件人是隐藏的
  • 更新收件人(默认启用)- 启用该项设置后,可以更新现有收件人属性,如状态
  • 更新替换的收件人(默认启用)- 启用该项设置后,如果收件人是由发件人从管理页面中替换的,则将相关收件人标记为已替换
    • 协议视图页面,这些收件人是隐藏的


改进了手动更新流程

手动更新流程经过改进后,可更新整套协议对象,其中包括所有链接、图像、事件、状态和数据映射。


更新了事件描述

更新了协议事件描述,共有三处变更:

  • 采用通用术语“文档”而不是协议的名称
  • 在名称值后插入用户的电子邮件地址
  • 包含 IP 地址


新增的验证方法:身份证

已将新增的身份证验证方法作为自定义选项添加到“Adobe Sign 设置”部分中。

身份证是一种高级身份验证方法,必须由您的成功经理启用,然后才能部署。


可用于添加文件的拖放支持
(仅限 Lightning)

现在,Lightning 允许您体验向新协议中添加文档的过程,具体方法是:从本地系统拖动文档,然后将它们放至文件区域。

通过拖放操作添加的文档,将会上传到 Salesforce 的个人文件中。


新的协议模板格式

“协议模板”界面已更新,分列在五个标签页中的模板内容让界面变得更加清晰明了。


简易签名

“简易签名”是一个易于使用的开箱即用组件,允许社区门户用户签署自助服务协议。可将此组件添加到任何 Salesforce 社区云门户(客户、合作伙伴、员工等),也可将此组件嵌入到其他 Lightning 组件。


适用于 Salesforce CPQ 的 Adobe Sign:
“生成 Adobe Sign”按钮

Adobe Sign CPQ 组件经过改进后,简化了向协议附加“报价 PDF”的过程。只需通过单击一个按钮,即,“生成 Adobe Sign”按钮或 LEX 组件,就可以完成相关操作。

单击 LX 组件中的“生成”按钮

已解决的问题

概述

Salesforce 2018 年夏季版 (v20) 扩展了 Lightning Experience 内的功能,并新增了客户一直以来所要求的几项呼声较高的功能。

注意:

适用于 Salesforce 的 Adobe Sign 版本 20 中,我们进一步与 Lightning Experience 保持一致,以优化整体性能。

有一部分优化工作是将协议列表移至 Lightning 组件。早期版本使用的是一个带有嵌入式“Lightning Out”组件的 Visualforce 页面。当针对标准对象(联系人、业务机会、帐户、合同等)从某个相关列表中启动新协议时,这种移动操作的结果会导致无法自动将该协议与此对象关联。其原因在于 Salesforce 缺乏对“Ikid”参数(即将直接传递到 Lightning 组件)的支持。

只有在使用 Lightning 页面布局时,才会出现这种限制。若使用“高级”页面布局,则可以继续启用这项功能。

有关更改页面布局的描述信息,请参阅此处。

 

支持 Salesforce 进程构建器

已经添加了支持 Salesforce 进程构建器的相关操作。

管理员可以构建多个进程,以便通过模板来触发协议的创建、发送、提醒、更新、取消和删除操作。

 

收件人的角色得到扩展

增添了三个新的角色,而且每个角色都有与之对应的委派者角色!如今,在您创建的签名流程中,参与者的类型可以包括:“接受者”、“表单填写人”和“经过认证的收件人”。

 

改进了对沙箱的支持

在 2019 年 3 月 16 日,Salesforce 将自动启用一项重要的更新,该更新会删除有关碎片识别的 URL。

在 v20 之前的版本中,该 URL 用于解析碎片信息,而且当 SFDC 实例尝试进行沟通时,该 URL 可针对 SFDC 实例的性质,对 Adobe Sign 发出指令(生产或沙箱)。

在 2019 年 3 月 16 日之后,安装 v19 或更低版本的客户需要联系支持部门,才能完成以下操作:标记沙箱环境,连接 OAuth 进程。

对于安装了 v20 及更高版本的客户来说,他们无需联系 Adobe Sign 支持部门,即可轻松浏览 OAuth 进程。

 

收件人将与他们触发的每个事件相关联

现在,“协议事件”对象可以将事件与触发该事件的收件人相关联,进而能够详细了解与这位收件人有关的分步式签名过程。

 

增加了收件人的 IP 地址字段

“协议事件”对象新增了一个字段:代理用户 IP 地址

这个新字段可以为所有根据协议记录的事件导入 IP 地址,并且可以将 IP 地址与触发对应事件的用户相关联。

可生成报告,以显示相关的 IP 信息

 

获取并更新旧文档密钥

对于仍在使用适用于 Salesforce 的 Adobe Sign v13 或更低版本的帐户来说,他们现在可以升级到软件包的较高版本,并且可以更新其现有协议的相应文档密钥。

 

v20.8(增量修补程序)

已将字段“API 名称”添加到“数据/合并映射”的选择列表中

新增了一项设置,可以在定义数据或合并映射时,显示字段的 API 名称。

要启用此项功能,请执行以下步骤:

  1. 导航至设置 > 平台工具 > 自定义代码 > 自定义设置
    • 此时会加载自定义设置页面
  2. 单击 Adobe Sign 设置标签
    • 此时将加载 Adobe Sign 设置页面

3. 单击管理按钮

 4. 单击新建(或者,如果您之前配置了设置,请单击编辑

• 此时将加载 Adobe Sign 设置页面

5. 使用“查找”功能 (cmd/ctrl + f),找到显示文件 API 名称

6. 单击保存

 

已解决的问题

问题编号

更正的问题描述

14931

使用“基本”页面布局发送协议时,出现错误消息

15012

“EchoSign 协议高级 VF”页面无法自动填充收件人

14578

除非数据映射中有一项要映射到其他对象的条目,否则文件映射将会失败

13169

自动设置错误

12457

如果收件人顺序发生变化,则不会保留收件人

14541

如果定义的收件人超过 11 位,则会提示出错

 

v20.9(安全修补程序)

对于将要执行升级并且已配置了大型文件或推送协议的客户,在安装新包之前,应该仔细阅读升级流程:

适用于大文件服务的升级流程

适用于推送协议的升级流程

 

使用“回调用户”替换了“回调站点配置文件”

由于向 Salesforce 回调站点授予广泛对象访问权限会导致安全问题,v20.9 引入了一个基于用户的新身份验证过程,此过程可确保对协议对象的访问权限施加超强的控制。

回调站点在传统上用于启用大文件服务和推送协议的客户。对于启用了以下一个或两个功能的所有客户,我们强烈建议升级到 v20.9,启用新的回调用户过程,并从站点用户中删除所有权限。

“回调用户”可通过“Adobe Sign 管理员”页面中的一个新增控件来启用,该控件位于 Adobe 帐户链接正下方。

 

v20.11(增量修补程序)

问题 621/14678 解决了 Lightning 环境先前存在的限制,该限制会阻止协议与启动该协议的父级 SFDC 对象之间的自动关系。

 

已解决的问题

问题编号

更正的问题描述

621/14678

改进了在自动将协议与父 SFDC 对象相关联方面的 Lightning 体验

15441

改进了在 Salesforce 中查询加密字段以查找字段的功能

15686

更正了以下问题:如果使用托管签名,则在“协议”页面上检索签名 URL 时,Edge 浏览器会出现问题

Salesforce 2018 年冬季版 (v19) 扩展了 Lightning Experience 内的功能,并新增了客户一直以来所要求的几项呼声较高的功能。

 

在 Lightning 页面中进行批量操作

现在,Lightning 界面中提供批量创建、发送、提醒、取消、删除和更新协议的功能,并且改进了在最终执行这类操作之前,对正在采取的操作进行概述的过程。

 

新的权限集,用于加快用户启用速度

对于那些安装适用于 Salesforce 的 Adobe Sign 应用程序、但无法选择“所有用户”选项的管理员而言,过去他们需要通过繁重的手动操作,使对象和字段可供各个用户访问。

但这种情况不会再出现了!在增加了三套新的权限后,管理员可以快速将所有的权限应用于各位用户,而无需为每个对象重复执行每个字段。

这三个选项包括:

  • Adobe Sign 用户 - 适用于 Salesforce 的 Adobe Sign 发件人用户需要具备的最低权限。包括对受管理包中所含的必需组件的有限访问权限:对象、字段、选项卡、类和页面。
  • Adobe Sign 管理员 - 适用于 Salesforce 的 Adobe Sign 管理员用户所需的最低权限。包括对受管理包中所含的全部组件的完全访问权限:对象、字段、选项卡、类和页面。
  • Adobe Sign 集成用户 - 适用于 Salesforce 的 Adobe Sign 集成用户所需的全部权限。包括所有管理员访问权限以及对所有组织数据的访问权限。

 

高级书面签名工作流程

通过书面签名,获取既准确又可以审核的电子签名。无需传真机,签名者即可完成以下操作:填写、打印、签署、扫描和返回文档。所有信息均采用电子方式进行捕获和管理,因此您将会收到清晰可辨的文本以及审核记录中的签名者验证数据。

高级书面签名工作流程取代了过时的传真流程,可带来更为一致和专业的结果。有关更多详细信息,请查阅此处。

 

适用于 Outlook 和 Gmail 的电子邮件组件

适用于 Salesforce 的 Adobe Sign 电子邮件组件可用于 Microsoft Outlook Web App (OWA)、Outlook 2016、Outlook for Mac 2016 或 Outlook 2013。这个组件包同样也适用于 Gmail for Work 集成。

这个电子邮件组件需独立安装,不过,只要花上几分钟的时间,即可完成该组件的安装和配置。

单击此处以了解安装详细信息。

 

改进了针对多个屏幕大小的可重排发送页面

在日常的业务工作中,小屏幕设备的使用变得越来越常见,这使左右滚动操作就成了一件非常痛苦的事情,它严重阻碍了您的工作效率。为了帮助这些喜爱使用平板设备的用户,我们对发送页面进行了重构,使其可排满范围更广的屏幕宽度,同时不损失任何功能。

 

Salesforce CPQ 的集成组件

更快地将 CPQ 报价从 Salesforce 直接提交到客户的邮箱,准备好使用 Adobe Sign CPQ 连接器组件进行签名。

 

Salesforce 社区云门户(自助签名)支持

如今,社区门户可以包含一个 Adobe Sign 组件,该组件能够提供即将由门户用户签署的协议。

Salesforce 管理员能够按需要发布协议、设立截止日期并定义续订周期。

用户可以访问社区站点,生成新的协议,以及直接在门户中对协议进行签名。

 

19.4 版 - 2018 年 1 月发行

如果是从低于 14 的早期版本中升级,则需要更新传统文档密钥

如果适用于 Salesforce 的 Adobe Sign 应用程序是从低于 14 的早期版本升级到当前版本,则用户可能无法对现有协议(即,其他用户在升级前发来的协议)执行诸如“删除”、“取消”、“查看”、“提醒”或“更新”等操作。

执行上述某个操作时,用户可能会收到类似于下面的错误提示:

“INVALID_DOCUMENT_KEY”或“出现了内部服务器错误”

这是由于版本低于 14 的应用程序中使用的传统文档密钥样式所致。

因此,需要对这些传统密钥进行一次性迁移。为了达到目的,我们提供了新的资源,如下所述:

完成设置步骤后,以下链接会出现在 Adobe Sign 管理员页面上:

  • 获取丢失的文档密钥 - 单击此链接可执行批量操作,以获取丢失的文档密钥,供现有协议使用。
  • 更新传统的文档密钥 - 单击此链接可清除现有的传统文档密钥,并获取新的文档密钥,以便供组织中目前所有的协议使用。

如果有些协议不具备关联的文档密钥,该资源也可以为这些协议提取文档密钥

当协议有了新的文档密钥后,用户就可以对其他用户发来的现有协议执行所有的协议操作。

注意:

仅当管理员从低于 14 的版本升级到 19.4 版本时,获取丢失的文档密钥更新传统文档密钥链接才会处于可见状态。

如果管理员是在版本 14 和版本 19.2 之间更新软件包,上述两个链接默认情况下会处于隐藏状态。对于这种情况,管理员可以联系 Adobe Sign 支持团队,以手动显示链接。

此操作要求您授予访问 Adobe Sign 支持团队的登录权限。


已解决的问题

问题 ID

说明

8014

改进了 Conga 在“取消”和“提醒”操作方面的功能

8979

解决了导致出现“超出视图状态大小的最大限制”错误的问题

9709

更正了 WRITTEN_SIGNED 事件类型中缺少 AgreementEventType 的问题

9832

解决了 Salesforce 平台用户遇到的“权限被拒绝”错误

9927

更正了这样一个问题:尝试附加到协议中的文件缺少了相应的扩展名

9934

改进了对地理位置字段的处理

10367

为那些从软件包版本 13 及更低版本进行更新的客户提供了一种 docKey 解决方案

 

版本 19.5 - 于 2018 年 2 月发行

添加了挪威语的本地化版本。

注意:

如果您使用的是挪威语本地化版本,并且已更新到适用于 Salesforce 的 Adobe Sign 19.0-19.4,那么您需要手动更新 19.5 翻译表格。

 

从 v19.0 - v19.4 升级到 19.5 的情况

启用翻译(如果您使用的是 Salesforce 的本地化版本,则需要执行以下步骤)

  • 以管理员身份登录到 Salesforce
  • 导航至设置 > 平台工具 > 用户界面 > 翻译工作台 > 翻译
  • 单击启用

 

将挪威语作为一个语言选项

  • 以管理员身份登录到 Salesforce
  • 导航至:设置 > 平台工具 > 用户界面 > 翻译工作台 > 翻译设置
  • 在“语言”选择列表中,选择挪威语
  • 单击保存

更新翻译

  • 导航至:设置 > 平台工具 > 用户界面 > 翻译工作台 > 翻译
    • 语言选为挪威语
    • 设置组件选为选择列表值
    • 对象选为协议

 

  • 主选择列表表格中,展开协议状态文件夹
  • 双击英文状态旁边的栏空间,以打开可在其中输入译文的文本字段。按照下面的表格,输入相应的值:

主选择列表值标签

选择列表值标签翻译

已批准    

Godkjent

已取消/已拒绝                

Avbrutt/avslått

已创建

Opprettet

草稿

Kladd

过期

Utgått

已发出进行批准                        

Ute til godkjenning

发出进行签名                        

Ute til signering

预送                                        

Før sending

正在发送中                        

Sending pågår

已签名      

Signert

正在等待对方批准   

Venter på kontragodkjenning

正在等待对方签名        

Venter på kontrasignatur

 

o   单击保存

 

  • 主选择列表表格中,展开语言文件夹并输入以下值:

主选择列表值标签

选择列表值标签翻译

中文(中国大陆)

Kinesisk (Kina)

中文(台湾地区)

Kinesisk (Taiwan region)

捷克语(捷克共和国)

Tsjekkisk (Tsjekkia)

丹麦语(丹麦)

Dansk (Danmark)

荷兰语(荷兰)

Nederlandsk (Nederland)

英语(英国)

Engelsk (Storbritannia)

英语(美国)

Engelsk (USA)

芬兰语(芬兰)

Finsk (Finland)

法语(法国)

Fransk (Frankrike)

德语(德国)

Tysk (Tyskland)

冰岛语(冰岛)

Islandsk (Island)

印尼语(印度尼西亚)

Indonesisk (Indonesia)

意大利语(意大利)

Italiensk (Italia)

日语(日本)

Japansk (Japan)

朝鲜语(韩国)

Koreansk (Sør-Korea)

马来语(马来西亚)

Malayisk (Malaysia)

挪威语(挪威)

Norsk (Norge)

波兰语(波兰)

Polsk (Polen)

葡萄牙语(巴西)

Portugisisk (Brasil)

葡萄牙语(葡萄牙)

Portugisisk (Portugal)

俄语(俄罗斯)

Russisk (Russland)

西班牙语(西班牙)

Spansk (Spania)

瑞典语(瑞典)

Svensk (Sverige)

泰语(泰国)

Thai (Thailand)

土耳其语(土耳其)

Tyrkisk (Tyrkia)

越南语(越南)

Vietnamesisk (Vietnam)

o   单击保存

 

  • 对象选择列表更改为表单字段映射条目
  • 展开源类型文件夹
  • 主选择列表表格中,展开语言文件夹并输入以下值:

主选择列表值标签

选择列表值标签翻译

常量

Konstant

Salesforce 对象字段

Salesforce-objektfelt

 

o   单击保存

 

 


已解决的问题

问题 ID

说明

6227

更正了在某些工作流程中更换收件人时显示错误审批人图标的问题

6816

修复了使用 EchoSign 高级 VF 页面替换签名者时引发 null 404 错误的问题

6956

修复了在导入过多字段时导致最大视图状态大小限制错误的问题

10426

更正了“潜在客户”对象要求所有字段明确允许访问数据映射的错误

10676

改进了日期公式,使其始终显示用户本地时差

10979

更正了“管理协议”选项卡需要拥有“系统”权限才能访问“查看设置”的问题

The Spring 2016 Salesforce (v18) release introduces the Lightning experience, and the newest update to the Adobe Sign for Salesforce package is "Lightning Ready".  Enabling the Lightning experience is completely up to you, and you can switch back to Salesforce Classic at any time.

In Lightning, the navigation menu on the left provides quick access to your Salesforce objects. You can use the App Launcher to access the Adobe Sign integration package.

See Find Your Stuff in Lightning Experience in the Salesforce Help for more information.

 

Lightning Experience

Enabling the Lightning Experience is easy:

  1. From Setup
  2. Click Lightning Experience in the left navigation menu to change the default settings before you switch the view. 
  3. Select Switch to Lightning Experience from your profile menu, to change to the Lightning view.
SFDC settings to switch to Lightening

See Enable Lightning Experience in the Salesforce Help for more information. 

 

 

Switching back to Salesforce Classic

If you are working in the Lightning Experience, switching back to Salesforce Classic is also easy. Simply click your profile picture in the upper right corner, and select Switch to Salesforce Classic from the menu.

Click your profile picture in the upper right corner, and select Switch to Salesforce Classic

 

Accessing the Adobe Sign integration application

Once Lightning is enabled, you can click the App Launcher to display the available apps, then click Adobe Sign.

See Opening a Different App in Lightning Experience in the Salesforce Help for more information.

The App Launcher

The menu for Adobe Sign displays. From this menu you can access all the familiar Adobe Sign pages and features. Note that the Manage Agreements and Adobe Sign Admin pages are currently only available in Salesforce Classic.

The menu for Adobe Sign display

In the Lightning Experience, the Adobe Sign pages have a new, cleaner look.

The Adobe Sign Lightning Experience

 

Enhanced Agreement page

The enhanced Agreements page can be used in both Salesforce Classic and Lightning. Before using this new Agreement page, you must enable the enhanced Agreement page style.

 

Enhanced Agreement Layout experience:

The enhanced Agreement page layout provides senders with all of the functionality of the previous layout plus additional features. The enhanced agreement page is available in both Salesforce Classic and Lightning.

To get to the enhanced agreement page, choose ‘Agreements’from the ITEMS menu on the lightning page or the left navigation menu on the Classic page.

The enhanced Agreement page layout

1. Recipients are numbered now as shown above. You can use recipient numbering to reorder recipients to create sequential routings and to create hybrid and parallel routings.

2. Sender can now quickly add themselves as a recipient anywhere in the routing, not just first or last, using Add Me and numbering.

3. Groups can be specified as recipients.

4. Private message can be added. Clicking the message bubble icon displays the Add a Private Message dialog. The bubble will appear slightly gray if you have a message.

5. Identity Verification

Define the details of the transaction

6. Select a related Contract

Enter the email addresses of the recipient

7. Select files from your document library or online storage accounts—You can now click Add Files to access the Select Files dialog and all the file sources that are enabled.

 

New recipient role: Delegator

In addition to Approver and Signer, admins and senders can now add Delegator to the recipient workflows. Delegators receive the agreement, but are not expected to sign.  Instead they will route the agreement to the approver or signer they choose. 

Great for situations where the signer/approver isn’t known until the signature process is underway, these two new roles will give you the flexibility to start gathering signatures immediately, and identify the proper downstream recipients at a later time.

 

Private messages

You can create unique messages for each recipient in the signing process before sending a document for signature or approval. To add a message, click the Add a private message icon. 

Create unique messages for each recipient

Recipients can easily read the private message during the signing experience. When someone has left a message for one of the recipients, the color of the message bubble will be light gray.

 

Hybrid routing

In addition to being able to create sequential and parallel recipient routing, you can use the new recipient ordering feature to create hybrid routing that includes parallel and sequential components using the new Send page. You can specify which participants need to sign at the same time (in parallel) and which need to sign in sequential order by dragging and dropping or using numbering order to define the signing sequence. 

 

Creating hybrid routing:

1. Enter the email addresses of the recipients.

Enter the email addresses of the recipients

2. To designate two recipients to sign second—in this example severtonea@gmail.com and kmaggerstein@gmail.com—enter a “2” in the routing order field for both. 

Enter a “2” in the routing order field for bot

When you save the agreement, the email addresses for severtonea@gmail.com and kmaggerstein@gmail.com display as parallel recipients in the second position. Note that the order of subsequent recipients will update to reflect the new routing order. 

The order of subsequent recipients will update to reflect the new routing order.

 

Recipient Group

You can speed up the signing processes by giving multiple team members the authority to sign on behalf of the entire group. Add a recipient group first, and then add multiple recipients to the group. Any one of the recipients listed can sign on behalf of the entire group. Recipient groups integrate with Salesforce groups.

 Add a recipient group

 

Modifying Agreements

You can make on-the-fly document corrections using the new modify agreements feature instead of canceling agreements and starting over. You can use Modify Agreements to add, delete, replace (delete then add), and reorder documents. You can also use the authoring environment to modify fields.

The modify agreements feature is available only on the new Send page. However, it can be used to modify agreements that were initiated before the November 2015 release as long as the transaction meets the “modifiable” criteria. If a document is modifiable, a Modify Agreement link displays on the Manage Agreements page when the document is selected. A modifiable agreement is one that meets the following criteria:

  • The agreement has not been signed, approved, or delegated to a signer or approver by the delegator to whom it was assigned.
  • The agreement does not include a digital signature or fax signature.
  • The agreement has not been initiated from a workflow.

 

 

Administration for modify agreements

The modify agreements feature must be turned on globally for your organization, and then the last check box, Allow senders to modify agreements after they have been sent for signature, will appear in the Account | Send Settings options for each user.

Account administrators and group administrators can specify whether you can modify documents that you have sent for signatures by checking the “Allow senders to modify agreements that have been sent for signature” in the Attaching Documents section of the Send Settings parameters in your Account. 

Allow senders to modify agreements that have been sent for signature

 

Modifying an agreement

If the modify agreements setting is enabled for your organization or group, you can modify agreements that are in the Out for Signature or Out for Approval sections. (See Modify agreements for more information.)

1. Click the Manage Agreements tab.

2. Click to select a modifiable agreement from the Out for Signature or Out for Approval section, then click the agreement description in the upper-right corner.

Click the agreement description in the upper-right corner.

The Send page displays in limited editing mode and you cannot make changes in the Recipients or Message sections.

The Send page

In this Send page, you can add, delete, replace (delete then add), and reorder documents.

To add a document, do one of the following:

  • Click Add Files.
Click Add Files.

  • Or, drag-and-drop files from your computer to the Drag More Files Here area.
Drag-and-drop files from your computer to the Drag More Files Here area.

  • To delete a document, click the delete icon (X) to the right.
Click the delete icon (X) to the right.

  • To recorder documents, click the grab bar and drag the document to its new position.
Click the grab bar and drag the document to its new position

Depending on your Send settings, you may be able to use the Preview & Add Signature Fields option to add form fields to the document or documents in the modified agreement. 

注意:

When you modify an agreement, the form fields that were originally added by the sender to documents using the authoring environment are discarded. Form fields that were added to library documents when they were created and form fields added to documents with text tags are automatically reprocessed.

  • If you do not need to add form fields or do not have the Preview & Add Signature Fields option, then click Update to save your changes.
  • If you need to add form fields, enable the Preview & Add Signature Fields option if necessary, then click Update to open the authoring environment. When done in the authoring environment, click Update.

If the agreement has already been signed, when the sender clicks Update the sender gets a message indicating that the recipient has signed, approved, or delegated it.

The "Cannot Modify Agreement" message

If the Modify Agreements feature has not been turned on globally for your organization, there are still a few ways that you can make modifications after an agreement has been sent for signatures.

If you scroll down to the bottom of the agreement description, you will see three ways that you can modify an agreement.

Replace Signer and Upload Copy links in the transaction metadata.

The actions you can perform on an existing agreement include replacing a signer, uploading a signed copy, and adding an expiration date.

To replace the current signer, enter the new signer’s email address and the reason that you are replacing the original signer. For example, the original signer might be out-of-the-office during the time you need to have the documents signed. Click the Replace Signer button when you’re finished.

Replace Current Signer interface

To upload a signed copy, click the Replace Signer link in the agreement description. Type the email address of the new signer and a short message about the reason for replacing the original signer. Note that until the new signer adds their signature, the original signer can still sign the document.

Upload a Signed Document interface

To add an expiration date, click the Add link in the agreement description. Then click the calendar icon to select the expiration date. Select the Notify Current Recipients check box, if you want the recipients to get notified.

The Add Expiration Date window.

 

Signing, approving, or delegating a modified agreement

The recipient of a modified agreement is notified that the agreement has changed before they can sign, approve, or delegate it.

The "Agreement has been modified" notification message

The recipient can click OK to continue. The signing, approving, or delegating process proceeds as usual.

However, if the agreement has just been modified while the recipient is on the eSign page, the recipient is informed and must click Refresh to continue.

The "Agreement Has Been Modified" error panel

 

Viewing the history and audit trail of a modified agreement

Information on the events specific to the modification of a document (e.g., Agreement was modified, Agreement modification was acknowledged) can be viewed from the Manage Agreements page.

1. Click the Manage Agreements tab.

2. Single click an agreement to select it, then click the History tab on the right side of the page.

The Adobe Sign Manage tab

The event history for the agreement displays in the information panel. The transactions related to the modification by the sender and the recipient’s acknowledgement of the modification are noted.

The Adobe Sign Event List

3. Click the Audit Report link in the upper-right corner of the History frame to open a PDF Audit Report. The transactions related to the modification by the sender and the recipient’s acknowledgement of the modification are noted.

The Adobe Sign Audit Report

 

Multiple templates per Salesforce object

For customers who are using Salesforce Lightning, our v18 integration will enable admins to configure having more than one template available for any SFDC object.  This is new flexibility for users and admins, enabling them to select the correct template to start the send process. For example, now a user can send an MSA or Partner agreement from an SFDC Account object; both could be available if needed, through Lightning components.

 

Support for Salesforce Lightning Components 

For Administrators using the Lightning experience, there is a new and extremely easy way to add Adobe Sign into standard and custom SFDC pages. We offer three components to allow the Admins flexibility in building the pages as they see fit.: Adobe Sign Send and Agreement component and an Adobe Sign agreement list

 

Enhanced Adobe Sign Admin page

The Admin Page has a new cleaner look and all functionality is now on a single page. The tabs have been eliminated. Switch to the Lightning Experience to use the new Adobe Sign Admin Page.

Enhanced Adobe Sign Admin page

 

Improved Setup Wizard

Use the improved Setup Wizard to link your Adobe Sign account to your Salesforce account. The Setup Wizard is available from both the Classic and Lightning user interfaces. If your accounts are not already linked, you will see the Setup Wizard when you choose Adobe Sign from within Salesforce.  

 The improved Setup Wizard to link your Adobe Sign account to your Salesforce account

You will receive a Success! message when the wizard has linked your account to enable automatic status updates.

Success! message when the wizard has linked your account to enable automatic status updates.

Dynamic product list creation

You can now automatically add your product lists to an agreement for signature. The merge mappings have been expanded to include all products tied to an opportunity. You can set which product attributes (like quantity and price) are included in your agreements as well as sort and filter the associated products.

 

Only I Sign

Your team can now sign any given document with "Only I Sign.” To do so, the sender can select the Sender Signs Only option on the Send Agreement page. The sender can then upload the document, drag and drop any required form fields onto it, and sign it. The document can be sent to the sender and any additional recipients specified. A record of this process is automatically generated in Salesforce, and a copy of the document is stored there as well. The Sender Signs Only option appears if the Enable Sender Signs Only setting is enabled, and it can be set to read-only using the Read Only Sender Signs Only setting.

 

Custom landing pages post-signing

You can now auto-redirect the signers of an agreement to a specified URL after they sign. For example, you can redirect signers to your company website or a survey page. Also specify how many seconds elapse before executing the redirect. The option to enter a redirect URL and specify the number of seconds is available on the Send Agreement page when the Enable Post Sign Options setting is enabled, and it can be set to read-only using the Read Only Post Sign Options setting.

 

Support for larger file sizes

Previously, additional setup steps were required to send transactions that included large files. Now you can send larger transactions as follows:

  • Manual Workflow—When clicking the Send for Signature button on the Agreements page, you can send a transaction that is up to 4MB, including multiple documents whose summed size is up to 4MB.
  • Background Actions—When sending a document using background actions, a single document up to 9MB or multiple documents whose summed size is up to 9MB can be sent.

Note:   Transactions larger than the noted sizes are supported with additional setup.

 

E-sign alerts within Salesforce

Your team members can now be alerted from within Salesforce when an agreement they’ve sent is about to expire. This option is controlled using the Create Sign Deadline Reminder Event and the Days Sign Deadline Reminder Event. The sender sees a pop- up alert in Salesforce and can then take action by contacting the signer and possibly extending the deadline.

 

Digital signatures

You can send an agreement out for a digital signature. Digital signatures are preferable to electronic signatures in certain regions (such as the EU) and industries (such as pharmaceutical). The digital signatures feature is currently in beta. Contact Adobe Support if you would like to use digital signatures before November 2015, when it will become generally available.

 

Simplified Setup Wizard

The new Setup Wizard makes it easier than ever to configure Salesforce after installation. Now you simply need to select the acknowledge option to allow Adobe Document Cloud eSign services to add a trusted remote site for your organization.

 

Admin control: Hide custom sidebar

If a custom sidebar has been added to the Agreement Editor page—accessed using the View Agreement button—you can now hide this sidebar by enabling the Hide Sidebar for Agreement Editor Page setting.

 

Admin Control: Auto-provisioning

In previous releases, users were automatically provisioned when they sent or managed agreements. Now you have the option to eliminate auto-provisioning using the Disable User Provisioning setting. Note that this setting does not control the auto- provisioning that occurs when Update Agreement is clicked from the Agreement list

 

Push releases

With v17, periodic patch updates can now be automatically pushed to your organization, eliminating the extra steps of downloading and installing a new package for dot releases.

 

Show Me How in-product tutorials

Using a new feature called “Show Me How,” team members can watch easy-to-follow tutorials covering the topics that typically lead to the most confusion.

 

Service Cloud/Console frames

Adobe Document Cloud eSign services can now be viewed as a frame within the Console view. This eliminates pop-up windows when using Service Cloud or Sales Cloud.

Fully rebranded the application to Adobe Document Cloud eSign services for Salesforce

Enabled OAuth as the authentication method for the package

Salesforce 1 Enabled

  • Fully native integration
  • Highest rated e-signature app
  • e-signatures you trust

 

Do it all on mobile – send and track agreements from Salesforce1

Send from anywhere

  • Send documents for signature from Android or iOS devices

Comply with business policies on the go

  • Automatically populate recipients, documents, and agreement options
  • Automatically merge Salesforce data into contracts and push signer data back

Manage agreements on the road

  • Get real-time notifications and status tracking

 

Close deals on-site with in-person signing from Salesforce1

  • Initiate contract for in-person signature
  • Hand device over to client to sign with finger or stylus
  • Close the deal and automatically store contract in Salesforce

 

 

Verify signer identity – get higher assurance with phone authentication

  • Get a streamlined, mobile friendly user experience for identity verification
  • Enable two-factor authentication
  • Automatically send a verification code via voice or SMS text message

 

 

Enable different levels of identity assurance for each signer

Verify identities of participants with two factor authentication

Select a different identity verification method for each recipient

  • Unique password
  • KBA
  • Social identity
  • (NEW)  Phone authentication

 

 

Easily change authentication method

  • Easily reset identity verification settings on documents out for signature
  • Use the Manage page to make changes and review other document protection settings

 

 

Send and manage in batch – save time and effort

Drive efficiency and create many documents in batches:

  • Partner agreements
  • NDAs
  • Consent forms
  • Renewal agreements

 

Send and manage agreements effortlessly

  • Create Agreement
  • Send Reminder
  • Cancel Agreement
  • Update Agreement Status
  • Delete Agreement
  • Change Owner

 

 

Deploy globally – enable e-signatures for your global workforce

Automatically work in language specified in the user’s Salesforce settings

Get a fully localized experience for global Salesforce users:

  • Senders
  • Signers
  • Administrators

 

 

Standardize forms and templates to meet business requirements

Upload and reuse documents from EchoSign document library

Apply a form field template to quickly add fields to commonly generated documents

 

 

Send contracts in record time – the best experience just got better

  • Work with an easier, more modern UI
  • Drag and drop to reorder recipients and documents
  • Use calendar picker to select expiration dates
  • Replace current signer when document is out for signature
  • Let recipients sign in any order

Send Agreements from Chatter

 

Significant Improvements to Data Mappings

 

Globally Translated Experience for Senders in Salesforce

 

Optimized Sending

Agreement Templates Improvements:

  • Automatically pull recipients from Account Contact Roles
  • Automatically attach Quotes when sending from Opportunity object
  • Automatically associate the Opportunity and Account to Agreement record when sending from those objects
  • Use specific Attachment ID for Agreement attachment
  • Use Agreement Templates with Conga Composer

 

Other  Enhancements:

  • Send to more than 6 recipients or send for approval with Conga
  • Option to retain Agreements from Lead record even if converted to Account, Contact, or Opportunity

 

 

Salesforce Identity Integration

Adobe EchoSign has been tested, validated and documented to integrate with Salesforce Identity, making it easier than ever for IT organizations to enable critical identity and access management features seamlessly and securely

Learn more at: http://www.salesforce.com/identity

Highlights for Version 13 Release

 

Optimize document workflows for your business needs

  • Send documents for approval
  • Send quote PDFs and use custom contacts with agreement templates
  • Create formulas to calculate data from other fields

Better identify your signers for critical documents

  • Enable advanced signer authentication

Get instant updates and collaborate in real-time to close deals with speed

  • Adobe EchoSign for Chatter brings you up to date wherever you are

Set up faster and hit the ground running

  • Leverage the simple setup wizard and new admin page
  • Synchronize Salesforce profiles and EchoSign groups
  • Quickly enable document data merge or push signer data back to Salesforce
  • Experience step by step guided walk-thrus of key features

 

Setup Wizard and Improved Admin Page

 

Send Documents for Approval

 

Advanced Signer Identity Verification

 

Use Case Example

 

Knowledge Based Authentication (KBA)

 

Web Identity Authentication

 

Enhanced Workflows for Agreement Templates

 

Merge Data from Salesforce to Create Documents

 

Push Data Back to Salesforce

 

Adobe EchoSign for Chatter

 

Automated Sync for Salesforce Profiles and EchoSign Groups

 

EchoSign for Salesforce Guided Walk-thrus

EchoSign Spring 2013 Features

  • Create powerful, dynamic forms with calculations and then merge calculated data back to Salesforce
  • Add or change signing deadlines after agreement is out for signature
  • Exclude internal signers from document deadlines
  • Improved document readability during preview or signing
  • Require signers to accept your organization’s custom terms of use during signing
  • Updated iOS mobile app with offline signing capabilities

 

Highlights from Version 12 Releases

Version 12 released in Spring 2012:

  • Merge data from Salesforce to documents before sending
  • Define default agreement options and preferences through agreement templates

Version 12 update (dot release) launched September 2012:

  • Associate supporting documents collected from signers with Salesforce objects
  • Attach files stored in Salesforce Content repository to send for signature
  • Separately attach each signed document to a Salesforce object when multiple documents were sent in a transaction

 

Improved Admin Page

 

Merge Data from Salesforce into EchoSign Agreements

 

Agreement Templates and Send to EchoSign button

 

Include the Signed Agreement and Audit Trail in Salesforce

 

Advanced Customization Options

 

Attach Files from Salesforce Content

 

Collect Supporting Documents

 

Adobe PDF Certification For All EchoSign Documents

 

Conditional Data Fields

 

Additional EchoSign Form Fields Enhancements

 

Additional Features

Update Salesforce.com with EchoSign Form Field Data