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.)
Possible Uses
The events captured can be the catalyst to a third party
system action (email notifications, data comparisons, etc.).
1.
Every time an ingredient specification is
created, the Ingredient Manager is notified by email.
2.
Every time a new specification issue is created,
a comparison will be performed. If any compliance data has changed, the
facilities producing the product will be notified when opening the
specification in custom portal.
Technical Overview
A feature configuration setting Common.Auditing.LifecycleEvents.Enabled determines if
events should be logged.
Events are captured in the commonLifecycleEventLog database
table:
|
commonLifecycleEventLog
{
pkid char (40) not null unique,
eventType int not null,
eventSource varchar(50),
timestampDateTaime not null,
factor char(40) not null,
char(40) not null,
reason nvarchar(256),
fkRelatedObject char(40)
}
|
- - create, save, workflow, etc.
- - cause of the event
- - time of change
- - user making the changefkAffectedObject
- - changed data object
- - user comments
- - optional participant
-
|
The event type codes include:
Create—1
Save—2
Workflow—3
Copy—4
|
|
Table of Logged
events
|
|
event source
|
event type
|
affected object
|
related
|
|
GSM.Editor
|
Save
|
Specification
saved (pkid)
|
·
|
|
GSM.Clone
|
Create
|
New specification
created (pkid)
|
|
|
GSM.Clone
|
Copy
|
Specification
copied (pkid)
|
New specification
created (pkid)
|
|
GSM.NewIssue
|
Create
|
New specification
Issued (pkid)
|
|
|
GSM.NewIssue
|
Copy
|
Specification
copied (pkid)
|
New specification
created (pkid)
|
|
GSM.Workflow.Transition
|
Workflow
|
Specificationification
transitioned (pkid)
|
Workflow Step
(pkid)
|
|
GSM.Workflow.Resolve
|
Workflow
|
Resolved specification
(pkid)
|
Workflow Step
(pkid)
|
|
GSM.Workflow.Resolve
|
Save
|
Resolved specification
(pkid)
|
|
|
GSM.SmartIssue
|
Create
|
Specification
created (pkid)
|
Smart Issue
Request (pkid)
|
|
GSM.SmartIssue
|
Copy
|
Specification
copied (pkid)
|
New specification
created (pkid)
|
|
GSM.GlobalSuccession
|
Save
|
Host specification
(pkid)
|
Specification that
was replaced (pkid)
|
|
SCRM.Editor
|
Save
|
Specification
object (pkid)
|
|
|
SCRM.Clone
|
Create
|
Sourcing Approval
copied (pkid)
|
|
|
SCRM.Clone
|
Copy
|
Sourcing Approval
copied (pkid)
|
Sourcing Approval
created (pkid)
|
|
SCRM.Workflow.Transition
|
Workflow
|
Sourcing Approval
transitioned (pkid)
|
Workflow Step
(pkid)
|
|
SCRM.Workflow.Resolve
|
Workflow
|
Resolved specification
(pkid)
|
Workflow Step
(pkid)
|
|
SCRM.Workflow.Resolve
|
Save
|
Resolved specification
(pkid)
|
|
|
|
|
|
|
