TM1 App:Approver can not release consol node after owning it
Posted: Tue Oct 08, 2013 3:04 am
Guys, Hi! 
I just need explanations on this particular behaviours. A rational.
I created an approval-type application using TM1 Applications 10.1.1 (former TM1 Contributor). During our testing we came to this scenario when an approver owned the consolidated node Europe. (These approver and leaf-node contributors are all non-admin users).
Scenario:
Europe (Consol node)
Benelux (Leaf node)
Iberia (Leaf node)
Scandinavia (Leaf node)
Basically, all leaves became under the approver's ownership. But when the approver tried to release Europe (since Release icon is available), it prompted him a NO-PERMISSION error (attached).
I looked at the logs to see where it encountered the error. Surprised, it did not run a process at all. I searched and found the link below. Though not the same error, I gave it a try, but was not successful.
http://www-01.ibm.com/support/docview.w ... wg21454522
1. The error prompts only during that scenario. But when an approver owns a leaf node and tries to release it, it releases smoothly without any error prompt. Why is that and why not on the consol node ?
While TM1 does not run any process when the approver attempts to release a consol node, it does run the }tp processes when he releases a leaf node that he just owned (logs show). I'm not really sure on this error, whether something is misconfigured, or at the Web browser, or if I just need to set some additional security, or if I just need to understand the rational.
Anyway, we tested and found out that the leaf-node contributors can always own their respective nodes, so they can still input. I thought the issue above was a workflow show-stopper. Certainly not.
2. Still I wonder. After the approver owned on the consolidated node and he was not able to release that node, when one leaf-node contributor owns his node, all other leaf nodes become available
. Available from being reserved by the approver. So let's say if there are 10 leaf nodes, and the approver owned on the consolidated node, when a leaf-node contributor owns his respective node, the other nine are automatically released from the ownership of the approver. Hmm.
Please share your thoughts.
Thanks very much.
Art
I just need explanations on this particular behaviours. A rational.
I created an approval-type application using TM1 Applications 10.1.1 (former TM1 Contributor). During our testing we came to this scenario when an approver owned the consolidated node Europe. (These approver and leaf-node contributors are all non-admin users).
Scenario:
Europe (Consol node)
Benelux (Leaf node)
Iberia (Leaf node)
Scandinavia (Leaf node)
Basically, all leaves became under the approver's ownership. But when the approver tried to release Europe (since Release icon is available), it prompted him a NO-PERMISSION error (attached).
I looked at the logs to see where it encountered the error. Surprised, it did not run a process at all. I searched and found the link below. Though not the same error, I gave it a try, but was not successful.
http://www-01.ibm.com/support/docview.w ... wg21454522
1. The error prompts only during that scenario. But when an approver owns a leaf node and tries to release it, it releases smoothly without any error prompt. Why is that and why not on the consol node ?
While TM1 does not run any process when the approver attempts to release a consol node, it does run the }tp processes when he releases a leaf node that he just owned (logs show). I'm not really sure on this error, whether something is misconfigured, or at the Web browser, or if I just need to set some additional security, or if I just need to understand the rational.
Anyway, we tested and found out that the leaf-node contributors can always own their respective nodes, so they can still input. I thought the issue above was a workflow show-stopper. Certainly not.
2. Still I wonder. After the approver owned on the consolidated node and he was not able to release that node, when one leaf-node contributor owns his node, all other leaf nodes become available
. Available from being reserved by the approver. So let's say if there are 10 leaf nodes, and the approver owned on the consolidated node, when a leaf-node contributor owns his respective node, the other nine are automatically released from the ownership of the approver. Hmm.Please share your thoughts.
Thanks very much.
Art