cdean's account

Ok, I am able to create a draft package via the REST API in eSign 7.2 on-prem server.
However, it now fails to apply the successfully retrieved layout with the following error:

Silanis.ESL.SDK.EslServerException while in ApplyLayouts.
(Silanis.ESL.SDK.EslServerException: Could not apply layout.
Exception: The remote server returned an error: (403) Forbidden.

I have my own account and the account settings allow layouts (see attached PNG).

Here is my minimal, programatically validated Package JSON Schema used to create the draft package:

  "roles": [
    {
      "id": "Signer",
      "signers": [
        {
          "email": "_EmailAddress",
          "firstName": "_FirstName",
          "lastName": "_LastName"
        }
      ]
    }
  ],
  "documents": [
    {
      "approvals": [
        {
          "role": "Signer"
        }
      ],
      "name": "_DocumentName"
    }
  ],
  "name": "_PackageName",
  "type": "PACKAGE",
  "language": "en",
  "description": "Package with _Layout Layout Applied",
  "visibility": "ACCOUNT",
  "status": "SENT"
}

I replace all underscored values with string data from our database, validate the string JSON, create the json StringContent then apply this to the POST API call.
The draft package is created fine with this.

I then retrieve the previously created and tested layout from eSign without any issues.

But when I go to apply the layout to the PackageId, I get the (403) Forbidden error. 
Why won't the Layout get applied to the package using the ESL SDK call, OneSpanClient.LayoutService.ApplyLayout(packageId, DocID, layoutId)?

Hi Duo Liang,

I have added .WithVisibility(Visibility.SENDER) when we create a package in the hopes of hiding the Shared Layouts UI control.
However, this single code change does not have the desired affect of hiding this control in the UI.
Do we need to do anything further in the code to achieve this?

Thank you, Duo

I have a newbie question, what is meant by

"could effectively limit the visibility to the sender him/herself for all layouts created by integration"