I couldn’t find any documentation explaining this great new addition with 23R2. There are a couple of slides in “IFS Cloud 23R2 - Whats New in Asset Management,” which I have added below.
But that doesn’t explain the process flow or the integration.
I found two community posts that also only provide very little info.
Follow the links from the activities there to see the details.
Thanks @Mathias Dahl - Will give it a go.
Cheers
By the way, you asked about how to get it to work. Very little is needed, actually, once a customer has bought it. Actually, there is no setup needed at all, apart from setting up Docman as usual (document classes, repositories, etc.)
One important thing to mention though is that we don't support the Esign functionality in Remote Deployment in this release. We want to enable it for Remote as well at later time, but when is not decided yet.
I'm demo environments, you should be able to ask IFS IT department to enable it via a case.
@Mathias Dahl - Manged to get this working in a Partner Enablement Environment. Thanks for your help.
@Mathias Dahl - Manged to get this working in a Partner Enablement Environment. Thanks for your help.
Perhaps, for the benefit of others, you can tell us what you did?
Hello @Mathias Dahl
This thread is a little old but I think it’s good to keep the content together. I’m getting this highly informative error message, might you be able to give me a clue as to what the problem is?
Hello @Mathias Dahl
This thread is a little old but I think it’s good to keep the content together. I’m getting this highly informative error message, might you be able to give me a clue as to what the problem is?
I will make a guess once you told me the context Which environment is this, to begin with? The more details, the better. On a high level it just said it could not send the document for signing.
This is a remote database, not hosted by IFS. I imagine that this is the type of error message that pops up when you don’t have a hosted environment.
Correct. The Esign solution doesn't yet support Remote deployments. It's a deliberate, therefore also known and documented restriction.
One could discuss whether it's wise to keep that command enabled in Remote deployment and it might seem like there is a simple answer, but it's quite nuanced...
@Mathias Dahl Thank you for your time on this. I think the better solution would be to make it work for all type of installations or hook-up to DocuSign. It seems that everyone wants to do things electronically.
Indeed, and that's the plan. Aimed at 25R2, but we are not making any promises.
