There are distinct
differences between the two
Changed
Assets selections for asset-based rules:
- All new or changed assets under a particular
path
- All new or changed assets under a particular
path since this rule was last executed
You typically use the latter only when you have already defined
a rule using the former. The
All new
or changed assets under a particular path since this rule was last
executed rule uses a different change detection "channel" than
the other change detection rule.
All rules that use
All new or changed
assets under a particular path are affected by any change to an
asset in the specified path. For any specified path, the first of
these rules to be run considers every asset to be new. A rule using
All new or changed assets under a particular
path since this rule was last executed is affected only by its
own previous runs. With this rule, a changed asset picked up by one
rule is not considered a changed asset by another rule, and each rule
considers every asset to be new when it is first run.
Because, in a typical globalization deployment, you want to translate
assets only when they have changed (or are new), the All new or changed assets under a particular
path selector is the common selection. When the rule has run and
a project has been created, you typically don't want other projects
created for this modified asset. So you use this rule to set a global
indicator that the asset has been dealt with.
However, if you had
another rule that does something else, like initiate a project with
a different workflow, you might want this rule to detect changes under
the asset path independently of the first rule. For this second rule
to not be blocked by the global indicator set when the first rule
ran, you use All new or changed assets
under a particular path since this rule was last executed.