Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

templateload - don't overwrite existing values on update with nulls

Description

If templateload is being used to update an existing template, it currently overwrites the:

  • name

  • description

  • archetype

  • userLevel

  • reportType

These fields are all optional in the templates.xml file, so if they aren't specified, the existing template values are replaced will nulls.

When updating an existing template where values for these fields aren't provided, they should remain unchanged.

Environment

None

Activity

Tim Gething April 1, 2016 at 4:29 PM

While work is being done on this utility, it would also be useful if the Active flag setting for an existing template was left as set.
This allows for the case where customised templates are being used.

For example we have a customised Invoice - content name Invoice-EIAH. If I load the standard templates during an upgrade, I get the standard Invoice/Invoice loaded - so I now have two Invoice templates in the system. To clean things up, I have to go through and look at all the templates with duplicate names, look at their content file name, and use this to distinguish the ones from the standard set, and delete these.

If I could just set the standard ones that I don't want as Inactive, and templateload left this flag as set, then when doing an upgrade, all the new standard templates would come in, but the ones I had flagged as Inactive would stay as inactive and thus hidden from normal view.

Regards, Tim G

Details

Assignee

Reporter

Components

Priority

Who's Looking?

Open Who's Looking?

Created March 7, 2016 at 10:10 AM
Updated April 1, 2016 at 4:29 PM
Who's Looking?

Flag notifications