Differences between Tachyon and on-premises Tachyon
As 1E continues to move Tachyon to the Cloud there are some features that are not currently available when compared with the on-premises version. To help reduce confusion, the table below list areas where the differences are.
Application | Page | Reason/Note |
|---|---|---|
Settings | Configuration Connectors | Only Tachyon and ServiceNow connectors are supported currently. |
Settings | Configuration Provider configuration | You will see an entry for Uninstall, this is a Reclaim feature that is not currently supported on Tachyon. |
Settings | Configuration Consumers | You will see consumers listed that are not currently available, these can be ignored. |
Settings | Configuration Components | You will see an entry for Reclaimer, this is a feature that is not currently supported on Tachyon. |
Settings | Monitoring Process Log | You will see log messages in this log that were created during provisioning of the instance, this is normal and may be ignored. |
Settings | Monitoring Infrastructure log | You may see a log message: ‘StateMachine Initiailse failed. Check from wrong XML’ in the workflow definition. This issue is benign and can be ignored. |
Settings | Permissions Users | The Tachyon deployment will automatically create a user that will be used to execute the Tachyon Inventory sync. You will see the CLOUD\tachyonsync is active in your instance, this user is required for the Tachyon Connector and must not be removed. |
Inventory | Manage Associations CM to Product Product to CM | The Inventory connector for MECM is not currently available, MECM uses on-premises servers that Tachyon cannot communicate with. |