React is a JavaScript library for building user interfaces. React enables users to create interactive UIs. Design simple views for each state in an application, and React will update and render just the right components when data changes. React is available free and open source under the MIT license.
N/A
ServiceNow Now Platform
Score 8.6 out of 10
N/A
The ServiceNow Now Platform is a digital workflow building and extension tool for ServiceNow featuring a number of low-code / no code tools.
React is a JavaScript user interface construction library that works well for:
Developing web apps with dynamic and complicated user interfaces.
creating reusable UI elements that may be used in other applications.
creating single-page applications with dynamic content updates that don't require a page reload.
The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.
React, on the other hand, might be less suitable for:
Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
When creating mobile apps, React Native is a better option.
Server side rendering only, as React is designed to run on the client side.
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.
React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.
Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.
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.
Everybody in the company is happy to use ServiceNow. All people are happy to use a user-friendly web tool in order to open IT incidents. IT people can easily support people with a stable and solid tool.
React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
As a regular user of the ServiceNow platform, including the incident management, change management and enterprise application management modules, I find that I am able to competently use the platform with minimal training and assistance. User guides are available from the vendor if required. The customisable front-end that we use in the organisation as an ordering tool for internal IT services is very easy to use, and makes searching for the required IT service simple for business users.
Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
We have many levels of interaction with ServiceNow. The first line of support sometimes is not equipped to resolve more complex issues, but the escalation process is clearly defined and followed with limited friction. Our account team is very responsive and willing to brainstorm ideas to improve and increase usage. We also have direct interaction with product teams to see previews of new features and at times to provide input to influence implementation details.
While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance
ServiceNow is by far a better tool over Remedy. Its ability to integrate so seamlessly to so many tools allows for plenty of opportunity to streamline and improve processes. Servicenow has intuitive flows that allow you to quickly pivot if process change. Its adaptiveness is what makes it far better solution over Remedy
1. It is not great when they can't seperate apps/products from a particular sku, forcing you to make a business case for a larger portion of functionlity than your current business case seeks to address. 2. ServiceNow reps are able to work with you when economies of scale are projected out. They are willing to start at a desired tier and provide pricing at applicable upgraded tiers
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
Ensuring good service support internally and externally has triggered opportunities to sustain good links with everyone and opened the door to more sales and successful business and ServiceNow has been key in all this, so the investment came back to us faster than expected.
