Document Management SystemProject Type: software

Document Management System

Uploaded image for project: 'Document Management System'
  1. Document Management System
  2. DMS-43

Create chain of approval users

    Details

    • Type: New Feature
    • Status: To Do
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Multiple Signer
    • Labels:

      Description

      Overview:

      Allow DMS user the ability to create a chain of users (workflow) in which a form will be sent so that each subsequent user can approve or decline a document.

      Entry Criteria:

      1. User enters DMS platform via link or consuming application.
      2. User navigates to create an approval workflow

      Acceptance Criteria:

      1. If I am a DMS user creating an approval workflow, I can enter in static people that should approve a document so that is go to specific people.
      2. If I am a DMS user creating an approval workflow, I can use a hierarchy to dynamically pull in approvers (ie. hiring manager to be pull in from ATS requisition).
      3. If I am a DMS user creating an approval workflow, I can save the workflow to be able to use when I have a document that needs approval.
      4. If I am a DMS user creating an approval workflow, I can copy a workflow so that I can tweak it and save a new workflow from the existing workflow.

      Exit Criteria:

      1. DMS user hits 'Save'.
      2. DMS user exits the DMS platform.

      Prerequisites:

      1. User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
      2. User knows how to access portal either by link or within CB application.

        Attachments

        1. 1.1 Approver List.png
          1.1 Approver List.png
          146 kB
        2. 1.2 Add New Approver.png
          1.2 Add New Approver.png
          95 kB
        3. 1.3 Add New Approver.png
          1.3 Add New Approver.png
          114 kB
        4. 1.4 Add New Approver.png
          1.4 Add New Approver.png
          116 kB
        5. 1.5 Approver List actions.png
          1.5 Approver List actions.png
          147 kB
        6. 1.6 Approver List Copy.png
          1.6 Approver List Copy.png
          111 kB

          Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. DMS-1824 Create an API to fetch all approver groups along with paging and sorting features.

          • Medium - Has the potential to affect progress.
          • On hold in Test

          New Feature - A new feature of the product, which has yet to be developed. DMS-1825 Create an API to fetch particular approver group details

          • Medium - Has the potential to affect progress.
          • On hold in Test

          New Feature - A new feature of the product, which has yet to be developed. DMS-1826 Create an API to add/update approver group data.

          • Medium - Has the potential to affect progress.
          • To Do

          New Feature - A new feature of the product, which has yet to be developed. DMS-1827 Create an API to delete a particular approver group.

          • Medium - Has the potential to affect progress.
          • In QA Testing

          New Feature - A new feature of the product, which has yet to be developed. DMS-1828 Create a popup UI for adding/updating the approver group.

          • Medium - Has the potential to affect progress.
          • On hold in Test

          New Feature - A new feature of the product, which has yet to be developed. DMS-1829 Create a page to show all list of approver group along with data table functionality and action buttons

          • Medium - Has the potential to affect progress.
          • Done

            Activity

            Ascending order - Click to sort in descending order
            7 older comments
            Hide
            Permalink
            Robert.Malony Robert Malony (Inactive) added a comment -

            Hi Aruna Raheja,

            Thanks for updating this! Only change would be "Copy", not sure if that is the right term. "Use" or "Select" may be better - thoughts Kristen?

            -Robert

            Show
            Robert.Malony Robert Malony (Inactive) added a comment - Hi Aruna Raheja , Thanks for updating this! Only change would be "Copy", not sure if that is the right term. "Use" or "Select" may be better - thoughts Kristen ? -Robert
            Hide
            Permalink
            aruna.raheja Aruna Raheja added a comment -

            Hi Robert Malony,

            We are cloning the existing list, that's why i have used it as "copy". We can also use the term "Clone".

            Thoughts? Kristen Robert Malony

            cc:Samir

            Show
            aruna.raheja Aruna Raheja added a comment - Hi Robert Malony , We are cloning the existing list, that's why i have used it as "copy". We can also use the term "Clone". Thoughts? Kristen Robert Malony cc: Samir
            Hide
            Permalink
            Robert.Malony Robert Malony (Inactive) added a comment -

            Hi Aruna Raheja,

            In that case, lets stick with "Copy".

            Thanks,
            Robert

            cc: Kristen and Samir

            Show
            Robert.Malony Robert Malony (Inactive) added a comment - Hi Aruna Raheja , In that case, lets stick with "Copy". Thanks, Robert cc: Kristen and Samir
            Hide
            Permalink
            narendra.kumar Narendra Kumar added a comment -

            Hi Robert Malony

            We have a few queries regarding this approver workflow.

            1) Can we have an option of no of days instead of the expiry date? Since we are creating an approver group that can we use multiple times for multiple documents. If we will use expiry date, we have te review expiry date for each user every time when we will send the document to the candidate. So we can use the no of days in which approver can take action otherwise it will be assumed as a skipped.

            2) Can we have at least one mandatory user in the approver group?

            cc - Samir

            Show
            narendra.kumar Narendra Kumar added a comment - Hi Robert Malony We have a few queries regarding this approver workflow. 1) Can we have an option of no of days instead of the expiry date ? Since we are creating an approver group that can we use multiple times for multiple documents. If we will use expiry date, we have te review expiry date for each user every time when we will send the document to the candidate. So we can use the no of days in which approver can take action otherwise it will be assumed as a skipped. 2) Can we have at least one mandatory user in the approver group? cc - Samir
            Hide
            Permalink
            Robert.Malony Robert Malony (Inactive) added a comment -

            Hi Narendra Kumar,

            See my comments below:

            1. Yes, that makes total sense and we can assign number of days rather than expiry date.
            2. Not sure what you mean by having one mandatory user? Are you referring to a person that has to review and Approve, and will not skip, regardless of settings? If so, then yes, and we will need UX to provide a means to select Mandatory users - cause I can see there being more than one, potentially.

            -Robert

            cc: Samir, Kristen, and Aruna Raheja

            Show
            Robert.Malony Robert Malony (Inactive) added a comment - Hi Narendra Kumar , See my comments below: Yes, that makes total sense and we can assign number of days rather than expiry date. Not sure what you mean by having one mandatory user? Are you referring to a person that has to review and Approve, and will not skip, regardless of settings? If so, then yes, and we will need UX to provide a means to select Mandatory users - cause I can see there being more than one, potentially. -Robert cc: Samir , Kristen , and Aruna Raheja

              People

              Assignee:
              narendra.kumar Narendra Kumar
              Reporter:
              molly.ronovsky Molly Ronovsky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 64h
                  64h
                  Remaining:
                  Remaining Estimate - 32h
                  32h
                  Logged:
                  Time Spent - Not Specified Time Not Required
                  Not Specified