Settings and activity
34 results found
-
3 votes
Martin Tsankov
supported this idea
·
-
4 votes
An error occurred while saving the comment -
48 votes
Martin Tsankov
supported this idea
·
-
13 votes
Martin Tsankov
supported this idea
·
-
20 votes
Martin Tsankov
supported this idea
·
-
10 votes
Martin Tsankov
supported this idea
·
-
2 votes
Martin Tsankov
supported this idea
·
-
27 votes
Martin Tsankov
supported this idea
·
-
14 votes
Martin Tsankov
supported this idea
·
-
88 votes
Martin Tsankov
supported this idea
·
-
12 votes
Martin Tsankov
supported this idea
·
-
1 vote
Martin Tsankov
shared this idea
·
-
7 votes
Martin Tsankov
supported this idea
·
-
14 votes
Martin Tsankov
supported this idea
·
-
6 votes
Martin Tsankov
supported this idea
·
-
56 votes
Hello, please provide additional details for this ask. Is a current setting your are using not working as desired? Thank you!
Martin Tsankov
supported this idea
·
-
6 votes
Martin Tsankov
supported this idea
·
-
4 votes
Martin Tsankov
supported this idea
·
-
6 votes
Martin Tsankov
supported this idea
·
-
14 votes
Martin Tsankov
supported this idea
·
(empty) is seen because ENGAGED and TRANSITION are just Base states.
WORKING is both a Base state and a "custom state"
In order to fix this the RCX team would have to either allow customers to edit the states ENGAGED and TRANSITION, which doesn't sound like a good idea.
or
They could map ENGAGED base state to ENGAGED "custom state" but keep it hidden from customers (makes sense). This way you wouldn't see (empty) when reporting on the "custom state"