Facing same problem here, but in Case object.

It’s related to DocuSign Envelope Status component. I’m removing it from our Record Page and let the Docusign Status in Related List to check our sent envelopes status until someone appears with the solution :)

Hi ​@vanesys  and ​@ohernandez — thanks for raising this.

Upon checking, the error “Uncaught Error in $A.getCallback() CstringUtils is not defined] Callback failed: apex://dfsle.StatusController/ACTION$getStatus” is typically thrown when the user doesn't have proper access at the permissions level to our Salesforce Lightning "Docusign Envelope Status" component. Provide all Docusign apex class permissions at the profile level. The Docusign apex classes start with "dfsle."

The easiest way to install or upgrade our managed package is for the admin to ensure they choose the "Install for ALL users" option. Note that choosing this option doesn't inherently allow all users to use the integration. Salesforce users must still be added as Docusign users via the Docusign Apps Launcher User Management admin setup page. The "Install for ALL users" option sets proper apex class permissions so that when a user is added as a DAL user, they don't run into the same error.
 

Let us know if you have more questions—we’re always here to help.

Ma. Cassandra | Docusign Community Moderator
Mark as “Best Answer” if this helped clarify things.

Hi Cassandra,

Thank you for your reply! 

We will assign permissions on those apex classes and test the behaviour, but it is strange that the error appears intermittently. I guess if it's a permissions problem it would appear all the time.

I let you know the results.

Have a nice day!

Thanks for the answer, but it’s not a permission problem, like vanesys said, it’s intermittent, something like it failed to load, if we reaload the page, it may correct.

Also it’s not something happening all the time, but I think DocuSign devteam should take a look about this bug.

Hi again, ​@ohernandez !

That’s great to hear—glad things are working now. If anything, else comes up or you hit another roadblock, don’t hesitate to reach out here in the Community.

Wishing you a smooth rest of your day!

—
Ma. Cassandra | Docusign Community Moderator

Hi @Ma.Cubio ,

I have checked the permissions and the error persists . I think like @ohernandez, that maybe it is a problem with the docusign component.

What else do you think I could check?

For now I'm going to apply @ohernandez's solution .

Thanks for your help!!!!

Hello ​@vanesys,
I’m sorry to hear that the issue is still unresolved. To further investigate this matter, we highly recommend that you create a support case so that we can check and gather more details and see if the behavior is bug-related

.—
Ma. Cassandra | Docusign Community Moderator