No, I didn't. I finished up with showing the users ARIS Express program and described the processes with its help. That was done for "as is" part of the project. I was disappointed that there were no ready process maps for all modules prepared in some standard notation ("to be" part). IMHO those maps should be prepared by the module maintainers and integrated deeply into documentation (and source code, i.e. put under source control into the master branch). They should provide user friendly and DRY alternative to documentation in html / text format. On my project the partner preferred to send videos and tutorials (screencasts) to the users when they had questions. In my opinion it's suboptimal since you cannot scroll video (playing it on 10x speed is nonsense), it's non machine readable, greedy for resources etc.
SUMMARY:
1) video tutorial / screencast = good for introduction, not good at all for processes description,
2) html or plain text documentation = suboptimal solution (better than nothing, but for a complex ERP system trying to reach users and blow the market it's definitely not enough),
3) process maps with all the details (events, states, transitions etc.) integrated into the code as tight as possible - is the way to go for the community / partners / vendors
