Hyperlinks on form while in task preview mode

Hi,

We have an approval task that is assigned to a group, so when a member opens the task initially, it is in task preview mode.

Which means that most of the form is read-only... Except for hyperlinks, which we use for selection options (card layout), adding to a grid (Add New link), editing a grid row (master-detail pattern), deleting a grid row.

This means that the not-yet-accepted task can be interacted with and can lead to modification of data in the task, all prior to acceptance.

Is there a way to avoid this? Is there a task property (or similar) that I can use in order to determine how to display the form while it's in preview mode?

Thanks,

Mike

  Discussion posts and replies are publicly visible

Parents
  • Hi Mike,

    As per the current Appian Limitation, the hyperlinks would be active before the task is accepted.

    Few approaches to restrict the access is

    (1) Use Record based approach instead of Task based. The Assignees can be configured as part of Related Action Visibility.

    (2) Fetch Task report to get the assignee who has accepted the task. And depending on the status of the task, condition visibility (if-else) of hyperlinks can be configured. But this approach might cause performance issue.

    (3) Use Two User input tasks - UI1 and UI2 with Activity Chaining. In UI1, a simple paragraph field and a button is sufficient and in UI2, the required form should be configured. But in the approach an extra UI needs to be added.

    Please confirm if any of the approaches were useful or please specify if any other approach followed.

    Thanks,
    Farnaz
Reply
  • Hi Mike,

    As per the current Appian Limitation, the hyperlinks would be active before the task is accepted.

    Few approaches to restrict the access is

    (1) Use Record based approach instead of Task based. The Assignees can be configured as part of Related Action Visibility.

    (2) Fetch Task report to get the assignee who has accepted the task. And depending on the status of the task, condition visibility (if-else) of hyperlinks can be configured. But this approach might cause performance issue.

    (3) Use Two User input tasks - UI1 and UI2 with Activity Chaining. In UI1, a simple paragraph field and a button is sufficient and in UI2, the required form should be configured. But in the approach an extra UI needs to be added.

    Please confirm if any of the approaches were useful or please specify if any other approach followed.

    Thanks,
    Farnaz
Children
No Data