Tips & Tricks

One of my customers deployed a custom hive on a user’s machine to test the connection from his machine to their Citrix environment to see why the users can’t get a session ready.What do you think?

We’re always updating our users on new features we launch via the community. It’s such a great way to communicate on a 1-to-many basis with our customers. Additionally, what’s even better is that we have started to launch beta testing groups on our community where we invite a certain number of customers to test new features before we release them.   Not only does this allow us to iron out any bugs before a full roll-out, it also creates a real feeling of collaboration and togetherness between us and our customers. Such a great way to make sure you are building a product that really meets the needs of your end users! 

Hey everyone!   I was taking out the trash this morning—that’s when I do my best thinking lol, and had a super quick idea on how to easily use our software for Lead Scoring. We have had requests before to add functionality for this to our product, but I think there’s already a quick and insightful way to get you there with your current implementation.   So, here’s what I’ve been thinking to solve this:   What if we use any actions users perform in your product and attribute a score to them. Example: every time a user logs in to your app, we give them 10 points. Whenever they activate a new feature in a trial, we give them 25.   There’s no standard way to create an overview based on ruling like this, but we can solve that using custom formulas:   [code]Count of ‘App opens’ * 10[code] Applying this formula and adding it to a custom report would give us a real-time count of accounts with the most opens and thus highest score. If we then add a timeframe to the report, we could run this mon

Have you or your users come across these error messages? validation.user_register.ratelimit or validation.user_login.ratelimit. This is due to our rate limiting feature being applied when specific users or actions exceed a defined limit. We've developed the following rate limits: Limit on failed registration: visitors from one IP cannot attempt more than 5 tries per hour when registering a user Limit on failed login: visitors from one IP cannot attempt more than 5 tries per hour when trying to login as a user You don't want this limit in your instance? No problem, just drop us a line at support@company.com and we can disable it for you. The phrase is not shown correctly? If the errors are shown as validation.user_register.ratelimit or validation.user_login.ratelimit, it can be confusing for users to figure our what is going on. You can easily change them by adding the following phrases in the control environment of your community:    Module: Common, Key: validation.user_login.ratelimit