A few folks suggested to me that a bit more information on the built-in properties and property scoping for uDeploy would be handy. Message received, and we’ll flesh out the documentation on that front. In the meantime, here’s a quick list of the automaticly available properties.

${p:version.name}

${p:version.id}

${p:component.name}

${p:component.id}

${p:resource.name}

${p:resource.id}

${p:application.name}

${p:application.id}

${p:environment.name}

${p:environment.id}

${p:<property name>} – Process properties. Defined on the process’s “properties” tab, given values by whoever is running the process.

${p:component/<property name>} – Component custom properties, set on the component’s “properties” tab.

${p:environment/<property name>} – Environment properties. These come from two places. You can define properties on the component’s properties tab, under the Environment Properties table. You then give values for these on each environment using the component. In addition, you can set custom environment properties on the environment’s properties tab. These custom properties will override the properties coming from components, although it’s recommended to avoid having the same name in both places.

${p:resource/<property name>} – Resource properties. This can include the built-in agent properties as well as any custom properties. Each of these have their own tab on the resource.

${p:resource/<role name>/<property name>} – Resource role properties. These are defined on resource roles, and the values are set when you add a role to a resource.

${p:application/<property name} – Application custom properties. These are set on the application’s properties tab.

${p:system/<property name>} – Global system properties. These are set on the “System Properties” page in the Settings area.

All of the following are comma-separated series of name=value, including each property on the given object.

${p:component/allProperties}

${p:environment/allProperties}

${p:resource/allProperties}

${p:system/allProperties}