Hey Robert,
You can use the TestStand API to programmatically read in the templates file, which is just a sequence file, then populate your current sequence file with those sequences. My templates file had two subsequences, Seq0 and Seq1, so my code looks like the following:
//Locals.File, Locals.Seq0 and Locals.Seq1 are object references used to store the temp file object reference, and the two sequence references.
//Locals.userCancelled is a boolean
//The option of 1, the last parameter, is a workaround in this case and should not be used outside of this scenario. It bypasses the check we have for having multiple instances of the same file open.
Locals.File = RunState.Engine.ReadPropertyObjectFile("C:\\ProgramData\\National Instruments\\TestStand 2017 (64-bit)\\Cfg\\Templates.ini", Locals.userCancelled,ConflictHandler_Prompt,1),
#NoValidation(Locals.Seq0 = Locals.File.Data.Root["Sequences"]["Seq0"].AsPropertyObject.Clone("",0)),
#NoValidation(Locals.Seq1 = Locals.File.Data.Root["Sequences"]["Seq1"].AsPropertyObject.Clone("",0))
RunState.SequenceFile.InsertSequenceEx(1,Locals.Seq0),RunState.SequenceFile.InsertSequenceEx(2,Locals.Seq1)
Then use the InsertSequenceEx() method to add the two object references to the current sequence context. Few caveats to this - the sequence file names are hard-coded, and that may be less than ideal. You would also have to ensure that code modules and types are all available (but this is true for templates, regardless). Ultimately, you can add a tools menu item that would run this and automatically add it to the sequence file you want your user to work with - this would be the easiest workflow for your consumers.
Let me know if you have questions on this.
