How to create a Task Report in SAIL

@anilkumark Hi, here goes the pseudo-code as desired by you

Step - 1: Create a grid that queries portal report and surfaces the tasks. Documentation at https://forum.appian.com/suite/help/7.9/Task_Report_Tutorial.html should guide you in creating the respective grid. Thereafter you need to make a slight change so that the rows are selectable and the identifiers represent task ids.

Step - 2: Build a process model which takes a set of task ids (Number - Integer (Multiple)) and task assignees (User or Group (Multiple)) as inputs. The process should be able to re-assign the tasks (by using their corresponding task identifiers) to the User or Group array. Use the 'Reassign Task Smart Service' smart service at https://forum.appian.com/suite/tempo/records/type/components/item/i4BCLGOdlMUpdGVqT-RV7oRg74uEGJO5CD7RuGZM2pRXQUsb9JpSFOaxCwmf7sv/view/summary to reassign the tasks.

Step - 3: In the interface which you have the task report (created in Step - 1), trigger the process model (For instance, by clicking the 'Reassign' button added below the Task Report) created in the Step - 2 by using the function fn!startprocesswrite at https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5yQeCToV_iK9c-uZFaHQndbxbAQOV2CNBg/view/summary and make sure that selected task ids and the newly chosen task assignees are sent properly.

Note: The approach I have specified works if the newly chosen task assignees are common for all the chosen task ids. But you can extend the use case in such a way that each selected task id will have its own task assignees. For this, you need to make changes in the interface (so that each task will have the capacity to accommodate the new task assignees) and also finally construct a multiple cdt which maintains a task id and its corresponding task assignees.

In my opinion there isn't a need to work around because we can perfectly replicate the Portal Report's Task Reassign functionality by following the above (or a similar one with changes) approach.

Just to clarify one thing, the functionality which you build here doesn't need to be necessarily associated with a Task Report because you are just creating a Paging Grid component and it's up to you re where to place it, which could be a Tempo Report or Task Report or Record View or Form etc.

@anilkumark Hi, here goes the pseudo-code as desired by you

Step - 1: Create a grid that queries portal report and surfaces the tasks. Documentation at https://forum.appian.com/suite/help/7.9/Task_Report_Tutorial.html should guide you in creating the respective grid. Thereafter you need to make a slight change so that the rows are selectable and the identifiers represent task ids.

Step - 2: Build a process model which takes a set of task ids (Number - Integer (Multiple)) and task assignees (User or Group (Multiple)) as inputs. The process should be able to re-assign the tasks (by using their corresponding task identifiers) to the User or Group array. Use the 'Reassign Task Smart Service' smart service at https://forum.appian.com/suite/tempo/records/type/components/item/i4BCLGOdlMUpdGVqT-RV7oRg74uEGJO5CD7RuGZM2pRXQUsb9JpSFOaxCwmf7sv/view/summary to reassign the tasks.

Step - 3: In the interface which you have the task report (created in Step - 1), trigger the process model (For instance, by clicking the 'Reassign' button added below the Task Report) created in the Step - 2 by using the function fn!startprocesswrite at https://forum.appian.com/suite/tempo/records/type/components/item/i8BCLGOdlMUpdGVqT-RV7oRg74uEGJO5yQeCToV_iK9c-uZFaHQndbxbAQOV2CNBg/view/summary and make sure that selected task ids and the newly chosen task assignees are sent properly.

Note: The approach I have specified works if the newly chosen task assignees are common for all the chosen task ids. But you can extend the use case in such a way that each selected task id will have its own task assignees. For this, you need to make changes in the interface (so that each task will have the capacity to accommodate the new task assignees) and also finally construct a multiple cdt which maintains a task id and its corresponding task assignees.

In my opinion there isn't a need to work around because we can perfectly replicate the Portal Report's Task Reassign functionality by following the above (or a similar one with changes) approach.

Just to clarify one thing, the functionality which you build here doesn't need to be necessarily associated with a Task Report because you are just creating a Paging Grid component and it's up to you re where to place it, which could be a Tempo Report or Task Report or Record View or Form etc.