Highlighter for Salesforce

Not all users need licenses. Only users who need to see highlights, and users who will administer the app, need one. If a user is in a role that will never need to interact with highlights, you don't have to give them a license. Licenses are currently free.

You need a license 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).

When you edit the Stage field itself, the highlight works. When you use the Path to change the Stage and press "Mark Stage as Complete", the field does not get highlighted until the page refreshes.

This can work without a refresh. Because the field is updated outside of the detail component, we need to create a special platform event to notify our component to refresh the highlights.

When you edit the Status field itself, the highlight works. When you use the Path to change the Status and press "Mark Status as Complete", the field does not get highlighted until the page refreshes.

This can work without a refresh. Because the field is updated outside of the detail component, we need to create a special platform event to notify our component to refresh the highlights.

This covers a field that is null, blank or empty. Create a filter that says the field equals a blank value. Leave Value Type and Value blank.

Yes. You can hide these fields like any others.

1. Click Setup, then Installed Packages.
2. Search for Highlighter, then click Configure.
3. Click New.
4. In the New Action, set the Object to Opportunity, the Action to "Hide Field" and the Component Name to Stage (StageName).
5. Under Only Valid For, check "All" to hide the field from all users, or pick the users it should apply to.
6. Click Save, then test it.

Some fields can be highlighted but cannot be used in the filters. To highlight these fields, set up other fields to filter on, for example fields filled by a Flow. Then use those fields in the action filters.

We usually don't turn on the license management feature for installs. We do not strictly monitor licensed usage except around renewal time. If your team grows by a few members, or more users want to start using the app, we 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 managing these licenses is a waste of time for our clients as well. 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 upgrading to our paid product and are testing it in the free version, we can offer limited support to make sure your test succeeds. If you need help configuring, paid support is available by the hour.

The first reason to check is whether the user is assigned one of our permission sets. Assign the "Admin" permission set to anyone who administers the app, and the "User" permission set to everyone else.

They are named licenses, not concurrent licenses. As an admin, you can change the user assigned to a license.

We cannot downgrade to a lower version. We treat sandboxes differently from production. We frequently update clients' sandboxes with new versions, so they can test their existing functionality in the new version. We release new versions almost weekly, so the upgrade was most likely pushed to your sandbox automatically.

Some clients opt out of automatic updates through a do-not-update exclusion list. To join the list, send us the org IDs of the sandboxes you want excluded, and we will make sure they are not updated in the future.