Skip to main content
Nintex Community Menu Bar
Solved

Elcom intranet integration


rossdefencebank

Hi there, at Defence Bank we currently use Elcom CMS as our intranet. Our current library of procedures are PDF documents uploaded into folders. As we migrate to Promapp, we need to manage the transition. Our thinking was to use minimode links however that doesn't allow users to access embedded processes. We're seeking advice from anyone who has successfully integrated Promapp with an intranet that's other than Sharepoint so we better understand what options are open to us.

Best answer by Damian

Ah yes, that explains that.

We moved off an old Novel intranet a few years ago and we made the decision to move all processes to Promapp. Many proceses were in Word Docs or PDF and while we translated some, we couldn't do them all before the switch over. So we created basic processes with a single activity then uploaded the document. Not ideal but meant that staff only had to look in Promapp for processes, even if some were just documents. We've slowly translated these over the past few years so most are now proper flow charts etc. Not quite what you were after, but an alternative perhaps?
View original
Translate
Did this topic help you find an answer to your question?

4 replies

Damian
  • 29 replies
  • May 28, 2020

Hey Ross,


 


we use SharePoint so can't help with Elcom but thought it was worth mentioning that you can enable Minimodes to access embedded processes.


 


Under configuration (Promaster may need to do this) you can turn 'Enable viewing of underlying processes (Click through)' On (the default is off) which will allow your users to click through to other processes.


 


Hope that helps.


 


Damian

Translate

rossdefencebank

Hi @Damian,


 


Thanks for coming back to me. I forgot to mentioned that our organisation has chosen not to allow access to underlying processes which is part of the challenge.


 


Regards,


Ross

Translate

Damian
  • 29 replies
  • Answer
  • May 28, 2020
Ah yes, that explains that.

We moved off an old Novel intranet a few years ago and we made the decision to move all processes to Promapp. Many proceses were in Word Docs or PDF and while we translated some, we couldn't do them all before the switch over. So we created basic processes with a single activity then uploaded the document. Not ideal but meant that staff only had to look in Promapp for processes, even if some were just documents. We've slowly translated these over the past few years so most are now proper flow charts etc. Not quite what you were after, but an alternative perhaps?
Translate

rossdefencebank

Thanks @Damian, that's a great idea and one of the directions we're thinking of taking.


 


Ideally we'd like to find a way to use the structure we've already built in the intranet but it might be better in the long run to make the transition in a similar way to what you've described and allow the various business owners to evolve their PDFs into processes over time. The benefit of this is we can educate our people to use Promapp from the beginning and we'll also have access to Promapp reporting, rather than running two systems in the interim.


 


Thanks again.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings