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

[Troy Riblett]

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 · Accepted solution]

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.

1. There must be a managed document (dms_document) that is in the published state that has the document to sign
2. 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
3. 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 

[DanielCordick]

Hey Troy,

This is awesome Thanks! one thing. when going to draw a signature the draw pad is greyed out. Do you have the same issue

how did you fix this if you did?

[Troy Riblett]

I think that happened to me and it was due to the widget dependency unassociating for the E-Sign Pad widget (I created a copy of the widget and assumed that was why it happened. Maybe you did the same?).

Anyway, make sure that it has a dependency on JQuery_SignaturePad.

I think I remember the dependency field being blank, so I had to open that record, set the dependency field to JQuery_SignaturePad and save it. If that's not it... Then I don't know. Sorry

[k_lutz]

Hello Troy,

Very helpful posting. I am trying this out in my PDI but the signature pad is not appearing even though I have added the dependency. Any ideas?