I've reached out to Nintex support many times and have not received the help I need so I'd like to turn to the community for support.
I was able to successfully add the Trial version for both 'Workflow for Office 365' and 'Nintex Forms for Office 365' to my tenant, as I can see both Apps when viewing my Site Contents and in the ribbon when in my custom list.
However, BOTH icons, when clicked, are not functioning as intended!
Is there anyone out there that has experienced this problem and found a solution? Nintex Support is not very quick and I have a deadline coming up to present to my managers.
Thanks for the reply @SimonMuntz
After opening the SharePoint site again on Edge (without incognito/private mode) the Nintex Forms is now working!
Unfortunately, the Workflow component is still not working. I've added the listed addresses to my Trusted Sites but to no avail. Are there any other recommendations you might have?
Hi @SimonMuntz ,
Please disregard the previous message. I was able to finally connect SharePoint Designer 2013 with my site collection and was also able to create and publish a basic workflow on a custom list.
I believe this confirms access to the SharePoint Workflow engine you've mentioned previously. However, when going back into my custom list and clicking on 'Nintex Workflow' in the ribbon, I am still seeing the "Oops... something went wrong'' message.
Can you please advise me on next steps?
Thank you for your time and patience,
I followed the Knowledge Base article exactly as written and still can not access the Workflow for Office 365 application. I've deleted both apps from Site Contents, from the App Management module in SharePoint Admin Center, re-added the app both in the site collection and in the SharePoint Admin Center. I've attached pictures for your reference.
I've also tried creating a new site collection and adding Nintex there. Same issue: Nintex Forms launches fine but Workflow for Office 365 still shows the 'Oops... Something went wrong' error.
Is there any way we can set up a Teams or WebEx session to help troubleshoot?