Hi Saurav, apologies for the delay. Yes, you can create a table or list of tasks in Nintex Apps.
Here’s a template that shows how to set it up. You can use the same models setup, but different components based on the desired UI: https://gallery.nintex.com/t/nactaskmanagement

I HAVE one more problem i want to show data before user accept or reject i understand your project but sir how to show data of means which data that trigger this workflow i want to show that data and based on that data user can able to approve or reject any way to do that

Hi Saurav, I responded to your question in the related thread: 

Hi ​@annajosephine , thank you for sharing the templates above.

I have set up some test pages and want to show all active tasks for the logged in user. However there seems to be a hard coded limit to the query of 20. I have tried to update it in the xml to 100, but it is still not bringing back all the active tasks, it’s only showing the latest ones. 

I have set up parameter conditions as per attached.

Can you please advise how to increase the query limit to 100?

​@FranF Are you using the task object from the workflow connector? I’m not having any trouble returning more than 20 results.

I’m wondering if you're doing something a bit different though… since that model takes conditions as parameters and your screenshot is different.

Hi ​@mkaastra, thanks.

Yes using the task object from the workflow connector. I’ve just set up another very basic one, that should bring back all active tasks regardless of assigned to, but this is only showing 15.

Screenshots attached.

Maybe it’s an issue at the Nintex Workflow Tenant end? Let me know if you recommend logging a job to resolve.

Hello ​@FranF,

Im working to support Mike and Anna on this one a bit. The List Tasks Api will only return the last 14 days of tasks if the “from” parameter is not specified. Can you try setting the “from” parameter and see if you’re able to pull back the list of tasks you’re expecting to see? Here’s a link to the documentation, and a screenshot with an example that should help show what this looks like:

Hope this helps!

Hi ​@Clark_Cregg , thank you that worked!

Just while I have you, I still have a couple of problems with this page:

1. Is it possible to sort the results on one of the fields?
   I want to sort on Due Date so that the tasks that are due soon or are overdue appear at the top of the list. The ‘fields to order records by’ doesn’t appear as an option like the Nintex table models do.
2. See below screenshots of the use case and model set up. 
   In summary, I want the user to be able to click a button to open the task in Nintex Workflow. Like SS_1 and SS_2 below.
   I set up a dependent model for taskAssignments to get the form url. It is working for most records. However on some records the form URL is not coming through.
   Can you please let me know what I am doing wrong in the set up? 
   
   Thank you

Hello!

Glad adding that parameter sorted out the original issue. In regards to your follow ups:

1. Im double checking internally with our team that manages the APIs to see if there’s an order by or sort option of some sort. I’ll follow up once I confirm with more certainty!
2. I believe your configuration seems correct. Im not sure about the details of the task assignments in your example, but if there is not a form associated with the task (like in an express approval scenario) then it will not have a link to a form.

Thanks ​@Clark_Cregg much appreciated.

Regarding 2. thank you, that was a penny drop moment. Yes - you are right, the ones with no URL are all express approval.

Thanks for your patience!

I was able to confirm there is not currently API support for ordering/sorting on the list tasks endpoint. However, I’ve raised that with the PM for evaluation for an improvement in the future.

In the meantime, I’ve got an option for how to sort using Apps. I’ve built a sample page that shows this (XML below). I’ll outline the steps below as well/

1. Add a Page event to the page component.
   • Select the page component in the index and at the bottom of the properties, under interactions, add an event and select “Page: Rendered”

2. Deselect “Query on page load” in your Task model

3. Add an action flow that queries the task model (using the query model action) and then sorts the model (using the “Sort Model” action). I selected the Due Date field and descending as the options in my example for the sort.

   • Note: I added some block UI and unblock UI actions to help the experience feel more cohesive in my example.

Its important to note that this is client side sorting, so its only sorting data thats returned in the query and it could be slow with large volumes of data.

<skuid__page unsavedchangeswarning="yes" personalizationmode="server" theme="Aurora" showsidebar="false" showheader="false">
	<models>
		<model id="Task" query="false" createrowifnonefound="false" datasource="ntx__Automation" sobject="task" rest-operations="query">
			<fields>
				<field id="description"/>
				<field id="id"/>
				<field id="name"/>
				<field id="status"/>
				<field id="subject"/>
				<field id="workflowId"/>
				<field id="workflowInstanceId"/>
				<field id="workflowName"/>
				<field id="dueDate"/>
				<field id="taskAssignments" type="array">
					<fields>
						<field id="id"/>
						<field id="urls.formUrl"/>
					</fields>
					<conditions>
						<class id="parameter"/>
						<class id="client"/>
					</conditions>
				</field>
			</fields>
			<conditions>
				<class id="parameter"/>
				<class id="client"/>
			</conditions>
			<actions/>
			<parameters>
				<request id="query">
					<parameter type="query" name="status" valuesource="fieldvalue" value="active"/>
					<parameter type="query" name="from" valuesource="fieldvalue" value="2025-01-01"/>
				</request>
				<request id="insert"/>
				<request id="update"/>
				<request id="delete"/>
			</parameters>
		</model>
		<dependentmodel id="Task_taskAssignments" principalmodel="Task" sourcefield="taskAssignments" sobject="task.taskAssignments">
			<conditions/>
		</dependentmodel>
	</models>
	<components>
		<skuid__table allowColumnFreezing="dragDrop" model="Task_taskAssignments" allowHTML="false" uniqueId="sk-3DJv-18455" mode="read" title="Task Assignment">
			<fields>
				<field id="urls.formUrl" uniqueId="fi-3DJz-37447"/>
				<field id="$Parent.dueDate" uniqueId="fi-3DJz-37448"/>
				<field id="$Parent.description" uniqueId="fi-3DJz-37449"/>
			</fields>
			<filtering enableSearch="false"/>
			<rowActions/>
			<massActions/>
			<exportProperties useTableColumns="true"/>
			<sorting enable="false"/>
			<interactions/>
			<renderConditions/>
			<styleVariantConditions/>
			<styles>
				<spacing top="4" right="4" bottom="4" left="4"/>
			</styles>
		</skuid__table>
	</components>
	<resources>
		<labels/>
		<javascript/>
		<actionsequences>
			<actionsequence reusable="true" id="af-3DKA-93418" label="Page Load">
				<actions>
					<action type="blockUI" message="Loading..." showPlaceholder="true"/>
					<action type="requeryModels" behavior="standard">
						<models>
							<model>Task</model>
						</models>
						<onerroractions>
							<action type="blockUI" timeout="3000" message="Error loading data..."/>
						</onerroractions>
					</action>
					<action type="sortModel" model="Task" client-side="true" method="desc" field="dueDate"/>
					<action type="unblockUI"/>
					<parameters/>
				</actions>
				<inputs/>
				<events>
					<event event-scope="component" event-name="page.rendered"/>
				</events>
			</actionsequence>
		</actionsequences>
		<statements/>
	</resources>
	<background/>
	<interactions/>
	<surfaces/>
</skuid__page>

Hope this helps get you unblocked and moving forward!

Thanks ​@Clark_Cregg , that’s a good idea, and thank you for the xml.

However I am still having some trouble.

In your xml the due date sorts by ‘Descending’. I updated it to ‘Ascending’ so that anything due today or overdue appears at the top. However the data is still sorting by descending in the UI.

Does this happen for you as well?