Jump to content

bernie

Hornbill Users
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bernie

  • Rank
    Member
  1. Hi @Victor, the reason I logged it there is because the Id is returned from an API request and I'm curious as to where via the API I can query this Id. I only mentioned the system logs because that's where I found an entry in the 'EspApiTransactions' log that contained the auditTransactionId and details of the change I made to an asset. From that I could determine a possible API call. It is merely a general enquiry. As I use the API more, I'm looking at what options I have for auditing. For example, if changes are being made the audit Ids could be logged, which could then be referre
  2. A number of the API methods return 'auditTransactionId', such as 'data::entityDeleteRecord'. I'm curious as to where if at all you can query these. I've had a look at 'system::getLogFileRecords'. If I query the 'EspApiTransactions' log I can see the Transaction Id in the message and the details of what was carried out. There is an input parameter 'filterTransactionId', but this has to be an 'xs:unsignedLong' value. I can't see any other log that might contain a TransactionId column, so not sure where that input parameter could be used.
  3. OK, I've finally had time to look into this further and I've now got the dependency working. Following what the WUI does when it comes to assigning dependencies using 'data::entityAddRecord' with 'ConfigurationItemsDependency' I'm able to add dependencies via the API. A similar configuration can be used to assign the impact using 'ConfigurationItemsImpact'.
  4. Thanks. In the meantime, I've got a work around, which is to use the .net option DateTime.ToLocalTime, which can (so far) be applied to all dates being returned.
  5. darn it, somehow it posted whilst I was still typing, and it wouldn't allow me to edit it Anyhoo, here's the full post: British summer is here (apparently), and now that I'm working on code that relies on dates and times of change requests I've noticed that different formats are being shown depending on what I query. E.g. If I query a request using 'apps/com.hornbill.servicemanager/Requests' - smGetRequests' I get: h_datelastmodified : 2020-04-01T08:17:49.000Z If I query an asset using 'data - entityBrowseRecords2' I get: h_last_updated :
  6. British summer is here (apparently), and now that I'm working on code that relies on dates and times of change requests I've noticed that different formats are being shown depending on what I query. E.g. If I query a request using '' I get:
  7. Hi ArmandoDM At the moment I'm looking at the possibilities of linking: Asset -> Asset Asset -> Request Asset -> Service Whilst investigating the UI activity of these processes I can see that Asset -> Asset sets the relationship type as '1' and '1' (left and right). With Asset -> Request the left relationship is 'request'. When you link an asset from within a request via the UI the reltypes (left and right) are set to '-'. I know that when you use the UI there are no options to specify the relationship. My assumption is that depending on wher
  8. Hi Steve, Thanks for the response. I've now found I can query these using 'appOptionGet'. One thing though, upon experimenting with the relationship types it appears I can actually supply anything, whether it's a potentially valid array integer (e.g. '0') or the name 'Connected to', and even something that doesn't actually exist. The linking still works (no errors) but there doesn't appear to be any difference to how the link appears (using launch explorer). Should I see a difference in how the links appear or does this relationship type information exist elsewhere? T
  9. I'm using the linkAsset API call to (yup you guessed it) link entities. This works well, but I want to be able to query and validate the possible values for the following parameters: leftEntityType xs:string required once The entity type of the first entity to be linked. (Asset, Request etc) leftRelType xs:string optional The relationship type of the first entity to be linked. (Connected to, Installed On etc) rightEntityType xs:string required once The
  10. For me the API is my best friend. Using the entityUpdateRecord, individual fields can be changed. Details of this can be found here: https://<ZONE>api.hornbill.com/<YOUR HORNBILL INSTANCE>/xmlmc/data/?op=entityUpdateRecord I.e. Use your existing hornbill URL (FQDN and Instance) and add '/xmlmc/data/?op=entityUpdateRecord' to the end
  11. I've seen some posts regarding tags for requests. It would be nice to have tags for assets too. Just like adding tags to a new topic in this forum, it would allow me to sync tagging currently used for deployed resources.
×
×
  • Create New...