The example provided in this document is provided “as-is” to the user and assumes that the user:
When a change journal entry is generated the following information is about the entry is available, which is visible through Strategy Desktop:
The following code demonstrates how to access the Change Journal Entries programmatically:
Sample Code/Error
Private Sub cmdGetJournalEntries_Click()
Set oObjSource = MySession.Component(DssRoleObjectSource)
Dim cjSearch As IDSSChangeJournalSearch
Set cjSearch = oObjSource.NewObject(DssTypeChangeJournalSearch)
cjSearch.TransactionTypes.Add (DssTransactionCollectGarbage)
cjSearch.Flags = DssChangeJournalSearchNotTransactionTypes
Dim list As IDSSChangeJournalList
Set list = oObjSource.SearchChangeJournal(cjSearch)
Dim entry As IDSSChangeJournalEntry
Dim objectList As IDSSChangeJournalObjectList
Dim objectEntry As IDSSChangeJournalObjectEntry
Dim num As Integer
num = 1
strOut (list.Count)
For Each entry In list
Set objectList = entry.Objects
For Each objectEntry In objectList
strOut ("**********" & num & "************")
strOut ("Object Name: " & objectEntry.ObjectReference.Name)
strOut ("Object Type: " & objectEntry.ObjectReference.Type) 'EnumDSSObjectType
strOut ("User Name: " & entry.UserName)
strOut ("Transaction Timestamp: " & entry.TransactionTimestamp)
strOut ("Transaction Type: " & entry.TransactionType) 'EnumDSSTransactionType
strOut ("Transaction Source: " & entry.TransactionSource) 'EnumDSSApplicationType
strOut ("Project ID: " & entry.TransactionProjectID)
strOut ("User Comments: " & objectEntry.UserComments(1)) 'multiple comments can be checked here
strOut ("Object ID: " & objectEntry.ObjectReference.ID)
strOut ("Machine Name: " & entry.Machine)
strOut ("Change Type: " & objectEntry.ChangeType) 'EnumDSSChangeType
strOut ("Transaction ID: " & entry.TransactionID)
strOut ("Session ID: " & entry.SessionID)
num = num + 1
Next
Next
End Sub
ADDITIONAL INFORMATION:
The Strategy SDK allows you to customize the standard Strategy Web interface, and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy Web products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy Web architecture or the process of customizing Strategy Web, please refer to Strategy Developer Zone (https://resource.microstrategy.com/msdz/).
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@microstrategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at https://www.microstrategy.com/en/support/contact-support.
CUSTOMIZATION WARNING:
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.
