Instructions and product packs
Instructions are developed and signed in TIMS. The name of the instruction and how it is signed governs whether it can be uploaded and run in Tachyon. Once signed, the instruction XML file can be uploaded directly into Tachyon using the Tachyon Portal Settings application.
Classic product packs are zips containing one or more Tachyon instructions. These are uploaded into Tachyon using the Tachyon Portal Settings application.
Integrated product packs are zips containing Guaranteed State policies and may also contain Tachyon instructions. These are uploaded in Tachyon using the Product Pack Deployment Tool. The tool can also be used to upload classic product packs but the documentation has not been updated to explain this.
Important
When any policy artifacts are modified, the Policy infrastructure is flagged as "dirty," triggering a prompt to Deploy Policy. This occurs even if the modified artifacts are not in use by any active Policy. If you're confident that none of the modified artifacts are in use, deploying is unnecessary. If unsure, you can safely proceed with the deployment, as it won't affect anything if there are no changes.
Code signing certificates
Instructions do not need to be signed if you only want to develop and test instructions locally in TIMS, or share them with other developers.
Instructions must be signed with an appropriate code signing certificate if you want to import instructions into a Tachyon system and run them. An appropriate code signing certificate is one that has been registered in your Tachyon license to be used with instructions that have a specific prefix. For more details about code signing certificates, prefixes and licensing, please refer to Running instructions in Tachyon for the first time.
Known issue:The current version of TIMS does not support CNG code signing certificates. You can select a CNG certificate but when you attempt to save an instruction then you will see an error: Tachyon Instruction Management Studio: Warning. The file <xml file> could not be digitally signed. Invalid provider type specified.