Topic
Instructions
Verify the following requirements for the running User:
- Contains a License for the Nintex DocGen application.
- Contains the DocGen User Permission set.
- Contains the Salesforce API Enabled Permission on profile or permission set.
- Add the Profile to the Nintex DocGen for Salesforce Connected Apps setting for Admin approved users are pre-authorized.
- Verify the profile is on the Availability section of the DocGen Package.
- Verify the Salesforce Sharing Settings for External Access are Public Read/Write for the Nintex DocGen Object - DocGen Package and any other Nintex DocGen Objects needed for the user generation experience.
- The user has access to all fields and Objects in DocGen Package Relationships.
- All objects from the Relationships are Public Read/Write in Salesforce Sharing Settings.
- If the Community User requires access to Salesforce Files / Content / or Libraries - the user must have the correct Salesforce License Type: Customer Community Plus to access or store documents.
- If Attaching back to a Salesforce Record - The user must have permission to add Files to that record.
- Any Buttons for Community Users must contain the Community Site name in the button. You will want a separate button for community users and internal users for the page layout:
- example "/community/apex/loop__looplus?eid="
- Merge images from RichText Fields:
- This may require the instance to be appended if using a button:
Instance Parameter for Button
- This may require the instance to be appended if using a button:
- Allow Community User to Send emails:
- The profile must have the following Salesforce Permissions enabled:
- Send Email
- Mass Email
- Allow sending of List Emails
- Read Access to the Documents Object in Salesforce.
- This is where the Generated Document is temporarily stored before sending the email.
- The profile must have the following Salesforce Permissions enabled: