Hi ​@kpillai ,

thank you for your question. AFAIK, the author of the item is not a property that can be directly queried. However, you can query the history of the item and the latest record from the history will be the author. You can use for example this API query for one rule (but it can be used for all rules as well):

query GetEntityHistoryListing_rule($skip: Int, $size: Int, $gid: GID!) {
  rule(gid: $gid) {
    nodePath
    history(skip: $skip, size: $size) {
      edges {
        node {
          _from {
            id
            timestamp
            author {
              numericalIdentifier
              ... on Person {
                username
                firstName
                lastName
                email
                userId
                __typename
              }
              ... on Service {
                module
                instanceId
                __typename
              }
              __typename
            }
            __typename
          }
          _to {
            id
            timestamp
            author {
              numericalIdentifier
              ... on Person {
                username
                firstName
                lastName
                email
                userId
                __typename
              }
              ... on Service {
                module
                instanceId
                __typename
              }
              __typename
            }
            __typename
          } 
        }
      }
      pageInfo {
        hasNextPage
        endCursor
        __typename
      }
      totalCount
      __typename
    }
    __typename
  }
  }

With variables:

{
  "size": 10,
  "gid": "36ed325c-0000-7000-0000-0000003afc15",
  "skip": 0
}

The record with the lowest history id is the first occurance and the user associated with this change will be the original author. Once you have those records for all rules, you can group by the users and count the unique rules.

Another option is to use the Audit module, however, you would have to always obtain all the records, and customers usually use some retention period for the audit records.

I will also ask around internally if we have a better way to get to this information or at least use some ordering in the query and limiting to just that first history record, which could make the API easier, and I will post it here if I find anything.

Let me know if this helps or if you need more information or assistance.

Kind regards,

Anna

Hi ​@anna.spakova  Thank you very much. I tried with playground and it worked but could not retrieve from JSON call in ONE Desktop Plan. I want it to be exported in excel or csv

Could you please share the PLAN? ​@anna.spakova 

Hi ​@kpillai ,

I don’t have a plan scpecifically for this query and it would take me some time to prepare it, but you can inspire for example here: 

The article explains how to parse more complex responses and it contains an example plan as well.

Let me know if this is sufficient.

Kind regards,

Anna

Hi ​@anna.spakova  I am able to get an export via desktop but can do only for one rule. I want to export the owner for all the rules.

Hi ​@kpillai ,

for all rules the query is similar:

query GetEntityHistoryListing_rule($skip: Int, $size: Int) {
  rules(versionSelector: {draftVersion: true}) {
    edges{
      node{
        history(skip: $skip, size: $size) {
      edges {
        node {
          _from {
            id
            timestamp
            author {
              numericalIdentifier
              ... on Person {
                username
                firstName
                lastName
                email
                userId
                __typename
              }
              ... on Service {
                module
                instanceId
                __typename
              }
              __typename
            }
            __typename
          }
          _to {
            id
            timestamp
            author {
              numericalIdentifier
              ... on Person {
                username
                firstName
                lastName
                email
                userId
                __typename
              }
              ... on Service {
                module
                instanceId
                __typename
              }
              __typename
            }
            __typename
          } 
        }
      }
      pageInfo {
        hasNextPage
        endCursor
        __typename
      }
      totalCount
      __typename
    }
    __typename
  }
  }
 }
}

You can remove the gid from the variables, as it is not needed anymore.

Kind regards,

Anna