This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Changes to the main form that affect the archive form

Saving the main form to a different form name

If you save a main form in BMC Remedy Developer Studio using the Save As function, the archived settings are not saved to your new form.

Configuring the Archive Type

On the Archive page of the Form Properties dialog box of the main form, if you select None from the Archive Type list, the connection between the archive form and the main form is broken. All archive information is lost, and the archive form is treated as a regular form.

Instead of losing the archive information, clear the Enable check box, and the archiving information is preserved. To resume archiving, select Enable again.

Qualifications

You can select the data to be archived based on a qualification. If you do not specify a qualification, all the data in the form is archived. Consider the effect on performance when using this option.

Licensing

When you license an application and license the main form, the archive form is also licensed.

Changing field properties on the main form

When you modify the following properties of character fields on the main form, the BMC Remedy AR System server updates the archive form:

  • Attributes
  • Entry mode
  • Field limits
  • Help text

When you modify the following properties, the archive form is unchanged:

  • Display properties
  • Index for FTS
  • Permissions
  • FTS and MFS settings for form fields

Fields on archive forms are always read-only.

Deleting archive fields from the main form

When you delete multiple fields from the main form, the BMC Remedy AR System server attempts to delete those fields from the archive form. If any of those fields contains data, none of them are deleted from the archive form.

However, if the fields are deleted one by one from the main form, the fields that do not contain data are deleted from the archive form.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Andrej Kajzer

    I have an issue on 9.0.01 HPD:Help Desk (overlay) is imported to another server i get an error that HPD:Help_Desk_Archive fields are missing.

     

    I am still able to save / modify form.

     

    What is the case? I also noticed that HPD:Help_Desk_Archive do not show the same UI as changed ootb HPD:Help Desk which is saved as overlay.

    How are ootb forms like HPD:Help Desk and Archive form synced? I was expecting to have at least same fields on Archive form when I add them to HPD:Help Desk.

     

    Thanks!

    Jan 13, 2016 08:07
    1. Prachi Kalyani

      Hello Andrej,

      We are verifying this with the concerned SME. We will get back to you on this.

      Thanks,

      Prachi

      Jan 18, 2016 01:34
    1. Prachi Kalyani

      Hello Andrej,

      Sorry for the delay in response. This is an open issue and we will be fixing it in future releases.

      As workaround for this issue, you must add the missing fields in the archive form manually and then create an overlay.

      Hope this helps!

      Thanks,

      Prachi

      Apr 14, 2016 05:57
  2. Fritz Erlangga

    Is this still issue on latest version (18)?

    I import .def and I get an error that HPD:Help_Desk_Archive fields are missing

    Oct 31, 2018 09:28