More on real-time reporting on Contributor

Since I’ve got a couple of questions considering how to do it, I’ll get in more details on setting up Event Manager to detect application changes. See original post, and mind the second PS, especially.

Some background:
datadatetime column in nodestate table of application database is changed when user saves data, so we want to detect this event.
You need to add a framework package, targeting nodestate table (all columns, except xml data, to fasten things up).
And you’ll have to add a publish task (an incremental if you want it fast), and publish it to Cognos Connection.

You need to set up Event Manager like:
1 Create new event
2 Set up event condition of (1=1), or something that evaluates to “true”
3 Add job of publish
4 Go to manage task execution rules
4.1 Set up key of nodeguid (unique elists)
4.2 Set up Ongoing Events to Change and select datadatetime as change key. That is every time datadatetime “changes” ) an event will be raised.
5 Schedule the event on 1 min basis and you’re “on air”

  • Carsten

    Thanks Yuri,
    I just set it up for the “go_new_stores_contributor” apllication. Working perfectly.
    However I haven’t had the “nodestateguid” and “changetimeid” in the nodestate table (?? is that a version thing?). I used the “nodeguid” and “datadatetime” instead and it is working, too.

  • http://ykud.com ykud

    I mistyped with nodeguid — it’s there since I can remember (Adaytum 2.4 to be precise).
    I’ll check about “datatime” — maybe I’m wrong with column name as well, got no place to check now.

  • d3h9

    “datadatetime” . Carsten is right.

  • http://ykud.com ykud

    Well, datadatetime it is then.
    Thanks

  • Pingback: ykud » Blog Archive » Event manager usage

  • Pingback: ykud » Blog Archive » Incremental Administration Links

  • http://www.cdp.co.nz Ben

    Thanks Yuri! – I used that to automatically run an admin link between elist items for inter-company activity when ever the datadatetime changed.