Hi Lawrence,
With the BOX, you normally have to initiate it from the NetConfig tool by clicking on a thread and then right-clicking and selecting ‘Create BOX’. Then depending on the context of your thread (inbound or outbound) it will pull in the routes (if inbound), Xlates, procs, etc associated with that thread. What I have done to create an ’empty’ box so that I can manually add items is simply picked an outbound thread, done the ‘Create BOX’ then deleted the items from the BOX. I can then manually add the items I want (using the drop down in the BOX tool) and then port my box to the desired site using the BOX manager and deploy.
Just be aware that the BOX doesn’t magically pull everything. i.e. if you are referencing a proc within your Xlate, the BOX doesn’t know to add that proc. Also, if you are using a Lookup Table within a proc, the tool won’t know about it. But, it does a nice job of pulling most of your items in “automagically”. But, you need to be cognizant if you select an inbound and outbound pair of threads, and the inbound has other routes to threads you don’t want, the tool will still pull the references to those because you are selecting the inbound thread.
For your example, you could create the empty BOX (as described above) in your source site, manually add the variant. Then in the destination site, open the BOX manager and deploy the box (if on the same server). If you are moving from one server to another (i.e. test to prod), then select the ‘Remote Host’ (by clicking on the << to get the Remote Host window) and hit the little icon to get the lists of host to pull from. You should then see the available BOXes and be able to drag that box from the remote pane to the local pane, then deploy.
Hope this helps.
Jim Cobane
Henry Ford Health
.
