: Remedy Development Best Practices
To: arslist@ARSLIST.ORG
**
I am kind of a nut about this since 7.x came out.
Fields: Custom numbering in a predictable range. Generally when customizing an
existing form I start with something like 600100200 for the field ID's. Using
this method you can easily
, 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
Sent: Wed 02/18/09 12:42 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Development Best Practices
Great summaries of customization best practices! The only thing I would add is
on the documentation; you need two different kinds of docs:
1. Functional descriptions of each feature added
Title: RE: Remedy Development Best Practices
**
I do not rename any of the 'container" objects...forms , guides or applications.
I DO include them in a packing list.
For shared workflow...you could create a "global or common or shared" packing list for these.
For documentation..
*To:* arslist@ARSLIST.ORG
*Subject:* Re: Remedy Development Best Practices
**
I am kind of a nut about this since 7.x came out.
Fields: Custom numbering in a predictable range. Generally when
customizing an existing form I start with something like 600100200 for the
field ID's. Using
@ARSLIST.ORG] On Behalf Of Steven
Iocco
Sent: Tuesday, February 17, 2009 3:10 PM
To: arslist@ARSLIST.ORGmailto: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
: Remedy Development Best Practices
**
I am kind of a nut about this since 7.x came out.
Fields: Custom numbering in a predictable range. Generally when
customizing an existing form I start with something like 600100200 for the
field ID's. Using this method you can easily run a simple SQL
(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor
Sent: Wednesday, February 18, 2009 4:28 PM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Development Best Practices
I'll point out one guiding principle that I try to follow that I haven't
seen anyone else point out yet
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
)
[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
% (global fields)...these are the field ranges I use.
Bruce Sisk
BFS Enterprises
-Original Message- From: Ray Palla <ray.pa...@insona.com>Sent: Feb 17, 2009 4:33 PM To: arslist@ARSLIST.ORG Subject: Re: Remedy Development Best Practices **
Generally speaking Steve;
The best
Of bruce sisk
Sent: Tuesday, February 17, 2009 6:30 PM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Development Best Practices
**
A little used feature of the Remedy admin tool is the packing list
feature. I work within the packing list or workspace. I add the
existing workflow or forms
PM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Development Best Practices
**
I am kind of a nut about this since 7.x came out.
Fields: Custom numbering in a predictable range. Generally when customizing an
existing form I start with something like 600100200 for the field ID's. Using
13 matches
Mail list logo
