Data not refreshed
| Infor OS component | Data not refreshed |
|---|---|
|
ION |
Third-party touch points Messages in transit that exist in the IMS intermediate tables or in SQS queues. If ION is still processing messages while the refresh occurs, these messages are missing from the refreshed tenant. OneView data Enterprise Locations: An Enterprise Connector is tenant specific, so Enterprise Locations are not refreshed. Connection parameters for Enterprise Connector connection points and File (sFTP from Cloud) connection points: To prevent the tenant refresh from connecting to an application that integrates with the source tenant, connection point parameters are not refreshed. Infor Ming.le service accounts used in ION API connection points and workflow ION APIs: During a refresh, the service accounts used for Infor Ming.le and for ION are not refreshed. When a tenant is refreshed, the models that were active in the source tenant will also be active in the refresh tenant. Due to the missing connection parameters and credentials, some of these models can now generate errors. |
|
Infor Ming.le ION API IFS |
IO BOX messages ION API trace logs Audit data
Ping federate connections ION API client IDs REDIS cache ION API metadata Tenant Specific Application Registrations PingFederate
OAuthGrantmanagementService |
| IDM |
You must complete tasks to restore service providers and identity providers after the tenant refresh is completed.
|