Appian Usage Insights

Is any one keeping this upto date at Appian?

Hi,

We are using this plugin on Appian 25.3 and the Collect Audited Logins smart service in V1.2.2 does not work. It runs without an error but produces an empty document. We were previously using this functionality in V1.2.0 and it worked fine.

Is this something you could look at please?

Thanks,

Johnny

• Support for Oracle DB scripts (ORA_Application_License_Reporting.sql, ORA_ALRDC_Data_Collector.sql).

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

• Support for Oracle DB scripts (ORA_Application_License_Reporting.sql, ORA_ALRDC_Data_Collector.sql).

• 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.

• 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?