Edmonton, Alberta — December 3, 2019 — Elantis Solutions Inc. announced that it is the only company in the world with two Nintex virtual Technical Evangelists (vTEs) on staff. There are only three vTEs in Canada – and less than sixty in the world – making this a unique competitive advantage for Elantis.
The Nintex vTE program allows vTEs by invitation only. To achieve and maintain Nintex vTE status, a vTE must stay cutting edge on technology advances and demonstrate their proficiency by leading pre-sales discussions and delivering effective solutions for clients. They must also be regular contributors on Nintex Connect, Nintex’s technical forum.
“vTEs show a passion for not just Nintex but also for technology,” says Dan Stoll, Nintex Manager – Technical Product Marketing & Evangelism. “They genuinely want to help, whether it be through the Nintex community, Nintex user groups (which a number of them run), or just being out in the channel helping customers realize the potential of solving one workflow at a time, and how transformative that can be to their business.”
Elantis has had Nintex vTE Rhia Wieclawek on staff in Vancouver, BC for over two years. This week’s addition of a second vTE in Edmonton, Alberta – Julian Charles – continues Elantis’ reputation for attracting highly qualified resources.
“Having two Nintex vTEs at Elantis supports our strategy to continue to expand across North America,” says Dave Roe, Elantis CEO, “but more importantly, it strengthens our ability to provide technology solutions that meet our customers’ needs. As we continue to focus on providing real value to our customers, we attract like-minded individuals to work with us.”
To learn more about Elantis’ partnership with Nintex, visit www.elantis.com.
Process excellence is a lofty goal, but many organizations struggle to get a hold of it. How can you simplify this journey?
What are the digital transformations trends shaping 2020? Let’s unpack a couple of these and understand where you can stay ahead of the technology curve.
Can I use one Microsoft Flow for multiple libraries? I could Save As, but then I’d have to make updates to each Flow individually. Is there a better way?