Appian Usage Insights

Overview

Gain insights into your Appian usage with an application suite specifically designed to cater for complex environment topologies and heterogenous license contracts.

Key Features & Functionality

With ‘Appian Usage Insights’:

  • Model your license contracts in the application through configuration only - no additional development required!
  • Cater for Cloud, self-managed or a mix of installation topologies.
  • Designed with the enterprise in mind, support large numbers of Appian environments, user accounts and keep track of license consumption over time.
  • Model your internal license usage using license pools mapped to user-definable business entities.
  • Visualize usage the way you want to:
    • Usage by business entity.
    • Usage by license type.
    • License pool membership.
    • License pool logins.
    • License pool membership (which user is in which license pool and, ultimately, which one consumes an actual license).
    • Logins by user (over time).
    • Capacity planning (allocated license count over time).

For more information, see https://community.appian.com/w/the-appian-playbook/2198/appian-usage-insights-faqs

Usage of this application does not permit your organization to exceed its licensed usage requirements. Your organization is required to maintain compliance with your licensing terms, and report any non-compliance to Appian per the terms of your organization’s contract with Appian.

Anonymous
  • Hi,

    Could you please confirm whether this tool is compatible with Appian version 25.1? The documentation mentions compatibility with version 24.3.

    However, I installed it on our DEV environment running version 25.1 and encountered the following issues:

    Issue #1: Blank audited_login.csv File

    • The audited_login.csv file in the data extraction ZIP package was blank.
    • As a result, the process model "ALR Process Data Package" failed with the following error:

    Error Details:

    • Problem: An error occurred while executing an Activity Class.
    • Details: The identifiers parameter cannot be null or empty.
    • Recommended Action: Review and correct the activity class, then resume the process.
    • Priority: High

    To address this, I modified the process model to handle null lists. 

    Issue #2: Foreign Key Constraint Error in ALR Analysis Process

    • When attempting to run "Run Analysis" from the Collection Run tab, the ALR Analysis process fails.

    Error Details:

    • Issue: Error in the task "Execute Stored Procedure ALR_SP_POPULATE_USER_POTENTIAL_LICENSE_POOL".
    • Problem: An error occurred while executing an Activity Class.
    • Details:
      (conn=401006) Cannot add or update a child row: a foreign key constraint fails (LicenseTracking.ALR_USER_POTENTIAL_LICENSE_POOL, CONSTRAINT 'ALR_USER_POTENTIAL_LICENSE_POOL_ENTITY_LICENSE_POOL_ID_FK' FOREIGN KEY ('ENTITY_LICENSE_POOL_ID') REFERENCES 'ALR_ENTITY_LICENSE_POOL' ('ENTITY_LICENSE_POOL_ID'))
    • Recommended Action: Examine and update the activity class to ensure valid foreign key references, then resume the process.
    • Priority: High

    FYI, backend database: MySQL on Appian Cloud.

    I’m not sure how to resolve these issues and would appreciate your assistance. 

  • hello, i've seen that it requires the execute stored procedure plugin ( inside the documentation) ... alas this one is flagged as obsolete. 

    Could you please upgrade it to avoid this dependency ? 

    Thanks in advance 

  • The information section says it's compatible with 24.3 but I'm not able to import the Appian License Reporting app without upgrading to 25.1

  • v2.0.0 Release Notes
    • Support for Oracle DB scripts (ORA_Application_License_Reporting.sql, ORA_ALRDC_Data_Collector.sql).
  • v2.0.0 Release Notes
    • Plugin:
    •  Bug fix related to collecting group membership to retrieve users starting from index 0.
    • Collector app:
    • Changed name to Appian License Reporting Data Collector (ALRDC)
    • Moved most data types to Synced Records from CDTs to align with Appian's modern design patterns.
    • Process models that required sync nodes were also updated to sync data with stored procedure calls.
    • As such, constants connected to Data Store Entities have been removed.
    • Reporting app:
    • Changed name to Appian License Reporting (ALR)
    • Moved most data types to Synced Records from CDTs to align with Appian's modern design patterns.
    • Process models that required sync nodes were also updated to sync data with stored procedure calls.
    • As such, numerous constants connected to Data Store Entities have been removed.
  • v1.2.1 Release Notes
    • Bug fix related to collecting group membership to retrieve users starting from index 0.
  • We are planning to install this plugin in our DEV environment. Can you please provide to details steps to install this in our dev environment?

  • Hi team,

    We are planning to use this app for collecting user activity. I have two questions about this app

    1. If we have HA setup with multiple appian nodes, will the collector collect users and login activity from all three of them?

    2. One observation I have through one of our recent collection, the number of users in LMA_ENVIRONMENT_USER table are one less than the actual active users in the environment. Anyone seen this type of issue? the user missing is active appian user since 2022, but i dont see any login done by the user. 

  • Hi team,

    We are trying to install this app on Appian 22.4 with MSSQL database. We were able to install collection app, also we have setup the database for Reporting app. But while importing the Reporting app, we are getting below error:

    processModel 0002e3e2-7e00-8000-5369-544d98544d98 "LMA Process Data Package": An error occurred while creating processModel [uuid=0002e3e2-7e00-8000-5369-544d98544d98]: com.appiancorp.process.validation.ValidationException: Process Model is not valid. Invalid Activity Class Schema ID (APNX-1-4071-007)

    We have tried this with Excel Tools 2.5.0 version. During inspection, it does not show any error but after importing it gives error.

  • Hi,

    It's a good suggestion to be able to optionally exclude service account logins. I'm glad you've found a solution to this that works for you (and thanks for sharing the details of your solution). There are no current plans to release a new version of this plugin, but I've added this feature to the backlog as I think if we were to release a new version this would be a good addition.

    Regards,

    David