We've seen an increased request of the possibility to execute applications with different parameters and behavior. The solution we came up with was to allow the Epsis TeamBox administrators to create these templates for different applications and make them available as building blocks in our application, Epsis Composer. This document will explain how to create templates and how to use them.


What is an info element template?

An info element template opens up the possibility to change the behavior of an application being launched. In other words; an info element template is basically a wrapping of command line arguments. To help understand the purpose of templates, we'll go through an example task; call someone on Skype when running an Info module. Below we'll go through this example, both how to create the template in the Admin tool, and how to use them to create info modules.


Create A Simple Template - Epsis TeamBox Admin


The Epsis TeamBox Admin tool is the place where you create the templates (before they can be used in Epsis Composer). 


Let's go through the properties available for a template:

  • Name (required) - name is used in Epsis Composer to filter and find the created template.
  • Description - used to help users and administrators understand what the template will do.
  • File path (required) - used to describe the file path to the application you want to create a template for.
  • Arguments - used to describe a change of behavior of the application. For instance a command line argument, for instance -K for kiosk mode on Internet Explorer or our double curly brace notation to inject a variable there.
  • Variables - used to provide a list of different changes in behavior. For instance "callto" command line argument for Skype.


Notice the double curly brace notation. What this does is that it describes where the data from a variable should be injected in the file path or arguments. Given the example in the screenshot, the complete string will become: "lync.exe callto:<sip: ><sip: >". 


Create A More Advanced Template With Window Handling - Epsis TeamBox Admin



Let's go through the properties available for a template:

  • Enable window handling - tells TeamBox if the window should be apart of the info module life cycle or not. 
  • Process name - name of the process you want to catch. This does not have to be the same as filepath.
  • Window title - name for the window you are catching.
  • Window title search type - Choose between substring, wildcard or regex to find the process or window title you are looking to catch.
  • Window class name - distinguish the window from other windows by using their classname.
  • Closing behavior - simulation for the window to act in a specific way when you traverse in the steps of using TeamBox. Choose between:
    • Close
    • Do not close
    • Minimize


As you probably can see, the string is incomplete with only the file path and the variable. The actual parameter for who you'd like to call is added through Epsis Composer when using this template, see the section below for explanation.


Use Template - Epsis Composer



The Epsis Composer is where you can benefit from the created templates. When you include a template in an info module you'll be prompted to enter values for the template variables. Name and description is available for all templates. This is to make it easier to find in the info element section as soon as the info module is saved. Note that this is NOT the same name and description as entered in the Admin tool. 


When the info display (which is based on the "Skype call" template) is included and saved on an info module. It's possible to re-use this exact info display as a regular info display, and it is located under "Info elements (re-use)" section. 


What this does is that when you run the info module in Epsis TeamBox, it will inject the information provided in "Call to" into the file path after the double curly braces notation. In the example provided in this document, that means that the Epsis TeamBox will execute a file path that looks like this at runtime: 

"lync.exe" callto <sip:john@example.com><sip:jane@example.com>