Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Component error in Adobe sign for Salesforce

New Here ,
May 07, 2019 May 07, 2019

Hello, when I try to view an agreement in Salesforce, I'm getting the following error:

Error in $A.getCallback() [echosign_dev1:AgreementEditor:4,35: String index out of range: 0]

Additional exception on component load: echosign_dev1:AgreementEditor:4,35: String index out of range: 0. Caused by: Error in $A.getCallback() [echosign_dev1:AgreementEditor:4,35: String index out of range: 0]

This comes up no matter what agreement I click on, even on agreements I was able to view previously.

In case it has anything to do with it, the sandbox I am using was upgraded to the Summer release over the weekend.

Thanks,

Sue Irvine

Cornell University

965
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

New Here , May 08, 2019 May 08, 2019

The fix from Salesforce seems to roll out in Sandbox now. I don't see the error any more in my summer 19 sandbox.

BTW, we track the issue from Summer 19 release internally and don't post status for Salesforce fixes.

Translate
New Here ,
May 07, 2019 May 07, 2019

We already filed a support case for this issue to Salesforce. The ETA of fix from Salesforce is 5/8/19 EBD.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 08, 2019 May 08, 2019

Thank you! Is this status posted anywhere on your site? I couldn't find it anywhere.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 08, 2019 May 08, 2019
LATEST

The fix from Salesforce seems to roll out in Sandbox now. I don't see the error any more in my summer 19 sandbox.

BTW, we track the issue from Summer 19 release internally and don't post status for Salesforce fixes.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines