I was wondering if anyone has tried biulding a solution for mailroom automation with Nintex. I was given the task for creating one which includes:
The business process is not set in stone, so I am open to ideas on how you manage your incoming and outgoing (paper-based) mail.
Been there, done that. (exactly that.) It was a long and somewhat painful project. It required forms, workflows as well as a lot of code.
The most painful part was the "who has access to which document" magic algorithm. It led to breaking the privileges inheritance and I fear the moment that SharePoint will start to complain.
Let me know if I can help somehow.
Geia sou, Dinos
I'd love to hear about your experience and maybe in process of gaining more insight we could also gain some ideas which can help both (and others). So to start with what intrigues me most - how did you realize the barcode part?
As for the unique permissions part - I agree it bothers me too. The threshold is 50K, if I'm not mistaken, and maybe a workaround would be to export the items, say on an annual basis to a separate list. Then give access to this list only to people who might need to access the archive.
Thank you in advance!
Hi Dimiter, (I apologize for failing to return your warm greeting in Bulgarian )
I will try to be as short and concise as possible:
DocumentIdProvider class documentation on msdn
So, if somebody gives me the document id ALIN00001, I know that it was generated in site ALpha, in library INvoices and it is the 1st invoice.
I hope I did not confuse you too much! We implemented this on premises, it should be possible to do on o365 but it will require more work.
Dinos, we are just starting to build this workflow (that's why it took me so long to reply) but we have an idea how to overcome the unique permissions. Our requirement might be different than yours but hopefully it gives you ideas at least
We need to give permissions per department and to define those we will use AD groups nested within SharePoint groups. Then we will enable the feature to create folders in the list and will give permissions to each folder for a particular department. We will then move the items (by means of the workflow) to a specific folder (for the particular department) - the "Create item in another site" action allows working with folders. In the end we will modify the view so that it shows a "flat" structure (without the folders).
Thus, you break the permissions at a higher level - the folder, and for us this seems lile a much better option - 50 unique permissions vs. 8000
Hope this helps!
Breaking the permissions using folders is definitely a much better approach.
Unfortunately our requirement was to "deliver" the documents to any combination of employees or AD groups. (eg an invoice delivered to the accounting dept and the group/user that made the purchase order).
As a solution we are planning an archiving mechanism that will keep the "active" libraries lighter.
Wishes for bug free implementations!
I see. If it's too dynamic then I guess there aren't many options other than item-levem permissions.
Our requirement was that departments like Procurement, Accounting or Controlling always have access to all documents. It's only the initiators that need to see their own items (by department).
Still I think you are on the right track with the archiving thing. Maybe a workflow that can copy items to another list and then delete them.