Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Add a new idea Subscribe
Status Open for voting
Workspace Nintex Automation Cloud (formerly Nintex Workflow Cloud)
Categories Other
Created by Guest
Created on Aug 7, 2020

RELATED IDEAS

Generate PDF with PDF Security Applied

Nintex o365 Document Generation action missing standard functionality. After the PDF file is generated and sent to the end user, the user who receives this PDF file can actually make changes to the file using a PDF editor tool. The ability to secure a PDF to only be viewed and printed using a password or completely locked down from changing before sending out to the end user.

We use a workflow in a critical financial system and we would like to have this feature added. It could either be password or certificate security, but just need the ability to prevent edit. I have attached a screen shot of how a file is locked down in Adobe along with the settings we are looking to disable as example.
  • ADMIN RESPONSE
    Sep 7, 2022
    Thanks for your feedback.  Opening this for feedback to get a sense of what others think and prioritize based on votes.
  • Attach files
  • Guest
    Reply
    |     Sep 7, 2022
    This is an extremely important feature if we implement this action in a critical system.
  • Guest
    Reply
    |     Sep 7, 2022
    We definitely need this functionality. The output documents our clients are generating contain PII and need to be secured with a password.

    We're working primarily with Salesforce. I could think of a couple different use cases. First, let SFDC control creating the password and storing it with the record. It would then become another field that could be passed in via the field tagger. Second, have Nintex create the password and provide the information in an email or separate document and/or update a field with the information.

    As the OP mentioned, we would also need to have control over whether the password provided Read-Only or Read/Write capabilities.