Next steps when replatforming apps to ServiceNow using ERP Semantic Mining
Summarize
Summary of Next steps when replatforming apps to ServiceNow using ERP Semantic Mining
This content guides ServiceNow customers through the process of replatforming legacy ERP (Enterprise Resource Planning) applications to the ServiceNow AI Platform using ERP Semantic Mining. It explains how to identify candidates for replatforming, utilize ERP data effectively, and build improved applications leveraging ServiceNow’s low-code and pro-code tools. Additionally, it provides important context about the status of ERP Semantic Mining and best practices for transitioning from legacy ERP systems.
Show less
Key Features
- ERP Semantic Mining: Used to identify legacy ERP customizations suitable for replatforming. It highlights related remote and extraction tables for efficient access to ERP data.
- Building Apps on ServiceNow AI Platform: Enables creation of new applications that consume ERP data directly, potentially replacing legacy retrieval methods such as Zero Copy Connector models that add extra steps.
- Handling Similar Candidates: Encourages consolidating multiple similar ERP custom apps into a single, better-designed ServiceNow app using low-code tools.
- ServiceNow Builders: Offers a variety of tools depending on licensing and skill level, including ServiceNow Studio, Workflow Studio, Table Builder, UI Builder, and Workspace Builder to rapidly develop apps that incorporate ERP data and custom fields.
- Data Access via Glide API: Supports querying ERP data programmatically, facilitating integration and customization.
- Legacy Code Management: After replatforming, the legacy ERP code can be safely removed if it is no longer referenced, with all live data accessed through remote and extraction tables via Zero Copy Connector for ERP.
- Important Notice: ERP Semantic Mining is being prepared for deprecation starting with the Zurich release; it will no longer be activated on new instances but will continue to be supported.
Key Outcomes
- ServiceNow customers can effectively identify and migrate legacy ERP customizations to modern ServiceNow apps, improving maintainability and user experience.
- New apps built on the ServiceNow AI Platform can directly consume ERP data, simplifying data retrieval and integration.
- Customers can leverage ServiceNow’s low- and pro-code builders to rapidly develop and iterate on replatformed applications without replicating legacy designs exactly.
- By consolidating similar ERP candidates into unified apps, customers reduce redundancy and streamline application portfolios.
- Post-migration, customers can decommission legacy ERP customizations safely, reducing technical debt and operational complexity.
After you use ERP Semantic Mining to identify legacy ERP (Enterprise Resource Planning) candidates, use additional ServiceNow AI Platform products and resources to replatform your app.
First, identify the customization you want to replatform from the ERP system with ERP Semantic Mining.
Then, use the remote tables and extraction tables linked in the candidate mining results for fast access to ERP data.
That ERP data can be used as a data source when you build new apps on the ServiceNow AI Platform, for example, with ServiceNow Studio.
Build a ServiceNow app that consumes ERP data
The next step in replatforming with ServiceNow Studio for ERP (Enterprise Resource Planning) is to build an app on the ServiceNow AI Platform that consumes the ERP data.
As you plan to replatform a legacy app on the ServiceNow AI Platform, consider where the data is coming from. For example, an old app may retrieve data from a third party into the system of record. When you build a new, replatformed app on the ServiceNow AI Platform, you can configure the new app to pull data directly from that third party. Using that method, the Zero Copy Connector for ERP model no longer pulls the data from the ERP system, which adds an extra step of retrieval.
Working with similar candidates when replatforming apps
If ERP Semantic Mining shows that a candidate has a number of similar candidates, consider building one app that meets the needs of some or all similar candidates when you replatform.
When you replatform a custom app from the system of record, you don't have to replicate the old app exactly. Use the replatforming process to design a better app. For example, an app that addresses the needs of multiple similar candidates in a single, new app built using low-code tools on the ServiceNow AI Platform. ServiceNow Studio is the quickest app to use, but there are other builders available to you, depending on your licensing.
ServiceNow low- and pro-code builders
After you identify ERP data to replatform, citizen developers can use ServiceNow builders to create apps quickly from the data. Any custom fields that exist in the ERP system of record, such as SAP, can be leveraged by the apps you build using the ServiceNow AI Platform.
For example, use in ServiceNow Studio, use a template (or build the app from the ground up) and incorporate remote tables using ERP models and remote tables. You can combine legacy data from the ERP models and remote tables with other ServiceNow data in tables.
Using Glide to query ERP data
You can also access data from the system of record through the Glide API.
For more information, see Sample Glide query for ERP data in ERP Semantic Mining.
After you replatform custom code to a ServiceNow app
Replatformed apps on the ServiceNow AI Platform use live data from the system of record without writing any code back to it.
After you have identified candidates to replatform and taken the recommended action in ERP Semantic Mining, you must only use Zero Copy Connector for ERP to access the remote tables and extraction tables. These tables are data sources for building apps, flows, and workspaces.
If you're sure that legacy code on the system of record isn't referenced elsewhere, you can remove it from the system after it's replatformed.