The 7.1 Import Tool also allowed this. The problem is still not addressed. The problem is not with the primary key of the record being imported but with additional attributes included in that record that are keys to other records. These additional attributes need to be looked up and altered.
To take your example of Recon. Look at an attribute level precedence record. The key of instance id is not the problem. There is an attribute called attribute instance id which is the instance id of the OBJSTR:Attribute record of the attribute in Q (Recon was the first of a better breed of references). The field id of that attribute is also in that record but the Recon engine references the OBJSTR:attribute record which fails if it is incorrect. In this case, however, the fix is simply a filter on merge to set the right instance id of the OBJSTR:Attribute record by using the class id and attribute field id to look up that instance id. Of course, perhaps if the CMDB driver were used (as you and other have recommended) to migrate simple class changes instead of having manually added fields on various machines through the class manager gui as one customer has done, the problem would not appear on recon at least - Recon job definitions ARE a better example. Consider transferring people. The instance id is well and good for the person, but the "key" for a permission is the combination of the person id (and redundantly its instanceid) AND the request id of a Support Group record. These will very rarely be the same across environments. In many cases these instance ids and request ids are redundant (esp. when the lookup symbolic is also in the record) but must be set correctly as some OOTB workflow uses one set of linking attributes and other workflow use other linking attributes. Of-course, none of these linking columns are documented! :) Cheers Ben -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of P Romain ARSlist Sent: June 26, 2009 2:22 PM To: [email protected] Subject: Re: How to export data (PROCESSES) from BMC Remedy User tool The same issue occurred with AIE and Recon jobs. In 7.5 this is eased by the new incarnation of the Import Tool which can use any field as a key field (such as instanceid for recon jobs). -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ben Chernys Sent: 26 June 2009 13:05 To: [email protected] Subject: Re: How to export data (PROCESSES) from BMC Remedy User tool No worries Rick. Indeed that was the point that Axton was trying to make. I know the point well as I've done had to do many of these tasks myself. The only problem with your approach you suggest is that the original problem of incorrect references in the data is not addressed. To extend your idea to handle that would require importing into staging forms and all the necessary filters to push to the real forms, or, of-course, using the API. IF and only if you maintain request ids, then this step could be avoided. Otherwise, you'll be faced with either the API or the above development project. I have found maintaining Ids across systems to be virtually impossible once systems go live. To whit, see the Data Management Tool to load foundation data. This is a huge tool with an inordinate number of forms and filters and took a horrendous amount of time to develop and comes with its own set of patches and fixes. All this just to load data into an application? Yes, the API would solve the problem nicely. But that carries the requirement to have a programmer - most ARS administrators are not programmers - and costs and time associated with maintaining source code. With Meta-Update, any ARS administrator/developer/consultant can develop API level scripts in very short order. Many scripts are already developed. It is this development time that Meta-Update saves. In addition, Meta-Update is replete with value transformation functions in its assignments, including a LookUp facility, a regex pattern extracts, SQL, ARS queries and the like. It can read CSV files that Excel or the BMC Import tool cannot. It can export CSV files and other files. All these result in a company gaining incredible control over ITSM foundation and other data with minimal development. Why don't you take a look yourself? Cheers Ben -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Carey Matthew Black Sent: June 26, 2009 1:42 PM To: [email protected] Subject: Re: How to export data (PROCESSES) from BMC Remedy User tool Ben, Thank you for pointing out that your third party product (from softwaretoolhouse.com) has a feature that might be able to help. I think the point that Axton was trying to make is that the out of the box application does not offer such a feature. I am sure that Axton (or any other programmer) could also write an ARS API based program (C, Java, Perl) to do the task as well. But it is nice to know that a software manufacturer out there saw a need and produced a tool to make this easier to do too. Krishna, I would also suggest an alternate approach to all of this as well. I must admit that it is a bit half baked, and has some of it's own downsides. (Like not being fully tested on my part.) But I think the idea is worth kicking out there.... What about this as an approach to try to use the Out of the box features and not have to use programming to get the job done? ) Create a Deployable application with NO OBJECTS other than DATA. ) Create queries for the forms that would get all of the needed data from the various forms. ) Export the application from Server A. ) Import the application to Server B. I think the data features of Deployable applications let you export and import the data in a way that would let you do what Axton was suggesting. If so then BMC could release such a def file "add on" and it simply could be used by customers to "skim data" from one server to the other. Obviously this approach would require the use of the Admin Tool (er... Dev Studio) to get the job done. However, I would also think that BMC could use RIK (or maybe just the Driver script) to allow customers to be able to schedule such a transfer of data too. Like I said... just another thought on how to achieve this goal. I hope some of these responses are helpful. As you can tell, after defining what you are trying to do, this community can be creative. :) I hope the suggestions/ideas help. -- Carey Matthew Black BMC Remedy AR System Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Fri, Jun 26, 2009 at 5:18 AM, Ben Chernys<[email protected]> wrote: > "There is no way to export bundled approval processes." > > Not true. > > There is an easy way to automate both export and import of a bundled > approval process, or anything else, for that matter. <snip> insert product plug here </snip> > 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 Axton > Sent: June 26, 2009 7:09 AM > To: [email protected] > Subject: Re: How to export data (PROCESSES) from BMC Remedy User tool > > There is no way to export bundled approval processes. You will need > to go to the AP forms to export the necessary data: > AP:Process Definition > AP:Rule Definition > AP:Notification > AP:Alternate > etc. > > I have found it best to maintain the entry ids between various servers > when moving approval related data so that I can make changes in one > environment then update data in other environments. I also prefer the > arx format as it seems to handle things best when going from arserver > to arserver. The import tool supports updating existing entries based > on the entry id. > > Axton Grams > > On Fri, Jun 26, 2009 at 12:00 AM, RKVKRKVK<[email protected]> wrote: >> Hi, >> >> Thank you very much to your reply. >> >> Actually what i am looking in BMC Remedy User is, There is a link >> called "AP. Administratoin" after logging to the BMC Remedy User >> which is used for to create approval processes. If we click on "AP. >> Administration' link, then it will open a window and shows process, >> rule, notification, role etc and with the help of this, i can able to >> create a new process and i can able to create new rules like > "IssueApproved, IssueCanceled, IssueError" and so on. >> Once i created the process and rules, If i want to export these >> processes, rules etc from BMC Remedy User, What are all the steps i >> need > to perform. >> >> Best Regards, >> Krishna B ____________________________________________________________________________ ___ 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" ____________________________________________________________________________ ___ 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"
