Get current object

Question

Here is my expression: 
 a!localVariables(
 /* Loop checks against passed in value of type to pull values
 from specific requirementActivity match */
 a!forEach(
 items: ri!requirement.requirementActivities, 
 expression: 
 if(contains(ri!activityType, fv!item.type),
 'type!{urn:com:appian:types:UW}UW-Requirement-Activity'(
 key: fv!item.key,
 type: fv!item.type,
 creatorId: fv!item.creatorId,
 creatorFullName: fv!item.creatorFullName,
 createdDate: fv!item.createdDate,
 commentText: fv!item.commentText
 ), 
 {}), 
 ),
), 
 activityType is Text Array

snippet of rule in play: 
 
 local!requirements: {
 a!forEach(
 items: local!requirementsResponse,
 expression: a!localVariables(
 local!receivedRequirementActivity: rule!UW_GetRequirementActivityByType(
 requirement: fv!item,
 activityType: "RECEIVED"
 ),
 local!waivedOrAcceptedRequirementActivity: rule!UW_GetRequirementActivityByType(
 requirement: fv!item,
 activityType: {
 "WAIVED",
 "ACCEPTED"
 }
 ),
 a!map(
 type: property(
 fv!item,
 "name",
 {}
 ),
 status: property(
 fv!item,
 "status",
 {}
 ),
 orderDate: property(
 fv!item,
 "createdTimestamp",
 {}
 ),
 orderRep: property(
 fv!item,
 "requestedBy",
 {}
 ),
 receiveDate: property(
 local!receivedRequirementActivity,
 "createdDate",
 {}
 ),
 receiveRep: property(
 local!receivedRequirementActivity,
 "creatorFullName",
 {}
 ),

It works great unless their are duplicate ActivityTypes - I need to return the current ActivityType and I'm rather new to Appian development and having a time sorting out how to handle this. What is currently happening is the fields: creatorFullName: fv!item.creatorFullName & createdDate: fv!item.createdDate in my table are populating every associated date and creator returned that's associated with the activityType. 
 I've been searching the docs and I'm just not really finding a direction to go. Any guidance would be greatly appreciated.

Peter Lewis · Accepted Answer

I'd suggest doing a few steps: 
 
 Move your queries up out of the a!forEach() for local!requirements into the top level and query all the requirement activity for all requirementResponses so that you're only running one query instead of one for each response. This should improve the performance by reducing the number of queries executed. 
 Update your local!requirementsResponse within the a!forEach() to return the requirements that relate to the given response. I typically do this using the displayvalue() function because it allows you to match an item from your response to your activity list. 
 At this point you're still likely returning a list of values for each response and you need to return only the most recent. I'd use the index() function to return only the first item from each list to ensure you only display one value. 
 
 I know that's a pretty high level, but hopefully that at least can get you started - of course feel free to ask any questions as you're going! 
 One other thing to mention - my suggestion was primarily for keeping the same data model as you currently have. If you are using something like synced records it would actually be much easier to do this because there is a function for a!relatedRecordData() that lets you directly define the properties for your activites. Some app developers also prefer to set up this logic in a database view, because you can use any of the functions that SQL offers to get your data in the format you need.

Marcel Paradies · Answer

It appears your issue is that for one of the items in the row you get an array of dates received. You might want to modify the way you build your list of local!requirements to account for that. If you do not need the additional data (you mention that you want to show the most recent data), you might want to modify it as early as GetRequirementsByCaseId to throw away older actions taken. 
 As a sidenote: Can I suggest you analyse your interface for performance some time down the line? Assuming "GetRequirementActivityByType" queries data from somewhere, you'd end up with n*2 DB queries to load the grid, which can slow things down a lot.

Get current object

Top Replies