Connect progress bar to stage/status picklist field

Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
edited June 25, 2020 in Ideas
The Progress Bar Indicator is awesome (https://github.com/skuidify/SamplePages/tree/master/progressIndicator)

What would make it awesomer and a better replacement for the new lightning Opportunity/Lead progress indicator is to be able to connect it to a Picklist Field and have each "step" correspond to a specific value from the picklist field. That way you could do it by Stage of an Opp or Status on a Lead or Status on any custom object.
5
5 votes

Implemented ยท Last Updated

Comments

  • Rob HatchRob Hatch ๐Ÿ› ๏ธ ๏ปฟ
    edited September 1, 2016
    That is a very interesting idea Jack. ย  I'll pass it along to Andrew - who basically whipped up the indicator as a side project.ย 
  • Pat VachonPat Vachon ๐Ÿ’Ž๐Ÿ’Ž๐Ÿ’Ž
    edited June 25, 2020
    Yup. I think I'd eventually conclude the same. As Jack says, the opportunity would greatly benefit from this indicator.
  • Conlan O'RourkeConlan O'Rourke โœญโœญโœญโœญ
    edited September 21, 2018
    I second this idea...it would also be great in the app I am building that helps demonstrate the performance progress of individuals....as the individual moves along through the program, their status would be nicely displayed.ย 
  • Anna WiersemaAnna Wiersema ๐Ÿ› ๏ธ ๏ปฟ
    edited December 13, 2019
    Guys! This is implemented! ย Thank Andrew for making it happen! ย You can checkout the update builder.js and runtime.jsย files or, if you have implemented the progress indicator component pack, just download the progressindicatorpack.zip file and upload it as the static resource for that component pack in your org. ย 
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited December 13, 2019
    Awesome! I'm getting an error though, even after completely removing the component pack and static resource and re-installing:
    An error occurred while attempting to load the "skuidopen" Component Pack. There may be an issue with the name or location of your Component Pack manifest files. Error: Please check Skuid Settings to ensure that this Component Pack has been correctly requested.
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited May 25, 2016
    The old version from Oct. 27 works if I re-install it.ย 
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited May 25, 2016
    It is really awesome though. If you have the picklist field added to your model, and you choose that field, it auto-adds steps for each of the values of that field.ย 

    But I'm still getting that error in the runtime.ย 

    image
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited May 25, 2016
    One thing I just noticed though, is that you can't delete any of the auto-added steps. Since we only use certain stage values with certain opportunities, this makes things awkward. It's also pulling in more values for this picklist than it should, this is the entire list, not just the list available to the particular record type, though I guess that's filtered at runtime not buildtime.
  • Anna WiersemaAnna Wiersema ๐Ÿ› ๏ธ ๏ปฟ
    edited December 11, 2015
    okay... so there was an issue because Andrew's static resource was named SkuidOpen, but the one I have been using for this component is just ProgressIndicator. ย So you have to make sure that it's referenced correctly in the builders.js file... i think it's fixed on github now in the builder.js file and in the zip file. ย 

    in line 5 of the progressIndicatorBuilder.js file, make sure "progressindicator" (the bold text below) is replaced with whatever you're calling the static resource in your org, which also needs to match the resource name for your component pack in the Skuid Connect tab.
    id: "progressindicator__progress_indicator",
  • Anna WiersemaAnna Wiersema ๐Ÿ› ๏ธ ๏ปฟ
    edited December 11, 2015
    Does that help clear up things? ย yeah, in the future it would be great to be able to choose which values you want to map, and which ones you want to ignore.
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited May 25, 2016
    Looks like it's also "skuidopen" in line 307 of builders.js
    Fixing that and retrying.ย 
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited May 25, 2016
    Works!
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited May 25, 2016
    Also looks a bit better when I changed the CSS file line 35 font-size to 15px and line 38 line-height to 30px

    image
  • Anna WiersemaAnna Wiersema ๐Ÿ› ๏ธ ๏ปฟ
    edited December 11, 2015
    Thanks, Jack! ย Line 307 should be fixed on gitHub now (for posterity).
  • Jack SanfordJack Sanford San Antonio, TX ๐Ÿ’Ž๐Ÿ’Ž
    edited January 12, 2018
    Bug report - if you connect this component to a model that isn't set to load data on page load it breaks the page. ย  ย  ย 

    <-- I know this component is totally extra and a side project, and I'm really excited to play with it more, don't take my comments as demands! Thanks Andrew and Anna!!-->
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!