At the most recent site I worked, they used a slightly similar prefix as
yours.. They had an internally generated 3 digit schema ID for every schema
that is customized or developed, (not the ID from the arschema), and used
that ID for the middle 3 digits... that left you with 6 digits for other
stuff.. They used the leftmost 3 digits for field type and right most 3
digits for incrementing the field ID
I had a personal preference in the past that was somewhat similar.. but
instead of giving every customized or developed schema a new number, I gave
a sub-module I considered it a part of an ID and used this as a middle 2 or
3 digit number. Usually 2 digits when you break every of those 1500+ schemas
into different sub-modules should be enough, but if you roll over then
stepping into the 3 digit mark isn't that bad an idea either.. I used the
left 2 digits for type of data (not data type), and the remaining right
digits for incrementing field ID's. When using this method if you can remain
within the 2 digits ID, you could even possibly squeeze in another 2 digits
for something else (developer who originally developed a field, or internal
version when the field was developed, whatever...)
For eg when working with CTM:People or any CTM:People related form,
designate a 2 digit sub-module ID say 99 and if you considered contact
information within the people form to have type of data ID to be 60, and if
I wanted to add lets say Skype ID field to People form, I might choose the
ID 60-99-00000 which translates to 609900000 would be used.. The next
contact information related field, LinkedIn URL would be 609900001.
I also had a personal convention for table fields and page fields that my
previous customer adopted.. If using the above algorithm lets say if I had a
page or table field main ID of 819900000, then the columns or pages as the
case may be would start getting ID's of 819900001, 819900002, 819900003,
etc.. For these fields I also had a Naming prefix for database names which
serialized the database names serially for the main page of the table
followed by pages, as well as table and their columns in table fields..
There are numerous conventions you can design to achieve that as I used more
than one convention to do this at different sites..
Although I was using this method for a long time, I did feel some of the
things used in my previous projects were a good idea so I might use a blend
of both sets of ideas to come out with a new personal convention..
Joe
-----Original Message-----
From: Reiser, John J
Sent: Friday, September 09, 2011 9:20 AM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: EXTERNAL: Re: "Outside of Reserved Range" warning?
Joe,
Re. your rant about field IDs needing alphas. That would be a great idea if
BMC could pull it off.
The range of ID numbers that I use a pulled from the telephone keypad.
TPAG forms all have ids that start 872400000 - 872499999
MRBC forms 672200000 - 672299999 etc
When I get a prefix that would be below 536870912 (that number in burned
into my memory) I add 1 as the left most digit 1536870912 which is still in
the acceptable range for developers.
The place this has failed me is when I want to reuse a modular form/workflow
combination and the key field ID starts 8724xxxxx and the modular part is
looking for a field id of 6722xxxxx.
Makes me want to rethink it and build everything as if it will always
interact with other objects in the system.
---
John J. Reiser
Remedy Developer/Administrator
Senior Software Development Analyst
Lockheed Martin - MS2
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased by
me
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe Martin D'Souza
Sent: Thursday, September 08, 2011 3:02 PM
To: [email protected]
Subject: EXTERNAL: Re: "Outside of Reserved Range" warning?
Yup :-) I think that was when I first learnt the use of archgid..
Unfortunately we found it out at a customer that didn't have a separate
development server.. Fortunately for them though, they had very few
customizations that were lost and were able to redo it within a few days..
And they still didn't bother to invest in a development server after that..
Go figure..
Joe
-----Original Message-----
From: Meyer, Jennifer L
Sent: Thursday, September 08, 2011 2:40 PM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: "Outside of Reserved Range" warning?
I remember that upgrade!
Ahh, the good old days.
Jennifer Meyer
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe Martin D'Souza
Sent: Thursday, September 08, 2011 12:20 PM
To: [email protected]
Subject: Re: "Outside of Reserved Range" warning?
David,
There was one version, I think when moving from 4 to 4.5 or somewhere
thereabouts, where Remedy Engineering accidently used the starting
non-reserved range 536,xxx,xxx that messed up some customizations that were
done using that starting non reserved field ID's. Since that time my
personal preference was never to use that, even if it is a trim field (line,
box, text) you are creating.. Until then I happily used that range for those
kind of fields. With the introduction of shared workflow, choosing your
field ID's became even more important even for some trim fields like text
fields..
So my personal preference was to use the 800,xxx,xxx to 999,999,999 range
but I see nothing wrong with starting from 600,xxx,xxx...
Choosing this higher number deliberately, you can almost guarantee yourself
that an accidental intrusion by BMC Softwares engineers on the 536,xxx,xxx
in any future patches or releases will not impact your customization.. There
is hardly a chance they would use the 600,xxx,xxx to 999,999,999 range
deliberately..
Cheers
Joe
-----Original Message-----
From: David Durling
Sent: Thursday, September 08, 2011 8:43 AM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: "Outside of Reserved Range" warning?
Is starting at 600,000,000 just a convention people in the ARS community
have chosen, or is there a real risk of running into a problem by starting
at the 536,xxx,xxx range the system will use by default if you're creating a
new form?
According to KA315200, a field range of 536870913 to 2147483647 can be used
for ARS 7.1 and 7.5.
David Durling
University of Georgia
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of White, Michael W (Mike)
Sent: Wednesday, September 07, 2011 4:20 PM
To: [email protected]
Subject: Re: "Outside of Reserved Range" warning?
"I seem to recall that 600,000,000 to 999,999,999 is reserved for custom
development.".
We roll our own and use that range.
Mike White
EMail [email protected]
Office 813.978.2192
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Logan, Kelly
Sent: Wednesday, September 07, 2011 4:14 PM
To: [email protected]
Subject: Re: "Outside of Reserved Range" warning?
"One. . .Two. . .I think you're right. . ."
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Tommy Morris
Sent: Wednesday, September 07, 2011 12:20 PM
To: [email protected]
Subject: Re: "Outside of Reserved Range" warning?
Yeah, I meant 600 million. I still have trouble counting to 5 so numbers
larger
than that stump me. :)
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Meyer, Jennifer L
Sent: Wednesday, September 07, 2011 11:19 AM
To: [email protected]
Subject: Re: "Outside of Reserved Range" warning?
Huh. I suspect it's the number of digits in your ID that's causing the
issue. I
seem to recall that 600,000,000 to 999,999,999 is reserved for custom
development. Field IDs 599,999,999 and below are for BMC's use, but I
don't
recall anything about using IDs above 1,000,000,000.
Jennifer Meyer
Remedy Technical Support Specialist
State of North Carolina
Office of Information Technology Services Service Delivery Division ITSM &
ITAM Services
Office: 919-754-6543
ITS Service Desk: 919-754-6000
[email protected]
http://its.state.nc.us
E-mail correspondence to and from this address may be subject to the North
Carolina Public Records Law and may be disclosed to third parties only by
an
authorized State Official.
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Reiser, John J
Sent: Wednesday, September 07, 2011 12:03 PM
To: [email protected]
Subject: "Outside of Reserved Range" warning?
Hello Listers,
ARS 7.6.03
MS SQL Server 2005
VMWare Windows 2003 Enterprise
I've been working in the Dev Studio for a while and I keep getting the
following response when I create fields.
"You have specified an id for the following fields which is outside the
BMC
reserved range. Do you want to continue?"
I could see a warning for creating a field inside the range of reserved
field ids
but outside?
Is there a config setting in Dev Studio to stop this message?
The field ids that I use are all between 1,587,700,000 and 1,587,711,199
Thanks,
---
John J. Reiser
Remedy Developer/Administrator
Senior Software Development Analyst
Lockheed Martin - MS2
The star that burns twice as bright burns half as long.
Pay close attention and be illuminated by its brilliance. - paraphrased by
me
____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
