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 customization candidates with ERP Customization Mining (ERP-CM), ServiceNow customers can leverage additional AI Platform tools to replatform these apps effectively. The process involves using ERP data sources linked in mining results to build new, optimized ServiceNow apps that consume live ERP data without relying on legacy code.
Show less
Building New Apps Using ERP Data
Customers should use the remote tables and extraction tables from ERP-CM results as direct data sources when developing new apps on the ServiceNow AI Platform, such as with App Engine Studio. Consider pulling data directly from third-party sources when possible to streamline data retrieval and improve app efficiency compared to legacy systems.
Designing Apps for Similar Customization Candidates
When ERP-CM identifies multiple similar candidates, it is practical to create a single app that addresses the needs of several candidates simultaneously. Replatforming offers an opportunity to redesign legacy apps using low-code tools, improving functionality and consolidating multiple legacy systems into one ServiceNow app.
Using ServiceNow Low-Code and Pro-Code Builders
ServiceNow provides various development tools suited for different skill levels and licensing, enabling rapid app creation from ERP data. Builders include:
- App Engine Studio
- Workflow Studio (Flows and Playbooks)
- Table Builder
- UI Builder
- Workspace Builder
These tools allow incorporating remote tables and ERP data models seamlessly, facilitating integration of legacy ERP data with existing ServiceNow data.
Accessing ERP Data Programmatically
The Glide API enables developers to query ERP system of record data directly, supporting advanced customization and integration scenarios. Sample queries are provided in ERP-CM documentation to guide development.
Post-Replatforming Actions
Once an app is replatformed on the ServiceNow AI Platform, it operates using live ERP data via ERP Data Hub’s remote and extraction tables, eliminating the need for legacy code interaction. If legacy code is no longer referenced elsewhere, customers can safely remove it from the ERP system to reduce complexity and maintenance overhead.
After you use ERP Customization 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 ERP Data Hub 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, 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 an example Gilde query, see Sample Glide query for ERP data in ERP Customization 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 ERP Data Hub 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.