hello
I'm on 25.1 and I have the below Use Case:
I need to display on a read-only grid a short list (5 or 10 items at least) of last opened Record of a given Record Type.
basically I need to store on a table the interactions over a Record List (every time a user clicks on a Record Link) in order to display the "last opened records" as a table
I was thinking on replacing the Record Link with a startProcessLink which stores this transaction on a table (recordId, user, timestamp) and then open the Record Summary as a task, but this has several disadvantages:
- the record page has several tabs (summary, attachments, other related data ....) which might requires additional effort to refactor
- transforming the record interaction into processes might have performance issues
any thoughts/suggestion about how to deal with this?
thanks
Discussion posts and replies are publicly visible
francescop586 said:last opened
How exactly is this defined? I assume that users do not just open a record for fun, but they interact with it. Then you can store the necessary data in the actions they start.
The idea using a startProcessLink will not get you anywhere.
As a last resort, there is a log file holding this information: docs.appian.com/.../Logging.html
users open a record not necessarily to execute actions, but even just to review data without executing any interactions; as an alternative, I was thinking on a specific action, like "add to favorite" in order to let the user select/unselect the records needed to see in such shortlist (the disadvantage is that this still requires a specific user interaction, and I wanted to have this totally transparent for the user)
the log file looks to be exactly what I need, filtering by "view Record Dashboard" action and by Record Type.
Do you happen to know how to extract (ie. on daily basis) the log (without manually jumping in System logs and downloading) and store on a dedicated record list? (we run on Appian Cloud)
I would try to discuss with business for what purpose they want this list. A subscription mechanism might be a smart idea to allow people manage their work load.
Log file reader plugin: community.appian.com/.../log-reader
Similar to what Stefan has said, this requirement is difficult to deliver. Log files are accessible as Stefan has pointed out that may provide some context but having has to consider requirements like this in the past they may not provide what you require.
As a suggestion, consider that when the record page loads, display on a certain % of the record data. To do more with the record, they would need to click a record action, which can then invoke the process to write the data to a table or column on the record, to further interact with the record, displaying the remaining data and then the other actions.
Please note, this will open a box of further requirements technically and on the business side, and is something I would avoid, but at least provides an option to proceed further if you really have to.
This is possible using a Stored Procedure with the right design pattern, and otherwise-OOTB functionality. It's not an "officially supported" behavior though, but it works fine.