The System name field represents the name of the system that is associated with a data source. The system name is used to display the source systems for a data type on the External Data Entities landing page (The External Data Entities landing page provides a single, consolidated view of the external data entities that can be leveraged in the application).
For example, if your data source is a REST connector that connects to an external weather service such as Google Weather API, you can enter "Google Weather" as the system name.
Same question. It would make more sense to have a System identifier for records that are fetched from an external system.
So I am more interested to know, if the Data Page is associated to a PRPC System Identifier, given that data is sourced locally (say via a Report Definition), will the Data Page stop working when the rule is transitioned to another environment (having a different system identifier) ?
Or will this have no impact on the Data Page, making the 'System Name' field redundant in this context?
UPDATE: Having set a dummy value in the System name for Data Pages that do not refer external entities, I have learnt that there is no validation against the prpc system identifier, which could have corrupted the data page configuration upon transition.
Essentially it means that System Name is merely an identifier to the source-system of Data Page.