The only area for improvement I experienced while working on Conga Sign is that the setup is quite complex; the initial implementation takes some time. The integration can also be a bit time-consuming because Conga Sign does not accept rest APIs or OAuth, requiring me to convert the APIs into OData.svc formatted APIs. This requires significant resources and MuleSoft support for some. Additionally, the licensing cost can be on the higher side for small organizations, but for my large organization, the cost is manageable. The biggest challenge when deploying Conga Sign is maintaining the solutions throughout the development environments. I have multiple sandboxes, production staff, validation parts, and UATs, and deploying each solution from one org to another can be quite challenging, requiring manual deployments and precision.
Sometimes Conga Sign creates issues where we have to go to Conga Sign setup and reconnect it again. Since we are using Conga Sign as a package in our Salesforce ecosystem, sometimes the package versioning has changed, so we need to check for the latest version and upgrade it. Occasionally, Conga Sign troubles us, requiring refresh actions that create some issues. This does not happen often, but it happens sometimes. Sometimes the solution that we are providing in the document does not accept all data types. We use text, lookup, and other standard fields, but sometimes it will not allow rich text, formula fields, and those kinds of data types in a Conga Sign document.
I cannot say much about how Conga Sign can be improved. As of now, I do not see any issues or necessary improvements. I can say that it would be helpful to provide more guidance. If someone is new to using Conga Sign, they need to be more aware. Providing guidance or even videos for them would be more efficient for customers as well.
Sometimes we require sending multiple documents for signatures, which is still not supported. This could be improved. I would like to add that some businesses still do not consider digital signing of critical documents a legitimate way.
From my perspective, there is no need for improvement as all projects have been completed quickly. If it were possible to send multiple documents for signatures immediately as a batch without having a user interface, that would be useful. For example, for one year, we need to send documents for signatures for additional terms and conditions, and if we had a setup for bulk signing, it would be more beneficial. We mostly need to update the UI for bulk document signatures. If a feature for that were available, it would be more useful.
If there was the ability to have some kind of warning or alert for sales reps, indicating that a contract is already out for signature before they send a second one, it would greatly reduce confusion. Currently, when reps send out a new contract for signature without canceling the previous one, it leads to unnecessary reminder notifications.
There is room for improvement in ensuring data residency compliance, as some clients express concerns about data processing transitioning to other servers. Another area could be its limited features when using it outside Salesforce, especially on public websites.
Conga Sign offers seamless integration with Salesforce, simplifying digital signature processes with ease of use and efficiency. It allows quick setup, enabling users to streamline document handling and secure electronic signatures efficiently.Conga Sign integrates with Salesforce to enhance document generation and digital signature processes. Features like drag-and-drop signature capability and automated email transactions reduce manual overhead and enable fast, secure document handling....
The only area for improvement I experienced while working on Conga Sign is that the setup is quite complex; the initial implementation takes some time. The integration can also be a bit time-consuming because Conga Sign does not accept rest APIs or OAuth, requiring me to convert the APIs into OData.svc formatted APIs. This requires significant resources and MuleSoft support for some. Additionally, the licensing cost can be on the higher side for small organizations, but for my large organization, the cost is manageable. The biggest challenge when deploying Conga Sign is maintaining the solutions throughout the development environments. I have multiple sandboxes, production staff, validation parts, and UATs, and deploying each solution from one org to another can be quite challenging, requiring manual deployments and precision.
Sometimes Conga Sign creates issues where we have to go to Conga Sign setup and reconnect it again. Since we are using Conga Sign as a package in our Salesforce ecosystem, sometimes the package versioning has changed, so we need to check for the latest version and upgrade it. Occasionally, Conga Sign troubles us, requiring refresh actions that create some issues. This does not happen often, but it happens sometimes. Sometimes the solution that we are providing in the document does not accept all data types. We use text, lookup, and other standard fields, but sometimes it will not allow rich text, formula fields, and those kinds of data types in a Conga Sign document.
I cannot say much about how Conga Sign can be improved. As of now, I do not see any issues or necessary improvements. I can say that it would be helpful to provide more guidance. If someone is new to using Conga Sign, they need to be more aware. Providing guidance or even videos for them would be more efficient for customers as well.
Sometimes we require sending multiple documents for signatures, which is still not supported. This could be improved. I would like to add that some businesses still do not consider digital signing of critical documents a legitimate way.
Everything is satisfactory based on my initial experience. However, different languages would be a needed improvement.
From my perspective, there is no need for improvement as all projects have been completed quickly. If it were possible to send multiple documents for signatures immediately as a batch without having a user interface, that would be useful. For example, for one year, we need to send documents for signatures for additional terms and conditions, and if we had a setup for bulk signing, it would be more beneficial. We mostly need to update the UI for bulk document signatures. If a feature for that were available, it would be more useful.
If there was the ability to have some kind of warning or alert for sales reps, indicating that a contract is already out for signature before they send a second one, it would greatly reduce confusion. Currently, when reps send out a new contract for signature without canceling the previous one, it leads to unnecessary reminder notifications.
There is room for improvement in ensuring data residency compliance, as some clients express concerns about data processing transitioning to other servers. Another area could be its limited features when using it outside Salesforce, especially on public websites.
The integration of Conga Sign with Conga Composer could be better.
The solution accepts only a few data types and not all data types.
Sometimes, the tool creates an issue, and we have to go to the Conga Sign setup and reconnect it again.