All Projects → JodieM → Indicators

JodieM / Indicators

Licence: MIT License
Indicators Lightning Web Component

Programming Languages

javascript
184084 projects - #8 most used programming language
HTML
75241 projects
CSS
56736 projects

Projects that are alternatives of or similar to Indicators

lwc-redux
Integrate Redux with Lightning Web Component
Stars: ✭ 35 (+16.67%)
Mutual labels:  salesforce, salesforce-lightning, lwc
Related-List-LWC
My first real foray into Lightning Web Components - an sobject / list view driven lightning data table
Stars: ✭ 21 (-30%)
Mutual labels:  salesforce, lwc, salesforce-lightning-web-components
PaymentForm
A form that takes credit card and address information. Uses a ported version of jessie pollack's card component.
Stars: ✭ 40 (+33.33%)
Mutual labels:  salesforce, salesforce-lightning, lwc
timeline-component-lwc
This component enables timeline view for Salesforce Record history.
Stars: ✭ 18 (-40%)
Mutual labels:  salesforce, lwc
apex-rollup
Fast, configurable, elastically scaling custom rollup solution. Apex Invocable action, one-liner Apex trigger/CMDT-driven logic, and scheduled Apex-ready.
Stars: ✭ 133 (+343.33%)
Mutual labels:  salesforce, lwc
sfdx-lwc-jest
Run Jest against LWC components in SFDX workspace environment
Stars: ✭ 136 (+353.33%)
Mutual labels:  salesforce, lwc
quiz-host-app
Multiplayer quiz app built on Salesforce technology (host app)
Stars: ✭ 69 (+130%)
Mutual labels:  salesforce, lwc
one-pub-sub-lwc
One PubSub: A Declarative PubSub Library for Lightning Web Component and Aura Component
Stars: ✭ 19 (-36.67%)
Mutual labels:  salesforce, lwc
spaghetti-cmd-loader
Salesforce Custom Metadata Type Loader, designed for Lightning Experience
Stars: ✭ 13 (-56.67%)
Mutual labels:  salesforce, salesforce-lightning
lwc-modules
Build any LWC you want without ever having to touch Apex
Stars: ✭ 20 (-33.33%)
Mutual labels:  salesforce, lwc
Lightning-Out-Demo
How to use Lightning component in node.js (External websites) by using Lightning Out. It shows how to enable CORS and SSL in Node.js with Video and complete source code.
Stars: ✭ 17 (-43.33%)
Mutual labels:  salesforce, salesforce-lightning
Salesforce-Short-Hands
The main purpose of this repository is to put all the utilities in one place so that other developers can get help and they can also contribute to this repo.
Stars: ✭ 31 (+3.33%)
Mutual labels:  salesforce, salesforce-lightning
eslint-plugin-aura
Salesforce Lightning (Aura) specific linting rules for ESLint
Stars: ✭ 24 (-20%)
Mutual labels:  salesforce, salesforce-lightning
build-apps-with-lwc
Ursus Park sample app for Trailhead project Build Flexible Apps with Lightning Web Components
Stars: ✭ 18 (-40%)
Mutual labels:  salesforce, lwc
Salesforce-Custom-Path-Assistant-LWC
A Salesforce custom path assistant built using only Lightning Web Components
Stars: ✭ 37 (+23.33%)
Mutual labels:  salesforce, salesforce-lightning
awesome-lwc
A list of interesting on platform Lightning Web Components resources and code examples
Stars: ✭ 124 (+313.33%)
Mutual labels:  salesforce, lwc
uswds-sf-lightning-community
A Salesforce Lightning Community Theme and related components built upon US Web Design System
Stars: ✭ 24 (-20%)
Mutual labels:  salesforce, salesforce-lightning
lwc-soql-builder
Awesome SOQL execution tool developed in Lightning Web Components Open Source
Stars: ✭ 85 (+183.33%)
Mutual labels:  salesforce, lwc
lwc-streaming-api
Lightning Web Component Streaming API
Stars: ✭ 25 (-16.67%)
Mutual labels:  salesforce, lwc
SF-Lightning-Lookup
Salesforce lightning dynamic lookup component.
Stars: ✭ 15 (-50%)
Mutual labels:  salesforce, salesforce-lightning

Indicators Lightning Web Component

Bring some colour and visibility to the data on your Lightning Pages. Allow users to see at a glance what this record is about and what it's status is. This component is highly customisable and can be used in many record pages.

The icons are based off the standard Lightning Web Component, Avatar.

See the Wiki Page from The Detail Department Wiki for more details about the history, and reason for this component.

Deploy this component to your Salesforce org.

Deploy to Salesforce

The Component will be installed as a custom component, which you can modify if needed. If there are any updates, it is up to you to deploy the changes. Ensure that your org has My Domain available to use the Component.

Steps

  • Add the indicatorList Component to the Lightning Record Page.

  • Enter the Settings for the Lightning Card:

    • Title - Not Required, but looks best if it is defined
    • Icon - Not Required, but looks best if it is defined - the icon name from SLDS Icons or default icons such as standard:account, standard:opportunity
    • Heading Text - Optional - the text to display above the icons
    • Icon Size - large or medium, defaults to large
    • Icon Shape - circle or base (square), defaults to base
  • Enter the Settings for each Indicator:

    • Indicator Field Names - the exact API Name of the field to display - case is important. Separated by a semicolon.
    • Indicator Icons - the icon name from SLDS Icons or default icons such as standard:account, standard:opportunity separated by a semicolon.
    • Indicator Text Values - the three character (max) text values to show for each icon. Separated by a semicolon. Eg enter ;; if there are 3 icons with no text.
    • Indicator Image URLs - the full URL of the Image to display, separated by a semicolon. Note: No quotation marks. Image URLs are not applicable for False values.
    • Indicator Hover Texts - the text to display on hover. Keep it short. Separate by semicolons. No semicolons in the text. Suggest enter Something like "Status - Green: Active - Red: Inactive" as no semicolons or wrapping is allowed. Alt text should be less than 50 chars long for good accessibility.
    • Icons for False - if you want the False value to display then enter an icon here. the icon name from SLDS Icons or default icons such as standard:account, standard:opportunity separated by a semicolon. Enter semicolons between all indicators if no False values are to be shown.
    • Text Values for False - works similar to Indicator Text Values, but if the value is False or blank. This works in conjunction with Icons for False and the Avatar will only show if Icons for False is entered for that Indicator.
  • After entering all settings, the Indicators should display on the Lightning Page preview and will then change in the preview as you adjust the settings.

  • Click Save

  • Test a boolean field to ensure the indicator disappears if False. Test a boolean field with False values to make sure the indicator appears if the boolean is False.

    Hint: Use the configuration worksheet (Make your own copy), I've created to help you work out the whole component before you set it up on the page.

Rules

  • The indicators work with Boolean or Text fields. Date Fields can be used if you enter Indicator Text Values as the value that is shown does not make much sense. Number fields can be used, if the number is not too big, or you use Indicator Text Values.
  • If the field is a Boolean and the value is False the Indicator will not show unless there is an Icons for False entered for that Indicator.
  • If there is a value in Indicator Image URLs that image will show. Images do not work for False values,
  • If the field is a Boolean and there is a value in Indicator Text Values then that text will show. Limit this text to 3 characters max, and Uppercase.
  • If the field is a Boolean and there is no value in Indicator Text Values the Icon will be shown.
  • If the field is a Text field and there is no value in Indicator Text Values the first 3 characters will show, in Uppercase.
  • If there is an Indicator Text Values, the Icon image will not be shown, but the colour will be from the SLDS icon name entered.
  • If you enter none for the icon it makes the spacing smaller between the avatars and sets the text colour as inversed. This is helpful when you want to use Emoji text for the avatars insted of icons. See Building a Checking Component for an example.
  • There is no field validation to ensure you don't use a combination of entries that look wierd, so if it looks strange, just go back to simple boolean or text fields.

Examples

Default view after adding component to the page

Suggested location and usage

Hover Text shown

See the Wiki Page from The Detail Department Wiki for more images and extensive examples for using this component.

Tips

  • Create a new Boolean Formula Field - eg Is Active (Is_Active__c) ISPICKVAL(Status__c,"Active")
  • Create a new Text field that returns a 3 character (max) value based on Picklist values eg CASE(TEXT(Status__c),"Oh Hold","HLD","Waiting","WT!","Cancelled","X","ACT")
  • Create a Formula for Is High Value Donor (Is_High_Value_Donor__c) and use $$$ as the text or the green money bag icon npo02__TotalOppAmount__c > $CustomMetadata.ReportingSettings__mdt.HighValueDonor.Amount__c
  • You can traverse to parent field relationships by entering for example Account.IsActive__c on a Component on the Contact page.
  • The Images can come from the Salesforce Logos page at https://login.salesforce.com/logos/. Copy the Logo URL value. If using images, the SLDS icon must still be entered, but you can enter a default icon like custom:empty
  • To get icons in non-SLDS colours, use an external service like DaButtonFactory or eg IconS8 rounded square (replace the colour in the URL) to generate an icon with the text and download it. Add it to your Asset Library, make the image public, and grab the URL. You can use the images from the external service directly, but it may not be a good idea long term. But beware, it might look a bit crap mixing with the SLDS colours. You may also need to display an attribution somewhere on the page, depending on where the images come from.

Future Component Ideas

See Issues Register

Your ideas and your help is needed. This is my very first component so it may be a bit rough around the edges, and I welcome pull requests for suggestions on how to fix or improve it. But be kind, please.

Acknowledgements

  • The coloured indicators idea came from the Weathervane App by Christian Carter and Beth Breisnes which was built for Classic and uses Custom Metadata Types. It has a few more features than this Component but it is something we can build upon later. It was a fabulous app but no longer supported as both have moved on to work at Salesforce.
  • The Setup section came from Clint Chester's excellent Component, Helpful Links Component
  • Further acknowledgements on my Wiki page.

Attribution

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].