E-signature on Catalog Item TASK. Allow sign via Portal?

Troy Riblett · ‎07-14-2021

With the E-Signature plugin active, I have found out that it is possible to setup a catalog task for a signature by setting the following fields:

E-signature document - Set to the managed document the user is to sign
E-signature template - Set to the template that is setup for the E-Signature
Assigned to - Set to the user who needs to sign the document
State - Set to work in progress

The assigned user is then able to see and use the "Sign Document" UI Action in the header of the catalog task which is great.

However, ESS users don't have access to the platform view in the instance I am working in. Is there a way to give them the ability to sign this via the service portal besides the Employee Service Center (I can't use the Employee Service Center, which is the only example I have seen of this working in the portal, because it is a paid plugin that we don't have).

Troy Riblett · ‎08-02-2021

Ended up getting something working for this. Though there was also requirement to generate a document based on variables, but that was its own headache.

Anyway, in order to be able to sign this from the portal the following are the requirements.

There must be a managed document (dms_document) that is in the published state that has the document to sign
The TASK must have a few specific fields set
1. Assigned To - Must be the user who is supposed to sign the task
2. State - Must be "work in progress"
3. Active - Must be true
4. E-signature template (sn_esign_esignature_configuration) - Must point to the managed document that the user must sign
There must be a widget with the e-sign widget embedded inside of it on a page that the user can access (I created a new widget with the below code, and created a new page that had just the widget)
1. The new widget should embed the "e-sign-task" widget using <sp-widget>
2. The widget should pass along the sys id of the task to sign in the widget options
  For example
  HTML
```
<sp-widget widget=data.widget></sp-widget>
```
  Server Script
```
var options = {};
options.table = 'sc_task';
options.sys_id = $sp.getParameter('sys_id');
options.sysId = options.sys_id;
data.widget = $sp.getWidget("e-sign-task", options);
```
3. The above code means that the widget will expect the sys_id to be a URL parameter named sys_id. i.e. the page will be something like INSTANCEURL/sp?id=PAGEID&sys_id=a02baa76dbe5745029d85425f396194f

View solution in original post

kgagrani · ‎04-26-2023

Did you find a solution for this? It not working for me either

Meenal Gharat · ‎05-19-2025

Hello,

Can someone share the widget configuration step in detail

I have created a widget refering to above script how can I test this?

Best Regards,

Meenal Gharat

Sharpy2 · ‎09-24-2024

Hi Troy!

Can you share your Widget Final Screen values? What did you do with Step #3? Was that something to add to the Widget page? Or just know the URL will get created based on those configs for the sys_id of the sc_task record?

Thanks!

kgagrani · ‎04-26-2023

I installed the plugins but getting an error while approving from portal > my approvals

Screenshot 2023-04-26 154116.png

Ramesh Poola · ‎11-09-2023

did you find anything on this, if yes could you please share that because I am also facing same issue.