Concept: Assembly Versions

Assembly version-management allows the Workday Enterprise Service Bus (ESB) server and Studio development teams to evolve assemblies within the Workday Runtime programming model over time without affecting existing users. For example, assembly version-management enables Workday to:

All assemblies have a

version

attribute. By default, when you create a new assembly project, Workday Studio sets the

version

attribute value for the

assembly

element in the

assembly.xml

file to the most current version of the Workday Runtime. The format is

year.drop-number

, where drop-number corresponds to the week number. Example:

2016.11

.

Studio displays this number next to the

Assembly

folder in the

Project Explorer

.

When changes are introduced to existing runtime features, Workday ensures that they are backwards compatible. This means that all existing assemblies operate as before, according to their version number. However, by default, new assemblies have the behavior that corresponds to the current version number. Typically, when Workday introduces a change, we define a new attribute on an assembly step or component. Older assemblies do not have this attribute, so we introduce a rule based on the version number to default the value for older assemblies. We also introduce a rule to default a different value for newer assemblies. As a developer, if you want to uptake new features in older assemblies, you have several options. You can: