FAQs

Not all users need licenses, only any users who need to see highlights, as well as users who will administer the app. Basically, if a user is in a role that will never need to interact with highlights, you wouldn't have to provide them a license. However, licenses are free currently.

You will need licenses for any user (usually an admin) who sets up the highlights, and also a license for each user who needs to see the highlights (or other actions).

Yes, but because the field is being updated outside of the detail component, we need to create a special platform event to notify our component to refresh the highlights. See this video for an explanation for how to do that:

https://www.loom.com/share/abdeb798b51c49b0993ff128210a7c26

Yes, but because the field is being updated outside of the detail component, we need to create a special platform event to notify our component to refresh the highlights. See this video for an explanation for how to do that:

https://www.loom.com/share/abdeb798b51c49b0993ff128210a7c26

A blank field can be highlighted by simply creating a filter that indicates the field equals a blank value. Value Type And Value should be left BLANK. See this video for how this could be done:

https://www.loom.com/share/8502a85a370249a990d4b17b6be44279

Yes, you can hide these fields like any others. Click on Setup -> Installed Packages -> Search for Highlighter -> Click on Configure -> Click on New. In the New Action: Set the Object to Opportunity, the Action to "Hide Field", the component Name to Stage (StageName), and then check the Only Valid For : "All" (If you want to hide fields from all Users) or whatever makes sense. Finally, Click on Save and go test it.

Some fields can be highlighted, but cannot be used in the filters. So in order to highlight these fields, alternate filter fields would need to be set up, perhaps populated by a flow, which would then be used in the action filters.

We usually don't turn on the license management feature for installs. The reason for this is that we do not strictly monitor licensed usage except around renewal time, so if you team grows by a few members, or more users desire to start using it, we just let you start using it, and we adjust the licenses next year, at renewal time. We don't have a person dedicated to license management and management of these licenses is a waste of time for our clients as well, so all you have to do is assign each user the appropriate Permission Set.

The short answer is that we do not offer support. However, if you are interested in potentially upgrading to our paid product and are testing it out in the free version, then we can offer limited support to ensure you are able to successfully test. If you need help configuring, paid support is available by the hour.

The first reason this might be is if the user is not assigned one of our permission sets. The "Admin" permission set should be assigned for anyone administering the app, and the "User" permission set for everyone else.

They are not concurrent, but rather named licenses. We do allow you to change the user assigned to the license as an admin, but they are not concurrent licenses.

We cannot downgrade to a lower version. Our approach to sandboxes differs from Production—we frequently update clients' sandboxes with new versions so they can test their existing functionality in the new version. Since we release new versions almost weekly, it is likely that the upgrade was automatically pushed to your Sandbox.

Some clients opt out of automatic updates by being placed on a do-not-update exclusion list. If you'd like to be added to this list, please provide the Org IDs of the sandboxes you'd like excluded, and we will ensure they are not updated in the future.