Scorecard measure description formatting

Forum|Forum|7 years ago
July 19, 2019
10 replies
180 views

Good Afternoon-

We have long descriptions for our manual scorecard measures including definitions, why it matters, scoring guidelines, etc.

The problem is that I cannot figure out how to format the description so it is readable. Formatting would include line breaks, bolding, etc.

I found that I could use a very simplistic form of Java when writing to the Comments section in the R360, however when I try formatting the Scorecard Measure descriptions this does not work.

Is there any way to format Scorecard Measure descriptions to make them more readable?

rho_ran_experian

Contributor ⭐️⭐️⭐️⭐️⭐️

I just recently put in a ticket about this issue. I would like to add more information about the measure in the description, but when I do it renders in paragraph form. It is not easy to read. This would save me a lot of time that I spend answering questions about how the score is calculated. I currently put some of that information in the Timeline activity that is created via the rule, because I can use code to put in line breaks. This is not idea because there is other data I need to put there referencing that particular score and the comments get very long. Not to mention I have to do it for every action in my rule. Being able to put this data on the Measure level once would be ideal!

TMaier

Helper ⭐️

I found this old post after trying to add color band criteria for measures in the description so that the CS team would have instant on-demand visibility in to the reason behind certain scores.

At the very least, allowing / honoring carriage returns in the description section would be a big win.

anirbandutta

Expert ⭐️

@shantan_reddy could you pl update the latest here?

It's an opportunity for engagement

shantan_reddy

Gainsight Employee ⭐️

Hi everyone,

We are doing a revamp of our entire Rules Engine. As part of that we will have rich text formatting available for scorecard comments. It will be available in January.

Regards,

Shantan

angela_domenichelli

Contributor ⭐️⭐️⭐️⭐️⭐️

Hi everyone,

We are doing a revamp of our entire Rules Engine. As part of that we will have rich text formatting available for scorecard comments. It will be available in January.

Regards,

Shantan

Reading this description - and our use case at athenahealth - the Rules engine would not address. Happy to start a new thread if needed, but it is the Scorecard Description i8tself that is causing major pains. We just need a Rich Text editor. You cannot embed links. You cannot even make a line or paragraph break. There are no options to bullet. All text in the description is 1 long jumble. This is vitally important for manual measures when the CSM need to know how to update the measure, so there is no rule populating a Comment.

Angela Domenichelli (She/Her/Hers)

bradley

Expert ⭐️

Hi everyone,

We are doing a revamp of our entire Rules Engine. As part of that we will have rich text formatting available for scorecard comments. It will be available in January.

Regards,

Shantan

Reading this description - and our use case at athenahealth - the Rules engine would not address. Happy to start a new thread if needed, but it is the Scorecard Description i8tself that is causing major pains. We just need a Rich Text editor. You cannot embed links. You cannot even make a line or paragraph break. There are no options to bullet. All text in the description is 1 long jumble. This is vitally important for manual measures when the CSM need to know how to update the measure, so there is no rule populating a Comment.

I agree with this - this is not a problem that rules engine can solve. Adding comments is great, but we’re looking to add rich text to measure descriptions. I would also add that this:

should also accept more than 80 characters and at the very least let you include special characters. Right now, you can’t even include “&”, meaning you have to spell out ‘and’ every time.

@shantan_reddy is this being looked at at all? @revathimenon can we get some 👀 on this?

We are revamping our scorecard right now, and I’ll tell you that a common problem with every scorecard is no matter how simple it is, if your users don’t have the context they need where they need it, it’s falling on def ears.