| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Summary
Many actions support the findReplace and findReplaceRegex parameters. These provide powerful re-use capabilities for automation by enabling templates (with the generic meaning of the word) to be used. The replacements occur at time of use. Use can be a very simple replacement like –findReplace XXX:YYY to very complex list of replacements using regex logic. Some scenarios require the more complex. Note that is string manipulation of some content.
Scenarios
...
| autoNumber | true |
|---|
...
| No Format |
|---|
--findReplace XXX:YYY |
...
| No Format |
|---|
--findReplace AAA:BBB,XXX:YYY |
...
| No Format |
|---|
--findReplaceRegex XXX-(\d+):YYY-$1 |
...
| No Format |
|---|
--findReplace "AAA BBB:YYY ZZZ" |
...
| No Format |
|---|
--findReplace 'AAA:BBB':YYY |
| No Format |
|---|
--findReplace "'AAA,BBB:YYY,ZZZ'" |
...
Just like other separated list parameters, if a separator is part of the text, then the element must be single quoted. See Tips.
Similarly embedded double quotes must be handled. See Tips.
If the element values contain lots of separators and/or quotes, it gets really complicated and difficult to read. The special parameter provides relief by allowing you to use different separator and quoting characters to be recognized instead so your element text can be used directly with modification. Confluence storage format is one of the worse case examples of this 
so use of the special parameter is highly recommended for these scenarios. See the special parameter section of Tips for examples.
Example Usage
...
| autoNumber | true |
|---|
...
| Include Page | ||||
|---|---|---|---|---|
|