1 Reply Latest reply: Aug 28, 2012 9:46 AM by Ron M-Oracle RSS

    Any Database Query to Find User Making Last Edit to Spec

    BeckieC
      Is there any table in the PLM4P database that records the user PKID for the at least the latest edit on a specification?

      We know this information is not presented in the UI. If we can find out if this is recorded anywhere in the database, we can write a query when this info needs to be known.

      Our business case is:
      The spec originator (author) has left the company, so we have allowed DRAFT edit rights to the entire group and not just the author.
      Now we want to determine which group member made a recent change.

      Thank you.
        • 1. Re: Any Database Query to Find User Making Last Edit to Spec
          Ron M-Oracle
          The commonLifecycleEventLog table should give you the history of each spec in terms of edit/saves.

          Details about the table are the following, taken from the Extensibiltiy Pack, Extensiblity Guide, in the Event Model chapter

          As specific events occur in GSM and SCRM, their details are captured and recorded in
          a single database table. Clients can watch for events added to this table to trigger some
          custom actions.
          Each event captured may include the following information:

          - Event Type—The type of event that occurred (1: Create, 2: Save, 3: Workflow, 4: Copy)
          - Event Source—What caused the event (New issue of a specification, workflow
          transition, etc.)
          - Actor—User who performed the event
          - Time—Date and time stamp of when the event happened
          - Affected Object—Specification or object that was acted upon (Specification that was
          saved, specification that was copied, etc.)
          - Related Object—Related object when appropriate (Workflow step, smart issue
          request, specification ID, etc.)
          - Reason—Reason the action occurred when appropriate (Workflow comments, global
          succession reason for change, smart issue request that caused the change, etc.)