|
|
 %object% %object1% %objects% confusion
| Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
| Bug |
Completed |
Low |
Thu 27th Nov 2014 |
1 vote
 |
| |
| Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
| 5.0.32.1 |
Fri 28th Nov 2014 |
5.0.33 |
Fri 28th Nov 2014 |
Log In |
| |
| saabie | | Thu 27th Nov 2014 08:21 |
The three references %object% %object1% and %objects% are in fact the same reference, so if you use one of them and then print out the contents of all three, you will find that they all have the same value.
But the GUI treats them as different references, and will list them in restrictions and actions seperately as:
[Referenced Object]
[Referenced Object 1]
[Referenced Objects]
This could be confusing to new users.
It would be better if they were in fact three different references.
Or if they are the same reference then drop-down lists in restrictions and actions should use the same name for all three:
[Referenced Object(s)]
|
| |
| Campbell | | Thu 27th Nov 2014 23:33 |
| %object% and %object1% are synonymous, the latter being useful when you have more than one object reference. However, %objects% is a distinct (and special) reference that matches on multiple reference, whereas the other references will only match a single item. |
| |
| saabie | | Fri 28th Nov 2014 00:51 |
When I tested this, if I use both the %objects% and %object1% reference then %object1%.Name prints the same list of objects as %objects%.List
|
| |
| Campbell | | Fri 28th Nov 2014 11:38 |
| Ok, this should be fixed. |
|
