Supporting History

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • 1.1
    • Affects Version/s: 1.0
    • Component/s: Foundation
    • None
    • Environment:

      N/A

    • Hide

      The TC needs to discuss this and come to a conclusion on how best to handle change history.

      Show
      The TC needs to discuss this and come to a conclusion on how best to handle change history.
    • Hide

      Based on the vote on a motion to move this issue to a future release that was unanimously carried. I am moving this issue to release 1.1 of S-RAMP.

      Show
      Based on the vote on a motion to move this issue to a future release that was unanimously carried. I am moving this issue to release 1.1 of S-RAMP.

      Issue-014 from the contributed issues document

      Upgrade lastModified... attributes to support longer history of changes.

      Both lastModifiedTimestamp and lastModifiedBy currently are required and have a default cardinality of 1.
      The question is should we change these attributes in the Core Model to their own type and then have a
      sequence of them in the BaseArtifactType?

            Assignee:
            Kurt Stam (Inactive)
            Reporter:
            Vincent Brunssen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: