Hello All
I would like to know that whether reviewer can reject all child nodes from consolidate node. The users are come up with this issue as it is time consuming to reject each child when they have to reject all child submission.
Is there any way which can allow to reject submission from parent node or "Reject all child node submission'' functionality?
Thanks
Dharav
Contributor Ownership?
-
declanr
- MVP
- Posts: 1831
- Joined: Mon Dec 05, 2011 11:51 am
- OLAP Product: Cognos TM1
- Version: PA2.0 and most of the old ones
- Excel Version: All of em
- Location: Manchester, United Kingdom
- Contact:
Re: Contributor Ownership?
The first question to ask would be how often do they need to reject ALL nodes at the same time? In the event its not very often then there isn't a problem, if it is quite often (or all the time) you should consider why that is; if its because there is a common assumption that is incorrect then perhaps the inputs/approval should be entered at a different level/in a different way.
That being said - version 10.1 allowed for manual alteration of the TI scripts that run behind the scenes for contributor, so assuming that is still the case you could change the reject TI to make it loop through all the nodes... this would however mean that they always reject all nodes, so could lead to nodes being rejected even though that wasn't desired.
Another method would be to create a websheet that only reviewers have access to, it would show a cube intersection with the relevant nodes and they flag with a Y or N which ones are to be rejected; they can then press an action button which initiates a TI that loops through those selections and then executes the reject TI as a sub process for each node to be rejected.
Both above suggestions are theoretical, I have implemented neither since I am of the belief that if you use contributor (or a tool like it) then the whole point is that you use it "out of the box" - when you start "messing" with its internal workings then you are probably better off developing something yourself.
That being said - version 10.1 allowed for manual alteration of the TI scripts that run behind the scenes for contributor, so assuming that is still the case you could change the reject TI to make it loop through all the nodes... this would however mean that they always reject all nodes, so could lead to nodes being rejected even though that wasn't desired.
Another method would be to create a websheet that only reviewers have access to, it would show a cube intersection with the relevant nodes and they flag with a Y or N which ones are to be rejected; they can then press an action button which initiates a TI that loops through those selections and then executes the reject TI as a sub process for each node to be rejected.
Both above suggestions are theoretical, I have implemented neither since I am of the belief that if you use contributor (or a tool like it) then the whole point is that you use it "out of the box" - when you start "messing" with its internal workings then you are probably better off developing something yourself.
Declan Rodger