Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
5 subscribers
Views
1560 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
This is just a small observation on the behavior of the LogReader function. Scen
chetany
A Score Level 1
over 8 years ago
This is just a small observation on the behavior of the LogReader function. Scenario: I want to get the details of the users who logged in the past 2 hours. Using the logReader plugin, I can use:
fn!readcsvlogpaging(
csvPath: "login-audit.csv",
startIndex:1,
batchSize:-1,
filterColumName:null,
filterOperator:null,
filterValue:null,
timestampColumnName:"Timestamp",
timestampStart: now()- fn!intervalds(2,0,0),
timestampEnd: now()
)
The above code will return me the Successful as well as Failed logins in the past 2 hours.
But, if I do not specify the "filterColumnName", "filterOperator" and "filterValue", it does not return any data.
When using keyword syntax, you have to specify them as null explicitly if you do not want to apply any filter on data coming from the log.
Also, you have to specify the keyword parameters in exactly the same order as in the plugin description. Otherwise you will get an error.
In...
OriginalPostID-210288
OriginalPostID-210288
Discussion posts and replies are publicly visible
Parents
0
Steven Miccile
Appian Employee
over 8 years ago
I do not believe custom functions accept keyword notation the way base product functions and rules do, meaning this is expected behavior.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Steven Miccile
Appian Employee
over 8 years ago
I do not believe custom functions accept keyword notation the way base product functions and rules do, meaning this is expected behavior.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data