Generally speaking Steve; The best method is to disable the OOB workflow and then do a Save As... Renaming to your custom nomenclature. Modify and enable the new workflow. You can then save a .def file of your new workflow to import (if needed) following a new patch or upgrade. Often following an upgrade your old OOB workflow will be re-enabled, so a .def of those is usually a good idea to keep track of them and allow you to compare any modification made by the update. As far as naming convention... Some people put the company name (ABC) at the front of the old name, but I find it's easier to find them alongside the original code if the company name is added to the end. For field IDs I let the system pick it unless I'm using the field in multiple forms and want continuity across them. Everyone has a different way of assigning their own IDs. I've seen some separate ranges for each specific field type, while others just go with a large group that is not in the Remedy reserved range. To each his own. I find that there is little gained by either approach and tracking them is time consuming. Have fun; R
_____ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Steven Iocco Sent: Tuesday, February 17, 2009 3:10 PM To: arslist@ARSLIST.ORG Subject: Remedy Development Best Practices ** Hi folks. Just wondering what practices some developers are using for custom code and enhancing ootb workflow. IE, field ID's in a non reserved range, New workflow easily identified perhpaps by the company name etc. My real big dillemma is modifying existing workflow. Does anyone have some best practices for modifying existing workflow so that in the event of an upgrade pitfalls can be avoided or at least anticipated? Thanks Steve __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
