We had a partner install a Custom Tool for MCP. Why is it visible in the SuiteApp Audit Trail but not in the SuiteScripts list under the Custom Tools type of suitescript? Did they only upload the files but not the actual script object xml? What's going on?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** The visibility of a Custom Tool in the SuiteApp Audit Trail but not in the SuiteScripts list under the Custom Tools type of SuiteScript could be due to a few reasons. Firstly, it's important to understand that the SuiteApp Audit Trail and the SuiteScripts list are two different entities. The SuiteApp Audit Trail is a log of all SuiteApp installations, updates, and uninstallations. It shows the history of SuiteApp actions, including the installation of your Custom Tool. On the other hand, the SuiteScripts list under the Custom Tools type of SuiteScript is a list of all SuiteScripts that have been created and deployed in your account. If the Custom Tool is visible in the SuiteApp Audit Trail, it means that the tool has been installed successfully. However, if it's not visible in the SuiteScripts list, it could be due to the following reasons: 1. The Custom Tool has not been properly deployed: After uploading the script file, you need to create a script record and deploy it. If this step is not done, the Custom Tool will not appear in the SuiteScripts list. 2. Permissions: The visibility of scripts in the SuiteScripts list can be affected by the permissions of the role that is currently logged in. If the role does not have the necessary permissions to view the script, it will not appear in the list. 3. The script is a Plug-in Implementation: If the script is a Plug-in Implementation, it will not appear in the SuiteScripts list. Instead, it will appear in the list of Plug-in Implementations. In your case, it's possible that the partner only uploaded the files but did not create and deploy the script record. It's also possible that the script is a Plug-in Implementation, or that the current role does not have the necessary permissions to view the script.