Skip to main content

IFS Electronic Signature feature ("E-sign") - questions and answers

  • October 17, 2024
  • 4 replies
  • 276 views

Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32

What is it?

 

The E-sign feature is available from IFS Cloud 23R2 (Cloud deployment only, Remote currently not supported). At its core it's an integration between IFS Document Management ("Docman") and Adobe Acrobat Sign.

In order to send a document for signing you need to first upload it to Docman, release it, and attach it to some screen/business object. For details on the process, watch the video linked below.

https://www.youtube.com/watch?v=Aed1j9VOPDU

 

Agreements/envelopes

 

When you send a document for signing to one or more recipients an "agreement" is created in Adobe Sign. The agreement acts like a container for the document and the list of recipients, and supports the whole flow from sending, signing and retrieving the signed document. As of 24R2, you can only send one document per agreement. An agreement in Adobe Sign is what other E-sign solutions sometimes calls "envelopes."

IFS keeps track of every agreement that has been created and, to use a term that's more known and to keep the possibility of integrating with other providers, we are also using the term "envelope" inside IFS.

 

My customer needs to send 10 documents for signing every week - how many agreements do they need?

 

Since 1 document sent for signing = 1 agreement used, the customer needs one agreement per document they want to send for signing. This is regardless of how many recipients sign the document.

Agreements are sold in packs of 100 and they are valid for a month. An agreement never expires but IFS keeps track of how many agreements are used and compares that with the number of agreements a customer has bought. If a customer uses more agreements than they have paid for, then can expect a sales person calling them, asking if they want to buy another pack 🙂

To answer the question above, the customer needs 10 agreements per week x 4 weeks = ~40 agreements per month = 1 pack of 100 agreements per month.

 

Does the customer need to create their own Adobe accounts?

 

No. When a customer orders the E-sign feature, an Adobe account is automatically provisioned and connected to IFS's master Adobe account.

 

Can a customer use an already existing Adobe account that they have created themselves?

 

No.

 

Is there any documentation?

 

Yes!

About E-Sign - https://docs.ifs.com/ifsclouddocs/24r2/SearchForAndUseDocument/AboutESign.htm?StandAlone=true

 

E-sign process model - https://docs.ifs.com/ifsclouddocs/24r2/ProcessModels/Process_Model/SendandReceiveDocumentforESign.htm?StandAlone=true

(click the green boxes/activities to read about each step)

 

4 replies

ctaylor56
Hero (Partner)
Forum|alt.badge.img+14
  • Hero (Partner)
  • 163 replies
  • January 7, 2025

@Mathias Dahl , we are struggling to get this working for a customer.  Customer has purchased their envelopes, but it seems the back-office (IFS Managed Services) process to “enable/activate” this feature in the customer use place environment is somewhat disjointed.  Support ticket opened for months and endless emails.  Not sure if you can offer any advice or assistance.


Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Author
  • Superhero (Employee)
  • 2826 replies
  • January 9, 2025

@ctaylor56 

There is a known problem with the esign solution in the internet-facing managed IFS Cloud environments. The esign solution works beautifully internally at R&D, but "something in the Kubernetes cluster" is messing up the communication between some containers/pods in there. Teams at R&D are looking into this problem as we speak.


Forum|alt.badge.img+1
  • Do Gooder (Partner)
  • 2 replies
  • March 28, 2025

@Mathias Dahl in another post on this topic you metioned that “A special SKU is needed, that will grant a pack of esign transactions. The customer does NOT need any Adobe licenses of their own.”

Are you able to provide the SKU and any information on the appropriate way to obtain pricing on behalf of a customer?

 

In the initial email interaction with the customer sales representative, the customer was directed to open a ticket regarding this which would allow the sales contact to provide additional follow up.  Upon opening the support ticket, it was rejected as “out of scope” and we were directed to open a topic on IFS Community instead. ??? 

/Brent


Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Author
  • Superhero (Employee)
  • 2826 replies
  • March 31, 2025
bmarxhausen wrote:

@Mathias Dahl in another post on this topic you metioned that “A special SKU is needed, that will grant a pack of esign transactions. The customer does NOT need any Adobe licenses of their own.”

Are you able to provide the SKU and any information on the appropriate way to obtain pricing on behalf of a customer?

 

I'm sure I can get hold of the SKU number/ID for you, but that doesn't seem like the right way to solve your issue below.

bmarxhausen wrote:

In the initial email interaction with the customer sales representative, the customer was directed to open a ticket regarding this which would allow the sales contact to provide additional follow up.  Upon opening the support ticket, it was rejected as “out of scope” and we were directed to open a topic on IFS Community instead. ??? 

That's really strange. The SKU for the Esign solution (or the transaction bundle, really) is no special from any other SKU I think. I suggest you push back on that strange recommendation. You don't order things on IFS Community.

Or, could it be that the customer is Remote hosted? The Esign solution is not supported in Remote yet.

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings