Ben Yes that works as long as the check result can not and does not change between submit and reconciliation.
Bmc advise not to create workflow at the cmdb level except for workflow executing rules. Unfortunately it is more flexible and faster to do so as you realise. Matt -----Original Message----- From: Ben Chernys <[email protected]> Sent: Wednesday, June 24, 2009 4:17 PM To: [email protected] Subject: Re: Recon Jobs Questions - a solution for handling merge qualifications across datasets. Here's the fix I settled for. In brief: Add an attribute called "TakeMe" to BaseElement. The can be a character field or an enum with two values (plus $NULL$): TakeMe, Check On each submission, if TakeMe is NULL, the CI being submitted figures out if it is to be the one or not. If it is, it sets TakeMe to Yes and pushes TakeMe=NULL to all other datasets. If not, is sets itself to NULL and pushes TakeMe=Check to all other datasets. The recon jobs then only look at their datasets and process TakeMe = TakeMe. You can make any conditions you like in a filter guide fired on Submit, Merge, Modify, Delete, etc to set the TakeMe flag. You can exclude the recon user in the filter that fires the guide. You can also set it to the original value when the user is the recon user. This does not slow down the recon jobs at the expense of a small slowdown in submits. Cheers Ben Chernys Ben Chernys [The entire original message is not included] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
