From the last demonstration that I have seen of 2.0.6 PAW is only able to prompt for parameters to a TI process at the time that you click on the Action Button. This is not how most systems are designed. Users will typically make selections in the Set Editor so that a grid returns data, eg for the Cost Centre that they selected. They will then either enter data into the grid, or just review the figures in the grid and then click the Action Button, which will either change a workflow cube to the next stage, or load the figures into another cube. They don't want to be prompted to select the Cost Centre again. Therefore the Action Button needs to have the ability to get parameters from selections on the sheet, especially from Set Editors, but also potentially from the Selected DBRW, or the equivalent cell in a non-DBRW based view such as an Explorer View.
|Who would benefit from this IDEA?||All customers will benefit from this. It will be very difficult to build any sophisticated PAW application without this.|
How should it work?
In the prompt for the Action Button you should be able to select the linked item that should provide the value for the prompt.
For a link to the currently selected value of a Set Editor you should just be able to drag a link to that Set Editor.
For a link to the Selected DBRW you should be able to drag a link to the Grid and you should be able to specify the Dimension/Hierarchy in the Grid from which you want to get the selected Element.
For a link to a cube value you should be able to drag a link to the cell from which that value should be taken and change an option to say that you want the value from that cell.
There should also be a option to take the value from a calculation.
What Benefit - Without this facility in my view PAW is not fit for purpose. You would always need to resort to embedding a TM1 Web Sheet and therefore I would suggest that you might as well continue to use TM1 Web and forget about PAW, which is what my client is currently doing.
The only alternative at present is to make PAW store the selections from Set Editors, etc in a cube, to have a TI that has no parameters, and to instead read the selections in from that cube as a way of getting parameters into the TI process. That was what we have to do in version 7.0 of TM1. PAW should be an improvement on that.
|Priority Justification||We will not even evaluate PAW for production use, until this facility is present.|
|Customer Name||Department of Business, Energy and Industrial Strategy|