-
Re: Anyone else having issues with the Scout badge?
christina.keimig Jan 13, 2016 10:03 AM (in response to Frank Field)1 person found this helpfulThe thing with the Scout mission is it is triggered by the FIRST EVER search. That messes things up for all pre-existing users, in my experience, which is why it's disabled in my instance.
-
Re: Anyone else having issues with the Scout badge?
Megan TruettJan 13, 2016 10:09 AM (in response to Frank Field)
1 person found this helpfulI reported that bug about three years ago and looks like the fix to that trigger was never addressed (haven't seen it work since or heard that it was fixed). Are you finding that new members aren't getting the mission or just ones who likely already completed their first ever search before the mission was activated?
FYI, you can't add a question to that long thread because we shut down comments on that doc awhile back to encourage separate threads like this for specific questions
-
Re: Anyone else having issues with the Scout badge?
Frank Field Jan 13, 2016 10:22 AM (in response to Megan Truett)Megan Truett, I meant to tag you, as I did see you posted that (I "liked" it earlier today), in hopes that you'd know the answer. Thanks for the follow up. Christina Keimig, I bet that is the situation in my community. We wiped the points out for the new year to "start over" on points/leaderboards, so perhaps that has something to do with it. Thing is, I do want people to earn that badge as search is an important function on our community (and will become more and more important as content grows)... Not sure if I should start a case or if there's some way I can do a mass reset so everyone can get that badge for doing search... :-/
-
Re: Anyone else having issues with the Scout badge?
Megan TruettJan 13, 2016 10:37 AM (in response to Frank Field)
1 person found this helpfulWiping the points doesn't reset the triggers. For some reason that first search is a different trigger in Jive than any subsequent searches. Ideally, Bunchball should track the next search (after the mission is activated), but looking at the available actions, just the first one ever-ever-ever is tracked by the system. I don't know if they did this because Bunchball just didn't think it through or if general 'search' is just not available from Jive. Curtis Gross -- any insight on that?
Frank, does that make sense? Overall, the BB system doesn't track activity retroactively. For example, you can't get points for writing a document if it happened before the gamification was enabled. So if someone did a search of any kind before gamification, that ship has sailed. There is no second first-time
-
Re: Anyone else having issues with the Scout badge?
CurtisG Jan 13, 2016 10:43 AM (in response to Megan Truett)1 person found this helpfulThe first search is stored as a property on a user. This means if this property exists for the user - the 'search' event will not be fired over to the backend bunchball system.
What does this mean?
- If a user has never searched before - they can earn the badge.
- Wiping points and badges will not reset this property.
A potential workaround is to make 'search for a piece of content and then like that content' the description of the mission and then just actually tie the reward to Search OR like X content. That way the search will be rewarded or - if the user has searched before - the like will trigger the badge.
-
Re: Anyone else having issues with the Scout badge?
Frank Field Jan 13, 2016 10:46 AM (in response to CurtisG)I'll consider that, thanks, Curtis Gross...
-
Re: Anyone else having issues with the Scout badge?
christina.keimig Jan 13, 2016 10:43 AM (in response to Megan Truett)That is precisely my experience as well, Megan... that very very first search is the only trigger and it's not retroactive. Annoying, to say the least.
-
Re: Anyone else having issues with the Scout badge?
Frank Field Jan 13, 2016 10:45 AM (in response to Megan Truett)Intuitively, yes, that makes sense. I have just developed in my short stint as a community manager, a healthy skepticism about things simply working intuitively. I notice when I click "advanced on the mission settings that "prerequisites" is set to "ALL." I wonder if it should be "ANY" instead? I didn't set this console up, I have just been tweaking it as I go along...
-
-
-