Overview
This plug-in will traverse through the last 30 days of login files and return the date and time of a successful login. This is useful for removing access for users who are not using the system.
Key Features & Functionality
Returns date and time of the last successful login in the previous 30 days.
Hi, it is not working properly, if I execute 3 times the same rule, only with the getlastlogindatetime("XXX") with the same username I'm going to obtain 3 different answers:
First execution: null(Null)Second execution: "04/02/2024 11:58 AM"(Text)Fourth execution: "04/29/2024 12:26 PM"(Text)Why is this happening? It does not work with high availability?
Hi Pedro Simões - Does this plugin work for multiple instance setup ? We have a high availability environment,\.
There is an issue with this plug-in. A report was filed with Appian Marketplace
Summary:
Detailed explanation of the issue:
The plugin is not properly displaying the last time a user logged into Appian.
Example: If I login to Appian at 9am local time on January 8, 2024, then log out, wait 15 minutes and log back into Appian what I should see is that my last successful login was 9am but what’s being returned is 9:15am. This type of plugin is useful/needed to determine if someone other than the logged in user accessed Appian between 9am and 9:15am. Let’s say for example that I worked all day on Friday, January 5th and logged out at the end of the day, when I log back in on Monday morning, January 8, 2024, I should see that my last successful login was on Friday, January 5th. If I see a date value of January 6, 2024, that will lead me to believe someone logged in as me over the weekend.
Ah - good question - under the App Information card, if the plug-in is Appian-supported, the Cost will explicitly say: Cost = Free - Appian Supported. More detail in our FAQs here: https://community.appian.com/p/appmarket-faq#:~:text=How%20are%20Free%20Apps%20supported%3F
I will note this down as a UX area of opportunity.
Sure thing - though I do note that the "report an issue" email still says "open a support case" when the plug-in is an "Appian Supported plug-in" (which i assume this is, given the Author listed is AppianCo?), which left me a little unsure.
Mike Schmitt - would you mind submitting via the Feedback --> "Report an issue" button at the right side of the listing? That will be the most efficient way to get a response from the plug-in's author (which the AppMarket team will facilitate). Thanks!
Appian AppMarket - there is a bug in this plug-in. The returned timestamp uses the 24-hour format for the hour, but also includes the "AM/PM" string - so for instance it might return a value of "11/29/2023 15:06 PM", which is not actually a valid timestamp, and breaks the "toDatetime()" function. This should be fixed such that it passes back something that's more directly usable by designers, since using it for anything programmatic at the moment is pretty much impossible without implementing some painful work-around.
Originally reported in this post.
@pedro.simoes, We are facing similar issue, we have three servers for PROD environment but the function reading only log file from one server hence we are not able to see correct results.
Pedro Simões - Does this plugin work for multiple instance setup ? We have one instance on Dev and it works fine but in Pre and Pro its not giving us correct results as we have 3 pre app servers and 3 pro app servers .
Is there any fix for this plugin to work with more than one app server set up?