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 Senior Software Architect Software Tool House Inc. Canada / Deutschland / Germany Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: mailto:[email protected] Web: http://www.softwaretoolhouse.com A free notepad for Diary fields: http://www.softwaretoolhouse.com/downloads/DiaryFieldEditor.htm An ARS API scripting tool used for migrations, integrations, imports, reports, extracts, batch jobs: http://www.softwaretoolhouse.com/products/SthMupd -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Matt Worsdell Sent: June 22, 2009 5:46 PM To: [email protected] Subject: Re: Recon Jobs Questions Then the only way would be to perform a copy dataset and run that process on a temp source, or use workflow execution. Messy. I have done something similar in so far as the requirement was to not merge target ci with a particular status. I had to grab the status of the target and update the source using compare and workflow execution. It does work for all classes but can be very slow. I found a stored procedure works well, I have some thoughts in how to do that within bmc reconciliation if that works for you. Matt -----Original Message----- From: Ben Chernys <[email protected]> Sent: Monday, June 22, 2009 3:53 PM To: [email protected] Subject: Re: Recon Jobs Questions Hmmm. Thanks Matt, but I think it ain't quite that easy. The source datasets cannot have their CIs deleted at any time. (requirement) 1) I do NOT want a merge activity in these conditions. Rather, based on conditions in all three datasets, I would need to select 1) whether I wanted to do a merge or not, and 2) the source dataset Have you tried the Workflow Execution stuff? It is this area of code that BMC raised the SW thingy for. That code simply doesn't work with any attributes not in BaseElement. The Trace message out of recon for this area of code use "s" instead of "%s" as a printf format string! Try also qualifications containing 0 (CLOB) length char fields from BaseElement. When you say "temporarily" do you mean DO fields? Or in the DB? The "Additionally" part is done with normal filters when the user is the recon user. Cheers Ben -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Matt Worsdell [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" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
