Documentum Email alerts

This should be an easy one, but I can't find it for the life of me.

When a user cancels a checkout an email goes to an expired account email. Where do I configure this setting? I want all emails to go to a group now and not a particular user. Thanks.

Find more posts tagged with

Comments

ckonaje

You can use combination of register and queue APIs to register for cancel checkout and using queue then send email notifications to email aliases. I guess if you can also set the user email address to the alias to get notifications. Events can be registered for by using Docbase administrator.

kjimenez

I think I was not completely clear, sorry. I am using Webtop. Is there a place in Webtop where the value is set, or do I need to script this?

Chris_Campbell

There are actually two ways. If you know how the event is being triggered and what object type, then you can use the Audit Management tool in Webtop or DA. (Check to make sure you have the proper audit management permissions first.) You can also adjust this through the Documentum Administrator interface using the DQL Editor and API Tester tools.

For the type of operation you're looking at, using DQL and API will be your best bet. Here's a quick run-through on how I'd do it. Maybe it's not the best way, but it should work. (As always, read up on your Content Server manuals before trying anything and don't blame me if something goes wrong.)

There's a quick way to do this, but I'm going to show you around the table before doing any changes. (Never update a table blindly without looking at it first.) Open up the DQL Editor and type in: select * from dmi_registry. You'll get a list of all the events being audited. You're looking for two things here: the user_name and the event. Whenever an event occurs, the system matches that event and fires off an email to the person listed in user_name. In this case, you're looking for whatever entries in this table have the inactive account is in user_name. (You could just DQL select * from dmi_registry where user_name = 'insert name here')

Any entries found can be removed by invoking an unregister,session,object_id,event,user API command. Or if you just want to update it to a new account name you could do the following:

fetch,c,object_id

update,c,object_id,user_name,'insert new name here'

save,c,object_id

That should do the trick. Oh, the real quick way? If you happen to have SQL access, you could just connect to the table and fire off update dmi_registry_s set user_name = 'new name' where user_name = 'old_name' which would do a global replacement of that expired account. Don't do this unless you really know what you're doing.

kjimenez

Thanks, that worked great