PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution
Using it in the application support team is worth it as it is capable of carrying a lot of information. But using it for a Service Desk operation might not be of much use as it won't be used up to its full potential and will be costly as compared to other alternatives available in the market.
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
It helps put manage the request really well. It is easier to create a request, track the request and manage the request. It doesn't get lost into a pile of requests.
We've already pre-setted some settings into our ServiceNow. So it automatically assigns the level of urgency and mentions on the ticke if its a high or low priority request.
I really like the ServiceNow dashboards. They ate setup in a really nice way. The dashboards show the real time data aswell as old data incase if we need to see if there is a pattetn in the request or to fix any recurring issue.
PowerApps has a great coding option, but there are some pieces of the tool that the requirement to understand code is a barrier to fun if the user doesn't code.
MUCH time can be spent looking for solutions on this young platform and the body of forum/help/lessons learned is not as robust as it will be in a few years.
Like many early-stage Microsoft products, PowerApps is a relatively blank slate that will be improved by the feedback of their users and ongoing feature development. Right now it seems that the product lacks a critical mass of use-case driven templates (there are some, but I haven't yet found one that didn't require more work to customize it to my need that it would take to build my own tool).
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
While we are very likely to renew, we are also assessing if we should renew all of what we currently subscribe to as we try to reduce costs. Some parts of the business feel there may be a better tool out there to fit their process requirements. We are currently working with them to identify what those requirements are to see if it makes sense while also pointing out a reduced cost of tooling is not always the best fit if we have an increased cost of customization and maintenance between tools.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
ServiceNow is a web platform that does not require any installation on a customer's computer. It is very easy to use and it is user-friendly. The customer started to open incidents very fast without investing time and money in training. Customer loves the dashboard at the startup where they can see all their open incidents or look at KB articles for any issue.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
The platform is provided as a SaaS solution and support from the vendor has been good. There are regular software releases with bug fixes, new features and enhancements, and furthermore we are given the opportunity to fully test these before rolling these new releases out into the production environment to minimise the risk of business disruption
We went through a re-implementation last year with a partner and were very pleased with the outcome. We looked at several partners and chose one that was able to provide an entire scope and cost upfront of what would be required to complete our requirements. We worked very closely with the dedicated team assigned to our project throughout the process and they fully delivered on all of our requirements that we presented in the initial scope.
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.
ServiceNow was chosen as replacement for Microsoft Project , due to better licensing model, more flexible configuration of the project stages and components, better API with Azure DevOps. Also ServiceNow is best in the area of Incident and Service management systems and the proof of concept with Jira and incident.io were not successful and we kept relying on ServiceNow. ServiceNow is much more scalable than MS Project for constantly growing enterprise companies for both employee and external contractor type personas.
The biggest positive impact ServiceNow has made to our organization is reduced IT support cost. When we didn't use ServiceNow, we needed a bigger support team. Now we don't need as many support employees.
The other positive impact that I've noticed is faster solutions to any problems. ServiceNow makes very easy to resolve IT issues, in a efficient way. The tickets are organized in a way that the higher priority tickets get worked on quicker.
The dashboard has also made the job easy to find a recurring problem from its core and fixing it forever so that we don't repeatedly get the same issues again and again
