To use or not to use – Remedy core fields

September 30th, 2009 by Venkat

Every new Remedy developer will have this doubt, to use or not to use the core fields on any regular form. As everyone knows that all the Regular Forms on BMC Remedy AR System will have 8 fields with predefined id and names, though we can change the names, we can’t change the database id’s of the core fields.

Reserved fields a.k.a Core Fields

Action Request Remedy Core fieldsSource: BMC Remedy Admin Tool Regular form

1. Request ID

2. Submitter

3. Create Date

4. Assigned To

5. Last Modified By

6. Modified Date

7. Status

8. Short Description

So guys, what do you think should we use the core fields in development by renaming and re-using these fields or should we just hide if we don’t need them?

This post is in part with Remedy 101 section.





  1. Jeniffer says:

    I pesonally don’t feel to use the core fields in the workflow and always wanted to find some way to delete the excess fields because it creates unnecessary problems while users create reports.

    The reason for not using them is I can’t use match all fields by db on workflow and that’s enough for me to neglect these fields.

    Any thoughts…..

    • Venkat says:

      May be there should be some way to disable them on forms that we don’t need.

      Anyway fields like Request ID, Created date, submitter, last modified by/date should be there for all the forms.


  2. Sonia says:

    All the core fields are there for a reason and each field is important for its own reason, so its useless to debate their presence unless you can change the heads at BMC.

    • Venkat says:

      Hi Sonia,

      I agree the fact that all fields are there for a reason but there are fields like Assigned to which we may reuse but when we try to map the fields with ID from another form and if they are used for different reasons, mapping will break.

      In this scenario, we need to leave them alone, which may not be the best thing to do.


%d bloggers like this: