Glad the COBRAS suite is getting it done out there – many late nights and weekends on those tools over the last year or so.
The primary reason CUDD doesn’t have notification devices in it is because the database schema between Unity and Connection varies here – it does in many places but it’s usually close. Notification devices deviate a bit more than most. Notably in Unity you get a static allocation of notification devices allotted at the time the subscriber is created. Every user is guaranteed to have every notification device that can be referenced by name regardless of if they use it or not. In Connection that’s not the case – you get a set of the 5 basic ones (the ones you can get at over the phone interface) and the rest are dynamic. This means you can add as many notification devices as you like which is cool if that’s what you need. This also saves database space since obviously no one uses all of their pre allocated notification devices in Unity – they’re just parking on rows in the DB and serving no purpose.
However – when dumping data out into a flat CSV file for groups of users this presents some obvious problems. I need to cram everyone’s data into a nice linear format and if someone has a bunch of notification devices vs. everyone else that has just a couple, now I have a problem.
I could dump the pre allocated devices out (Pager, Work Phone, Home Phone, Mobile Phone and SMTP) easily enough – if this will cover what you need I can look at that this week. I’ll have to be explicit, though, that the notification devices created on top of that won’t be included in the output. If it’s necessary to get all the user/admin created devices on top of that I’d have to get real fancy and run through all the users selected for output and construct an super-set of all notification device names when creating the columns for output up front before starting the dump – that’s a bit more involved, however – I’d have to put that on the longer term to-do list.
