If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Change statuses of e-list in the table nodestate

Started by EP_explorer, 14 Oct 2009 12:32:44 AM

Previous topic - Next topic

EP_explorer

I want to change statuses of e-list of one Contributor application based on statuses of another Contributor application - they must be the same.

I don't see any ideas to make it using base instruments. May be anybody can give advises?

I know that statuses of any Contributor application are contained in a table nodestate. I can use SQL Update to change the statuses - I even did it and saw that Contributor application changed statuses. But I want to ask - is it dangerous to application to make such things or not? May be I must change other tables as well - not only nodestate.

Cognos Planning 8.4

Wait for advises.

adityashah27

so you just want to change the elist wf state? and not data?

just curious,whats the business need to do this?

EP_explorer

Quote from: adityashah27 on 14 Oct 2009 02:03:15 PM
so you just want to change the elist wf state? and not data?

just curious,whats the business need to do this?

I will change data by using D-link ;-). But I can't change wf of state of certain elements of e-list using base methods.
And I ask ideas.

mizu

what about running a GTP macro from CAC which would reset the states of the application?

EP_explorer

This macros will reset every status of e-list elements. I want to change some statuses and don't change others.

For example - at first 100% statuses are 'Submit' and after the marcos - 30% are 'Submit' and other 70% are 'Work in Progress'.

craig_karr

We made a solution like that for a customer with a script setting the node states in one app based on another. Uppon review by Cognos they said that they could not apporve that, but the app worked fine anyway

EP_explorer

Quote from: craig_karr on 20 Oct 2009 03:14:46 AM
We made a solution like that for a customer with a script setting the node states in one app based on another. Uppon review by Cognos they said that they could not apporve that, but the app worked fine anyway

Did you only update table 'nodestate'? or any other tables as well?

Or was it another solution?

craig_karr

#7
Only the nodestate table. Cognos said it was a smart solution, but too "outside the box" in order for them to approve the solution and support it. Works fine though  ;D

EP_explorer

Quote from: craig_karr on 20 Oct 2009 08:10:38 AM
Only the nodestate table. Cognos said it was a smart solution, but too "outside the box" in order for them to approve the solution and support it. Works fine though  ;D

Thank you a lot.