Joe, As others have said, there is no problem with what you are doing and in fact it is encouraged. It allows you to share workflow (and with granular overlays you can overlay workflow and change nothing but say to add to one more form and you keep inheriting BMC changes to it and it is attached to one more form - or 10 or 20).
There are a couple of things to consider. 1) Be very careful about any field ID below say 1000. There are special meanings for some field IDs in that range and those special meanings apply regardless of the form it is on. If you really mean it and want that special meaning, it is OK to use them, just be aware that they have them. 2) There are fields in the range between 1000 and 10000 that are sometimes used by subsystems. There are no systemic special meanings but those subsystems will interpret and use the fields for the purpose of the subsystem regardless of what you want them to be - some DSO fields if you use advanced DSO fit this bill (but those are below 1000 anyway). 3) Field names must be unique AND THEY MUST MATCH BETWEEN BASE AND OVERLAYS so if you use one of the BMC fields, it is actually best practice to name it the same as BMC does. And, you should only use that ID with the datatype and meaning as the BMC field. Why? Because of the "slip under" feature of how overlays work. If you have a field that is in BMC range on your form and we add the field to the base, the logic of the system will "slip our field under" your custom field, converting it to an overlay as it assumes that you have "advance added that field since it is a BMC range field" into your form and we are "syncing up" with your extension. This is why you want the name, the datatype, the meaning to match.... Note: This is really for use of any of the "special" fields below 10000 and when you are customizing an ootb form. If you are talking about custom forms, just worry about the below 10000 fields. I hope this is useful, Doug From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe D'Souza Sent: Tuesday, August 26, 2014 7:25 AM To: arslist@ARSLIST.ORG Subject: Using an ID like 1000000001 (BMC Software's development field range) in a home grown custom form... ** Is there any repercussion from using a field ID like 1000000001 in a custom build form? This field ID is the Company field ID in the COM:Company form and I wanted to build a 'staging/integration' form to accept data using AIE, process it if necessary, before I push it to the 'Load' form. To make the Push fields easier and speed up my development time, I wanted to use the same Field ID's and Field names. The above specific ID was just an example. I intend using the same ID's for other staging forms I build for location, site, people etc. as the ID's in their respective foundation forms. To the best of my knowledge from the documented reserved ranges, the ranges used for the foundation data in the foundation forms, are not reserved ranges for any functional type of fields. Sure they are within the BMC Software range that is used by their developers for their applications, but since this staging/integration form is fully custom, I see no harm using those Field ID's.. Did anyone have any issues doing the same? Joe _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"
