A place for Apptio product users to learn, connect, share and grow together.
This is the recording from the What's New in R12.7/R12.7.1 webinar. Thank you to our presenters @Eric Brandstetter� & @Kaitlin Smith-Brendehl and our facilitator @Debbie Hagen!
R12.7 Release Notes
R2.7.1 Release Notes
Report Collections and Role Based Permissions
Control access to reports through role-based permissions
Map Columns
Assign cost pools with machine learning
Machine Learning in R12.7
Monitor engagement with Apptio Usage reports
Apptio Usage Q & A
Q: Can ITP Admins see ITP usage data?
At this time, there is no ability for IT Planning administrators to see ITP usage data.
Editable tables: Accommodating user input
Editable Tables Q & A
Q: How does data go from “Prod” back to “Dev”?
Editable tables are not part of the TBM Studio version control. As such, the table can be directly accessed and updated from Dev or Prod. Changes made in either Dev or Prod can be directly seen in the other environment.
Q: Can you delete multiple rows at one time?
Multiple rows can be deleted at one time by right clicking all and selecting Delete then Save. There is not a multi-select button (e.g. show blank check boxes) to select and delete.
Thanks Deb, I'll have a look on community for more inform on these
Hi Julie,
We have multiple customers who use the "updating a table transform from the editable table" step as an approval. There are also ways to have an approval column on each individual edit (and leverage Apptioscript or role-based reporting controls to control who can edit it.
Apologies Deb, my question was in regards to approving data entered onto the editable tables from the reporting surface i.e. once the table has been made available in Production.
If someone enters data in to an editable table on the reporting surface (in PROD) can it be approved by an administrator after the data is entered?
If a user has the ability to edit it (which can be controlled on the Reporting Surface,) then then can edit it. There is there is the "Show changes" feature for audit. Changes to the editable table reaching the rest of the configuration go through checkin/checkout, so it can be controlled the same as any other change.
A bit more from Stephen Atwell:
Editable tables are not part of version control. They are intended to be edited in production, and they only have one version of their data. They have no concept of checkin/checkout.
You CAN have have a normal (not editable) table that periodically updates its data from an editable table. These updates DO go through checkin/checkout, because they are an update to a table transform, NOT an update to an editable table.
Basically, editable tables are not part of the normal change control process at all. Their data can be copied into to, at which point it works effectively the same as downloading the data from the editable table, and uploading it in studio.
Let us know if that doesn't answer your question.
Julie, can you elaborate a little? Are you talking about only allowing certain users to make changes, or are you talking about having records of who made what changes or something else?
Another question for Editable Tables that I'm not sure definitive answer - change management controls on the data entered by users, is this possible?