An entity badge is an icon that visually indicates information about a contact in the contact's profile banner. For example, the Has Opportunity badge indicates that the contact has an associated opportunity.
Create and manage entity badges in the Badgestab on the Entity Codes page.
The badge icons in the Admin Console appear differently in the Application Foundation Layers (AFL) UI.
The default entity badges are:
Badge icons as displayed in Admin console
AFL UI badge icons
Name
Description
Locked by Business Process
This entity has an active business process. Its profile cannot be updated.
Has Late Touch
Indicates tardiness with respect to making contact with a client
Has Related Business Process
This entity has an associated business process
Has Opportunity
Has associated parent opportunity or product opportunity
Open Service Requests
Indicates open service requests for an entity
Tier A
Entity to receive top-level service
Tier B
Entity to receive mid-level service
Tier C
Minimal service requirement
Has Campaign
This entity is a campaign participant
Birthday is today
This entity has a birthday today
Upcoming Birthday
This entity has a birthday within the next 7 days
Adding entity badges
Add entity badges to create a visual representation of details and properties for contacts. Entity badges display in the contact banner of a contact's profile in the Contacts workspace.
To specify conditions for entity badges, knowledge of the Scheme programming language and the EntityBadge class is required.
To add an entity badge:
Navigate to the Entity Codes page.
In the Badgestab, click the Addbutton. The Add Badge Configuration dialog opens.
In the Descriptionfield, enter a description of the badge. The description displays only in NexJ Admin Console.
In theTooltip Textfield, enter a descriptive name for the badge. The name displays in a tooltip when a user hovers their cursor over the badge in NexJ CRM.
In the Iconfield, specify an icon to display for the badge in NexJ CRM. To choose an icon:
In the Iconfield, click the Selectbutton. The Select Icon dialog opens.
Select an icon to use for the badge, then click OK. The Select Icon dialog closes.
In the Expressionfield, write an expression in Scheme code for the conditions that an entity must satisfy for the badge to display on the entity's profile. The expression is relative to the EntityBadge class. For example, use the expression (= (@ entity tier caption) "A") to display the badge on tier A contacts.
Select Activeto activate the badge in NexJ CRM.
In theReference Namefield, enter a reference name for the badge.
Click OK. The Add Badge Configuration dialog closes.
The new entity badge is created. If Activeis selected, the badge now displays on contact profiles.
Rearranging entity badges
Rearrange entity badges to change the order in which they display in the list in the Dashboard Badges zone.
To rearrange entity badges:
Navigate to the Entity Codes page.
In the Badgestab, select the badge to rearrange, then click the Upor Downbuttons to move the badge up or down in the list.
The badges are rearranged.
Editing entity badges
Edit entity badges to change badge properties such as the icon, tooltip text, and expression.
To specify conditions for entity badges, knowledge of the Scheme programming language and the EntityBadge class is required.
To edit an entity badge:
Navigate to the Entity Codes page.
In theBadgestab, select the badge to edit.
In the Detail zone, click the Editbutton . The Edit Badge Configuration dialog opens.
Make your changes to the badge.
A red asterisk indicates required fields.
Click OK. The Edit Badge Configuration dialog closes.
The entity badge is edited. If Activeis selected, the modified badge now displays on entity profiles.
Deleting entity badges
Delete entity badges when you no longer need them.
To delete an entity badge:
Navigate to the Entity Codes page.
In the Badgestab, click theActionbutton for the badge you want to delete, and click theDeletebutton.
The entity badge is deleted and no longer displays on applicable contact profiles.
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.