Platform

Related to R12 Waterfall Charts Documentation 

Kyle Kindle says

Still trying to figure these out ... so, you configure the waterfall as "Development" until you're ready to check it in and promote, at which point you configure it as "Production"?

When in development (and waterfall is configured as "Development") I should be able to see the behavior that I'll get in production when I change the configuration to "Production" and promote there?

(I don't seem to have the ability to enter causals in Development when configure to Development. Do I need to check it in before testing? )

Hi Kyle,

Waterfalls are a bit confusing, as they are one of the few items that can be updated by an end user. (As opposed to reports which can only be edited by a TBMA in Dev).   

As a TBMA, you'll edit waterfall properties like the tables, size and columns in DEV.

The piece that is confusing here is the Environment property.  This applies to the 'Explanation" column of a waterfall (see below) .This can be set to either Dev, Stage or Prod,  allowing the Explanation column to be populated in the selected environment. 

Some examples of when you might want to use the different Environment settings:

 - If you want to allow you end users to edit the Explanation, set it to Prod. 

-  If you want your Super Users or QA  to edit Explanation, set the property to Stage. 

 - If you want the TBMA to be the only one who edits Explanation, set it to Dev.

Thanks

...Bob

So ... I set it to Dev. Save it. Check it in even. And still cannot add explanations in the development environment.

Somewhere it said that there was a way to make them editable vs. read-only. I see no controls that would relate to that.

In fact, I cannot even get it created so that the explanation table stays unhidden. It thinks it's visible since when you right mouse on it, it says hide table. You can then Unhide it. But not do anything with it. Presumably because it was not configured to be editable.

This functionality is at the top of my list of frustrations, largely because it would be the "killer feature" that would make adoption of Apptio a snap.

Support ticket entered.

Thank you Kyle Kindle I'm seeing if we can pull the "Assumed Answered" mark off this question so we can update it with your resolution. If the system won't let us back that out, I'll still flag this for follow up. 

I worked on the support case that Kyle submitted.

It looks like there is a bug that affects being able to enter explanation rows when your waterfall report is set to be editable in "Development". 

Currently we recommend setting the report to be editable in either Staging or Production (where this works as expected).
When this is set to be editable in development, the Add Explanation, Save and Cancel buttons are not visible outside of when you have the report checked out in your workspace in tbm studio mode. Also, right clicking on the table allows you to enter a row but doesn't allow you to enter any values into any of the cells in that new row.

When configured to be editable in Staging or Production, the explanation table works as expected. (The "Add Explanation" button is visible and clickable as well as the "Save" and "Cancel" buttons).

A bug has been submitted to get the functionality working in development. (BIIT-79578)