Reference: Version Changes at the XML Level
This table below summarizes XML-level changes that have occurred for each version
update.
Version | Previous XML element/attribute | Replaced by | Meaning/Reason for change |
|---|---|---|---|
11.0 (These changes all concern changes to integration-system
definitions in the workday-in transport component.) | simple-type-reference
| simple-type
| The item's type is being declared, not referred to. |
type-reference
| class-report-field
| The new element name better represents the meaning. | |
service
| service-reference
| The item is not being defined, it is being referred to. Removed the
defined-by attribute, which is no longer used.
| |
integration-system/@template
| Removed | No longer applies. | |
param/@required
| param/@option
| Changed the boolean required attribute to an
option attribute with a value of
required , where true. | |
cloud/name
| cloud/@name
| Less verbose. | |
integration/name
| in-connector/@id
| Less verbose. | |
in-connector/id
| private-key
| private-key
| |
12.0 | key-file
| private-key
| Affects sftp-out and ftps-out
transports. Renamed the attribute to better reflect the meaning. |
public-key-properties
| private-key-properties
| Renamed to better reflect the meaning. | |
aggregator/@spawn-aggregated-processing
| Removed | This feature allowed an aggregator to create a new task or thread to
handle an aggregated message. This functionality was not used in Workday
integrations and was not suitable for public Workday Studio, so it was
removed. | |
store/@compress
store/@encrypt | Removed | Previously allowed fine-grained control over the store step. However,
Workday policy on integrations is to always compress and encrypt, so they
were removed. | |
ftp-out/@tmp-directory
sftp-out/@tmp-directory ftps-out/@tmp-directory | Removed | Previously these transports managed their own temp files, but were
refactored to use common FileBackedManagedData (FBDM) capability, so these
options were removed. | |
14.0 | delivery-service/child::*
| Removed | Sub-elements of the delivery service defined the allowed transports.
Such constraints should not be defined at design time. This is a runtime
configuration task, so they were removed from the design time development
stage. |