I’m NOT the Service Connect person here but I have a question. Our test and prod systems are in Azure but when they were created, one uses a D: drive and one uses an E:. Is there a way to write our scripts so the drive is set in a variable instead of being hardcoded? Again, I don’t write the scripts but it would make testing easier if we just had to change one location ( or pull it from an environment variable ) when moving from test to prod.
I’m not sure I’m afraid. Someone else does the scripting but is concerned that the Test system and Prod are different. I personally am not a fan of hardcoded references anywhere. If I knew more about SC, I could probably answer that but let’s assume it is the input channel. Is there a way to put that in a setting or divine the drive letter by where SC is installed?
I don’t think there’s a standard letter for the temp storage drive but generally there is one that is and you can add others that do persist. At least that’s my understanding according to the previous infrastructure guy.
The reason I ask is because input / output channels are specific to each install and so you should be able to move the workflow around without having to change or touch the channels