Skip to content
This repository has been archived by the owner on Apr 19, 2023. It is now read-only.

4. Templates

Jump to bottom
Graham Pugh edited this page Sep 28, 2019 · 1 revision

You will need some template files to make this work. Defaults are provided in the Templates folder.

Recipe Template

You will need a recipe template file for the JSSRecipeCreator to base its recipes from. If you have a working JSS recipe and workflow, you can start from that.

The Recipe Template allows you to specify values that are common to all of your recipes. JSSRecipeCreator will search the Templates directory for a file named RecipeTemplate.xml (this default can be changed in the preferences). If it is present, it will be used. If there is no RecipeTemplate.xml, JSSRecipeCreator will create a blank recipe XML structure to fill for you.

You can also run JSSRecipeCreator with the -s flag to force creating a recipe on the fly, or the -r option to specify a different recipe template than the default.

Except for scoping groups (the groups argument) and recipe values (like Identifier or MinimumVersion), JSSRecipeCreator adds all values to the INPUT section of a recipe, and your JSSImporter arguments should reference those INPUT variable names appropriately (see the provided RecipeTemplate.xml for an example. The specific INPUT variables managed (and thus they should be included in your template) are:

  • Comment (Extra comments you want to add, like author name. Can be set with the preference Recipe_Comment)
  • Description
  • Identifier
  • CATEGORY (Package Category)
  • SELF_SERVICE_DESCRIPTION (Self Service Description)
  • ICON (Self Service Icon)
  • NAME (Product name)
  • POLICY_CATEGORY
  • POLICY_TEMPLATE
  • MinimumVersion
  • ParentRecipe

Plus, you should have an element started for the JSSImporter processor.

Shea always used Testing for his self service policies, so this value is added to the POLICY_CATEGORY in the provided templates. JSSRecipeCreator will see that value and use it as a default. All of the above values work in the same way.

Policy Template

This is the PolicyTemplate.xml file you use with your JSSImporter recipes. The file doesn't actually need to be present, but if you copy it to the Templates directory , it will magically appear in the menu as an option, rather than having to key it in.

Defaults to Templates/PolicyTemplate.xml (but you can change it in the preferences).

Smart Group Templates

For each unique smart group you intend on using, you will need a SmartGroupTemplate (see the JSSImporter documentation for the structure of these). Again, it doesn't have to be present, but having it in the Templates directory will allow default-discovery and speed up your process.

The preferences by default specifies Templates/SmartGroupTemplate.xml as the default choice, which can of course be changed to suit your needs.

Clone this wiki locally