Index field for FragmentDefinition objects is always 0

Description

Pre-JPA DLM used to track the 'index' of a FragmentDefinition – meaning the position of the fragment within the XML config file.  In modern DLM the file is gone, but the field is still there (and it always has a value of 0).

This discrepancy doesn't seem to have a significant negative impact on the portal, but should be cleaned up.

Environment

None

Status

Assignee

Andrew Wills

Reporter

Andrew Wills

Labels

None

Estimated End Date

None

Fix versions

Affects versions

Priority

Major
Configure