Adding a Standalone Published Parameter

You can create published parameters that are not initially (or at all) related to a particular transformer setting. This allows you to create workspaces customized to your particular translation needs. Unlike published parameters that are applied to just one part of a workspace and require individual editing, standalone published parameters can be applied to any (or all) parts of a workspace, all at once.

Creating a Standalone Published Parameter

Right-click on the Published Parameters node in the Navigator pane and choose Add Published Parameter.  

Type

Configuration

The parameters required in this field are dependent on the Parameter Type you choose. For example, you can populate a list and the contents will be displayed in a pull-down menu when the parameter is published, or point to a file or directory.

Name

Enter a name. This will appear under the Published Parameters node in the Navigator pane.

Prompt

Enter the prompt that will appear when you run the workspace.

Default Value

Choose the default value that will be used.

Using a Standalone Parameter

Once created, you can use the parameter by

Examples

Here is an example of a workspace including a standalone published parameter. The initial Add Published Parameter dialog is created to generate a database password prompt on a workspace.

It is used by both Joiners, shown below and could be used by a reader or writer too.

 

In this example, the published parameter is an createed to switch options. The workspace filters the data according to the option chosen.

When you prompt and run the translation, you will be asked which option you want to use:

Existing Published Parameters

Existing Published Parameters will work as they always did, but now have unrestricted sharing abilities.

In other words, there was a previous restriction that published parameters could only be shared with parameters (for example, transformer settings) of the exact same type. This limitation has been removed.

This allows greater scope by allowing, for example, an integer type parameter to be shared with a float type setting.