8 - Nintex Drawloop DocGen™ for Salesforce

This is an open user-forum, giving you the opportunity to submit new ideas and feedback for Nintex Drawloop Document Generation for Salesforce. It gives us direct user insight on our product, existing features, and may even influence future product releases. Your feedback is highly valued!

- The Nintex Team


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Support File Storage Value Type for Adobe Sign Delivery Option

    Currently, the Adobe Sign delivery option supports the "attachment" storage type. Would like to have this support the "files" storage type

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow multi-factor authentication in the OneSpan integration

    Allowing for specification of a contact and cell phone number for SMS authentication would greatly enhance the integration with OneSpan.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Implement DocuSign Email+SMSDelivery

    DocuSign released an option to send a document to a phone, as an SMS message. User can sign on the phone.
    The current DS integration does not support that feature.
    Please consider to implement this DS delivery option.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  4. O365 Admin Approval required in order to reauthroize 3rd party integration with Nintex Doc Gen

    When in Salesforce and trying to authorize the 3rd party integration with our O365/SharePoint instance we are presented with an admin approval required pop up message. Despite our O365 admins approving the request in O365 the same message is repeated if we go back and try to reauthorize the 3rd party integration. We would like Nintex to fix their product to address this issue with therelated to the admin consent workflow introduce by Microsoft

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. apikey support for SMTP delivery option

    Cut-off Deadline for implementation is December 09, 2020

    Currently the SMTP delivery option works by entering the username (restricted to be an email address) and password

    Most SMTP email delivery services have moved or are moving to an apikey based approach to integration. SendGrid is disallowing user id/password based authentication on Dec 9, 2020

    Request to support apikey based integration with SMTP email services

    In this for SendGrid, the user name would be “apikey” so the form needs to accept a user name that is not in a email format

    Password needs to be able to support the api key…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
    Released  ·  Samuel Sysum responded

    Support for non-email based usernames has now been release, you can upgrade to the latest version of Drawloop to continue using SendGrid.

    One note: when configuring your SMTP delivery option, you will see a new “From Email Address” field, you will want to provide an email address that will be displayed to email recipients when sending your emails through SendGrid. Previously we used the email address from your email based credentials as the From Address, now you will need to define this manually.

  6. Allow font size attribute to be passed to Docusign on Secure Fields

    When creating a Secure Field under a Recipient, we have the ability to specify font family, but not font size. font size is an attribute that is available via the docusign api. I tried to work around it but was unable to because of details I wont go into here.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. Deliver to Google Docs

    We would like to deliver documents straight to Google Docs

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Dynamic CONTACT as a recipient for Adobe Sign, for Community-Portal signing

    We need to be able to send to Adobe via a CONTACT, not an email.

    With Adobe you can have users sign their documents directly inside the SF-Community Portal. For this to work, we need DocGen to be able to send to a CONTACT in stead of an email.
    Currently one can only select a fixed CONTACT. We'd like this to be extended so that we can use a dynamic contact, from either a Relationship or via a button-parameter. Then enter that contact in the Recipient field with a Tag, just like dynamic name/email recipients.

    W/o this feature, we are…

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  9. When email is sent through generate documents , thread Id in email is getting changed after mail is sent(in inbox). Need fix for this

    When email is sent through generate documents , thread Id in Email is getting changed after mail is sent(in inbox). When users reply to this mail the email wont be attached to existing case in salesforce as the thread ID on case is different than the one in mail..Need fix so that case thread id wont be changed after mail is sent.

    The issue wont happen if the mail is not sent through generate documents

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  10. adobe sign and doc gen

    It would great to have a more detailed integration between adobe sign and document generation. Right now the two work very seperate, and during a signature piece, there is no ability to modify something being signed unless it is created in the adobe suite.

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  11. Send on behalf of to Adobe Sign

    We need a way to send agreements on behalf of another user. Ideally this could be allowed/dissalowed on the package level, and granted to specific users via permission set.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Merge documents from AWS CloudFront

    Provide the ability to pull documents from AWS CloudFront and merge into package. Providing the ability to preview before saving the final document will be a real plus.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add Dropbox Integration

    Add Dropbox to the list of 3rd Party Integrations

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  14. Second In person signer routed via LoopPlus

    Using Drawloop with DocuSign

    Able to add a 2nd recipient with In person Signing and routed via LoopPlus.

    i.e the 2nd signer is able to sign (within Salesforce) after the first signer

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Open for voting  ·  0 comments  ·  3rd Party Integration  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base