Discuss Appian ACD201 Exam Topic 2 Question 16

You're designing a custom component rule!pagingComponent() to page through a list of items. The component must display the current page numbers being shown, as well as the total number of items. Users should be able to click arrows to increase or decrease the pagination.

Review the following:

Which two patterns should be used when calling the component in this scenario? (Choose two.)

APassing into the rule input totalCount of rule!pagingComponent() the value: local!query.totalCount where local!query is returning a dataSubset and returnTotalCount = 'True'.

BA rule input ri!pagingInfo on rule!pagingComponent() with a local variable of the same name in the main interface with an initial value. When the arrows are clicked, this updates the value of the local variable in the main interface.

CA local variable local!totalCount calculated using count(local!query), which is passed into rule!pagingComponent() via a rule input. The data type of local!query is a list of record or Custom Data Type (CDT).

DA local variable local!pagingInfo inside rule!pagingComponent() with an initial value. When the arrows are clicked, this updates the value of the local variable.

Suggested Answer: A, B

Passing local!query.totalCount (from a dataSubset with returnTotalCount: true) into a rule input allows rule!pagingComponent() to accurately display total items for pagination.

Managing paging state (such as ri!pagingInfo) as a local variable in the main interface and updating it when arrows are clicked ensures that pagination is controlled centrally, maintaining state across the UI and allowing the component to function as intended.

Get Premium ACD201 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

17 comments · newest first

Brynn 2 months ago

I’m leaning towards A and B as well. They cover all bases for pagination.

Willow 2 months ago

Yeah, D doesn’t really allow for dynamic updates. A and B are more flexible.

Gerald 2 months ago

D seems less effective. Updating a local variable inside the component feels limiting.

Kiley 2 months ago

True, but C ensures we have the right data type. It’s worth considering.

Brynn 2 months ago

C could work, but it feels a bit more complex than necessary.

Willow 2 months ago

B makes sense too. Keeping the local variable updated is key for user experience.

Gerald 3 months ago

I agree with A. It’s crucial to get the total count right.

Kiley 3 months ago

I think A and B are the best choices. They ensure accurate total count and update the interface smoothly.

Juan 3 months ago

Surprised that totalCount isn't just a simple input!

Hermila 3 months ago

D) seems a bit off, why not just use a local variable outside?

Dell 3 months ago

C) sounds good, but is it really necessary to use count()?

Walton 3 months ago

I think B) makes more sense for handling the clicks.

Kristine 4 months ago

A) is definitely the way to go for total count!

Albina 4 months ago

I'm a bit confused about option D. It mentions a local variable inside the component, but I thought we needed to manage state in the main interface. Is that right?

Mozell 4 months ago

I think option C could work too, especially since we need to calculate the total count. But I'm not clear on whether local!query should always be a list or if it can be something else.

Melodie 4 months ago

I feel like option B is similar to a practice question we did about updating local variables. It seems like a good way to handle the arrows for pagination.

Paris 4 months ago

I remember we discussed using local!query.totalCount for pagination, so I think option A makes sense. But I'm not entirely sure about the returnTotalCount part.

Appian ACD201 Exam - Topic 2 Question 16 Discussion