Ok..I created the overlay so the form went from unmodified to overlaid in Best 
Mode. So I go to create a field and it states to create a new field it must be 
in view overlay...do you wish to continue. So I did and then created my field 
and made all the needed changes to the properties...oh and I didn't get the ID 
out of range error this time. The thing is I created a filter like this for 
that field...basically:


ACC,
Please close tag assigned to the SOC for Ticket # $Ticket Number$ for $Location 
+$ as the SOC trouble ticket has been closed and issue resolved. ED tag $ED Tag 
#$


When this runs it has all the fields except the ED tag field populate in the 
message. I compared ED (Equipment Discrepancy) Tag to the Location field and 
all looks pretty much the same except the name and ID of course so I have no 
idea why it is not populating. Any ideas?
Thanks,
Ron Young

"To the world you may be one person but to one person you may be the world."

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Longwing, Lj
Sent: Monday, October 07, 2013 1:17 PM
To: arslist@ARSLIST.ORG
Subject: Re: ...ranges out of reserve range

**
Ron,
First - Stay out of Base mode...if you can't do something in Best Practice, you 
need to figure out how to do it there....going to base IS NOT THE ANSWER to 
your problem...

Second - More than likely the reason you couldn't create a field is because you 
were right clicking somewhere on a view that hadn't been overlaid (despite the 
form being overlaid)...and when a view isn't overlaid, you can't 'customize' it 
with new fields...so the option is disabled...

So...if the form is overlaid, and you need to add a field to the form 
somewhere...overlay the view as well.

On Mon, Oct 7, 2013 at 12:11 PM, Joe D'Souza 
<jdso...@shyle.net<mailto:jdso...@shyle.net>> wrote:
**

Ron. That warning thing does not mean much.



In fact I wish BMC rewrote that message under other different conditions.



Personally I stay away from the 10000000x range. From observation of what you 
see in the fields meta table, BMC Software has encroached on that range and 
have built field sin that range.



I usually use field IDs in the range 600000000 to about 999999999 - you do get 
a warning that you are trying to save a field outside blah blah blah.. This is 
a range that BMC Software appears to have not built a single field on, if you 
look at any of the out of the box applications. I think we are safe to use that 
range.



By the way if you are using archgid to change the field ID's when you recognize 
the need to change them, make sure they are not used in the mappings of filters 
that are setting fields from web services. The archgid does not change ID's in 
those filters and does not report on its verbose that it has not. You will have 
to redo those mappings manually. From my conversation with Doug, he stated that 
since archgid was developed way before web services was a feature in the AR 
System, it got left out when it became a feature.



If there is enough demand for it to be rewritten to include and consider web 
services in its use, it might get re-written.



Joe

________________________________
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Young, 
Ronald P.
Sent: Monday, October 07, 2013 1:58 PM

To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: ...ranges out of reserve range

Thanks much Michelle for the below email!

I know I have inquired about this previously but I want to follow up because I 
am still getting the same error. I have Dev 8.0. I am in "Base mode" because 
even in Best Mode not would not let me add a character field...it was grayed 
out. So I went back into Base mode as I see in the chart below to create this 
field. Once I got the field the way I wanted it I clicked save and it gave me 
the "out of reserved range id" error. Most of the fields on the form...origin 
form start with like 536######...for instance 536873894. Anyway, it would let 
me save it but I cancelled and changed the field ID to say 100000004 and it 
saved with no error. Am I wrong in doing that or what should I do. The previous 
time I received this error I looked at the help files and it talked about the 
reserved ranges and that I should use 100000000 and up until a certain number 
(don't have that in front of me right now.) The thing is I have several forms 
that my team lead is wanting me to change and I don't want to run into this 
every time I change or add a field. Let me know what you think.

Thanks,
Ron Young

"To the world you may be one person but to one person you may be the world."

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Lucero, 
Michelle
Sent: Tuesday, October 01, 2013 12:40 PM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Re: Form Edit

**
Hi, Ron:

To be on the safe side, simply don't step out of 'Best Practice Mode' at all.  
The description you gave sounds as if you stepped out of 'Best Practice Mode' 
into 'Base Development Mode' and made the change.  Just don't go there.

If any object in your environment shows "Unmodified", then consider it a BMC 
OOB object.  Create an overlay to make a change to said object.  Below is a 
table of Customization Types you'll see in Developer Studio.

--the text in the table below can be found in Developer Studio Help
Customization Type

Description

Mode

Custom

Identifies custom objects

Best Practice Customization

Overlay

Identifies overlay objects

Best Practice Customization

Overlaid

Identifies overlaid origin objects

Base development

Unmodified

Identifies origin objects that are not overlaid

Best Practice Customization and Base Development


My interpretation of Customization Type:
Custom - Objects you or other developers in your environment have created in 
Best Practice Customization mode (as you should always do).
Overlay - BMC OOB objects that were customized by you or other developers in 
your environment in Best Practice Customization mode.
Overlaid - BMC OOB objects that were overlain.  You will only see this 
customization type in Base Development Mode.  If you see it, you're in the 
wrong mode.
Unmodified - BMC OOB objects that haven't been updated in anyway by your or 
other developers in your environment.

Two Resources:

-          Developer Studio Help - lots of articles on overlays

-          BMC Webinar from last week - "Overlays and Customizations"

Hope this helps.
Michelle

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Young, 
Ronald P.
Sent: Tuesday, October 01, 2013 10:56 AM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Re: Form Edit

**
Got it...so custom is just used when I create something totally new in Best 
Practice correct? Anything, original say in Base Mode should be just be 
overlaid in Best practice mode and not converted to custom correct?

Thanks,
Ron Young

"To the world you may be one person but to one person you may be the world."

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Karthik Nagaramu
Sent: Tuesday, October 01, 2013 10:50 AM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Re: Form Edit

**

Hi,
The best approach is to create overlay in best practice mode.

Regards,
Karthik
On Oct 1, 2013 11:32 PM, "Young, Ronald P." 
<rpyo...@southernco.com<mailto:rpyo...@southernco.com>> wrote:
**
Thanks Karthik. Also, let me know if that is the right thing to do by bringing 
a form  that states unmodified (in Base and Best Practice Modes) and then 
convert it to custom in Best Practice Mode or is it best to just overlay it in 
Best Practice mode?

Thanks,
Ron Young

"To the world you may be one person but to one person you may be the world."

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Karthik 
Nagaramu
Sent: Tuesday, October 01, 2013 8:14 AM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Re: Form Edit

** Hi,

Any form or active link changes midtier needs to be flushed.

Regards,
Karthik

On Tuesday, October 1, 2013, Ron Young wrote:
Quick question for you all. I brought a form from basic and converted it to 
custom. Right or was I wrong in doing that? Then I went in and made some fields 
required which worked fine but then I also made some fields hidden and this did 
not work. I am not sure if the cache needs to be flushed for this to work or 
not but that has not been done. Is that needed? I don't have access to the 
confi tool since our Remedy Server is maintained by our IT group. I did log out 
and then log back into Remedy and those areas that I made hidden are still 
there.

What do you think?

Is it always best to flush cache after editing a form or not?

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at 
www.arslist.org<http://www.arslist.org>
"Where the Answers Are, and have been for 20 years"
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
________________________________
This message, and any attachments, is for the intended recipient(s) only, may 
contain information that is privileged, confidential and/or proprietary and 
subject to important terms and conditions available at 
http://www.bankofamerica.com/emaildisclaimer. If you are not the intended 
recipient, please delete this message.
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where 
the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to