Next steps when replatforming apps to ServiceNow using ERP-CM
Summarize
Summary of Next steps when replatforming apps to ServiceNow using ERP-CM
After identifying legacy ERP app candidates with ERP Semantic Mining (ERP-CM), ServiceNow customers can replatform these apps onto the ServiceNow AI Platform to modernize and optimize their business processes. This approach leverages ERP data through remote and extraction tables, enabling the creation of new, efficient applications without replicating outdated designs.
Show less
Key Steps for Replatforming
- Identify customizations: Use ERP-CM to pinpoint ERP customizations suitable for replatforming.
- Access ERP data: Utilize remote and extraction tables linked in ERP-CM results to quickly access ERP data, which serves as the foundational data source for new apps.
- Build apps on ServiceNow AI Platform: Use tools like App Engine Studio to develop apps that directly consume ERP data. Consider optimizing data flow by connecting new apps directly to third-party sources when applicable, avoiding unnecessary retrieval layers.
- Consolidate similar candidates: When multiple similar ERP candidates exist, design a single, improved app that addresses the needs of multiple business units or functions, rather than replicating each legacy app.
Utilizing ServiceNow Builders
ServiceNow offers a range of low-code and pro-code builders to accelerate app development using ERP data, including:
- App Engine Studio
- Workflow Studio (Flows and Playbooks)
- Table Builder
- UI Builder
- Workspace Builder
These tools enable citizen developers and professional developers to create apps that incorporate ERP system custom fields and data models. Apps can combine legacy ERP data with other ServiceNow platform data for comprehensive solutions.
Accessing ERP Data Programmatically
Developers can query ERP data directly via the Glide API, allowing integration of live data from the system of record within ServiceNow applications. This supports dynamic data access without duplicating data storage.
Post-Replatforming Actions
- Use the Zero Copy Connector for ERP to interact with remote and extraction tables, ensuring up-to-date ERP data consumption without modifying the source system.
- After validating that legacy ERP custom code is no longer in use, safely remove it from the system of record to reduce maintenance overhead.
This replatforming approach enables ServiceNow customers to modernize legacy ERP applications efficiently, leveraging AI-driven insights, low-code development, and seamless data integration for improved agility and business value.
After you use ERP Semantic Mining (ERP-CM) 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-CM.
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 App Engine Studio.
Build a ServiceNow app that consumes ERP data
The next step in replatforming with App Engine 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 instead of having the Zero Copy Connector for ERP model pull it from the ERP system, which adds an extra step of retrieval.
Working with similar candidates when replatforming apps
If ERP-CM 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, perhaps one that addresses the needs of multiple similar candidates in a single, new app built using low-code tools on the ServiceNow AI Platform. App Engine 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 more on citizen development, see Delegated development and deployment.
For example, use in App Engine 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've identified candidates to replatform and taken the recommended action in ERP-CM, you need to use only 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 the legacy code on the system of record isn't referenced anywhere else, you can remove it from the system after it's replatformed to a ServiceNow instance.