Hi All, I have added a new free utility to help you get started with the new Best Practice Development Mode in Remedy 7.6.04.
This utility will convert old definitions into Custom Objects before you import them into your new server. This would convert an old def-file to Custom objects: C:\...>rrrDefBPCU -i old63.def -o custom76.def -t cust -a At the moment you can only convert to/from Base and Custom, but that is still a great help if you want to avoid the BPCU-utility from BMC, hacking with the driver-program, or doing save-as on each and every object... The def-import-functionality in Dev Studio seems to double-check everything, which makes it impossible to destroy your things. The downside is that you need to delete the objects before you import the converted definitions. Note that this is not (yet) a replacement for the real BPCU-utility, as it does not find your old ITSM-customizations and split these into Base and Overlay. Other interesting things I have learned during this endeavor, is that you can not create Deployable Applications in Custom mode, nor can you Overlay a Aeployable Applications. You can, however, add new forms to your application in Best Practice Mode... Download the tool from: https://www.rrr.se/cgi/tools/main#rrrDefBPCU Please let me know how it works out, and if you are missing some kind of functionality in the utility. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. usage: rrrDefBPCU -i old/cust/base.def [ -o custom.def ] -t { cust | base } [ -v ] [ -a ] [ -e encoding ] This utility converts your old or Base definitions to Custom objects, or back from Custom to Base, for use in 7.6.04 in Best Practice Development Mode (within Dev Studio). This can come in handy if you want to import your old definitions, promote current objects from Base to Custom, or vice versa. Any objects, such as forms, filters, active-links, etc in your input definition will be converted if needed. Just import the output definition into your system. NOTE that importing in place does not work to convert objects, for some reason. The Remedy server will protest with ARERR 8861 - Base and overlay object must be the same type. -i is the old or base definition that you want to convert. -o will be the resulting definition created by this tool, otherwise a report of objects needing a change will be printed. -t cust tells the utility in which format you want the target. -a will include all input objects in the output definition, not only those objects that were changed. -e will set default encoding for input and output files. This is only needed for old definition files where the encoding is not specified on the first line. -v verbose will print the status for all object names. Please contact us at support.se if you would like to see any other direction for your conversions, or have anything else to report. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
