App creation config: Web-view configurations

At a bot level, different views are shown to the user:
1. My-tasks: The user can view all the tasks pending on them. These tasks can be input or approval tasks.
2. My-items: The user can view the specific requests (against unique request IDs), with the logic:
  1. The user has raised the request itself
  2. The user was a participant for a request. For example, if a user is a L1 approval for a request, then post task completion, the request would reflect under my-items
Information points shown to the user under my-items:
1. Participants:
  1. Requested by: The user who has requested/initiated the request
  2. Initiated on behalf of: The user for whom the request has been initiated/requested
2. Progress Path:
  1. The user can view the progress of the request, and view step-wise progress of a request
3. Comments:
  1. The user can render a comments section
  2. A user can view historic comments & also add the comments
  3. A comment is tagged to a step. If a request is in progress, then its tagged to current in progress steps
4. Tags:
  1. The user can view the tags which are associated with a request.
  2. Tags are created by admin while creating an application.
  3. Tags can assist user in bifurcating requests.
5. Form:
  1. The user can view the forms in read-only mode.
  2. These are the forms which the user would have filled or viewed under different tasks that the user would have completed for a request
Web-view configurations
1. A workflow designer can choose to disable the information points under my-items, for a particular application.
2. Workflow designer can choose to disable the information related to:
  1. Participants
  2. Progress Path
  3. Comments
  4. Tag

Updated about 2 months ago