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
            molly.ronovsky Molly Ronovsky (Inactive) created issue -
            molly.ronovsky Molly Ronovsky (Inactive) made changes -
            Field Original Value New Value
            Epic Link DMS-40 [ 69739 ]
            molly.ronovsky Molly Ronovsky (Inactive) made changes -
            Fix Version/s Winter release [ 10428 ]
            Prashant.samal Prashant Samal (Inactive) made changes -
            Sprint DMS - Sprint 4 [ 132 ]
            Prashant.samal Prashant Samal (Inactive) made changes -
            Rank Ranked higher
            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Sprint DMS - Sprint 4 [ 132 ]
            akash.thakur Akash Thakur (Inactive) made changes -
            Sprint DMS - Sprint 6 [ 134 ]
            akash.thakur Akash Thakur (Inactive) made changes -
            Rank Ranked higher
            swapnil.pandhare Swapnil Pandhare (Inactive) made changes -
            Sprint DMS - Sprint 6 [ 134 ]
            prasad.patil Prasad Patil (Inactive) made changes -
            Resolution Not in scope [ 10700 ]
            Status To Do [ 10000 ] Done [ 10001 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Resolution Not in scope [ 10700 ]
            Status Done [ 10001 ] To Do [ 10000 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Fix Version/s Enhancements - Fall [ 10610 ]
            Fix Version/s Winter release [ 10428 ]
            samir Samir made changes -
            Remaining Estimate 32h [ 115200 ]
            Original Estimate 32h [ 115200 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6 [ 165 ]
            Hide
            Permalink
            samir Samir added a comment -

            Hi Robert Malony,

            Below tickets are related to Multiple Signer feature, Can you please confirm this functionality

            DMS-43

            DMS-44

            DMS-45

            DMS-46

            DMS-47

            Regards,

            Samir

            ShashiKant Mishra

            Show
            samir Samir added a comment - Hi Robert Malony , Below tickets are related to Multiple Signer feature, Can you please confirm this functionality DMS-43 DMS-44 DMS-45 DMS-46 DMS-47 Regards, Samir ShashiKant Mishra
            samir Samir made changes -
            Assignee Samir [ samir ] Robert Malony [ robert.malony ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6 [ 165 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ]
            Robert.Malony Robert Malony (Inactive) made changes -
            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:
            1. User enters DMS platform via link or consuming application.
            2. User navigates to create an approval workflow

            Acceptance Criteria:
            *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.
            *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).
            *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.
            *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:
            *DMS user hits 'Save'.
            *DMS user exits the DMS platform.

            Prerequisites:
            *User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            *User knows how to access portal either by link or within CB application.             		h2. h2. 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:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            Acceptance Criteria:
             # 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.
             # 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).
            # 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.
             # 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:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. h2. 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:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            Acceptance Criteria:
             # 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.
             # 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).
            # 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.
             # 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:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.             		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:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             

            Acceptance Criteria:
             # 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.
             # 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).
             # 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.
             # 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:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             

            Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            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:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             

            Acceptance Criteria:
             # 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.
             # 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).
             # 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.
             # 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:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             

            Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.             		h2. 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.

             h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             h3. Acceptance Criteria:
             # 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.
             # 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).
             # 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.
             # 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.

             h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             h3. Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. 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.

             h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

             h3. Acceptance Criteria:
             # 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.
             # 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).
             # 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.
             # 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.

             h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

             h3. Prerequisites:
             # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
             # User knows how to access portal either by link or within CB application.             		h2. 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.

            h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # 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.
            # 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).
            # 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.
             # 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.

            h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. 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.

            h3. Entry Criteria:
             # User enters DMS platform via link or consuming application.
             # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # 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.
            # 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).
            # 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.
             # 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.

            h3. Exit Criteria:
             # DMS user hits 'Save'.
             # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.             		h2. 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.

            h3. Entry Criteria:
            # User enters DMS platform via link or consuming application.
            # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # 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.
            # 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).
            # 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.
             # 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.

            h3. Exit Criteria:
            # DMS user hits 'Save'.
            # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Description h2. 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.

            h3. Entry Criteria:
            # User enters DMS platform via link or consuming application.
            # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # 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.
            # 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).
            # 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.
             # 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.

            h3. Exit Criteria:
            # DMS user hits 'Save'.
            # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.             		h2. 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.

            h3. Entry Criteria:
            # User enters DMS platform via link or consuming application.
            # User navigates to create an approval workflow

            h3. Acceptance Criteria:
            # 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.
            # 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).
            # 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.
            # 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.

            h3. Exit Criteria:
            # DMS user hits 'Save'.
            # DMS user exits the DMS platform.

            h3. Prerequisites:
            # User is a current user of CBAT, CBES, or WT OR has stand alone link to log in.
            # User knows how to access portal either by link or within CB application.
            Robert.Malony Robert Malony (Inactive) made changes -
            Labels Needs_UX
            Hide
            Permalink
            Robert.Malony Robert Malony (Inactive) added a comment -

            Hi Samir,

            Reviewed these requirements and we need this functionality with Offer Letter for Fall release.

            Adding for UX to provide any visuals that are needed as there has to be a chain of approval and rejections for offer letters.

            -Robert

            cc: ShashiKant Mishra and Kristen

            Show
            Robert.Malony Robert Malony (Inactive) added a comment - Hi Samir , Reviewed these requirements and we need this functionality with Offer Letter for Fall release. Adding for UX to provide any visuals that are needed as there has to be a chain of approval and rejections for offer letters. -Robert cc: ShashiKant Mishra and Kristen
            Robert.Malony Robert Malony (Inactive) made changes -
            Assignee Robert Malony [ robert.malony ] Kristen [ ruel ]
            Hide
            Permalink
            aruna.raheja Aruna Raheja added a comment -

            Hi Robert Malony, Samir, Kristen

            Please check the attached mockups and provide your feedback onto the same.

            CC: ShashiKant Mishra

            Show
            aruna.raheja Aruna Raheja added a comment - Hi Robert Malony , Samir , Kristen Please check the attached mockups and provide your feedback onto the same. CC: ShashiKant Mishra
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.1 Approver List.png [ 113200 ]
            Attachment 1.2 Add New Approver.png [ 113201 ]
            Attachment 1.3 Add New Approver.png [ 113202 ]
            Attachment 1.4 Add New Approver.png [ 113203 ]
            Attachment 1.5 Approver List actions.png [ 113204 ]
            Attachment 1.6 Approver List Copy.png [ 113205 ]
            Hide
            Permalink
            Robert.Malony Robert Malony (Inactive) added a comment -

            Hi Aruna Raheja,

            Looks good but a few quick question:

            1. Why are there two fields for Add a Group Name. THe first one at the top makes sense, but shouldn't the other textarea be named "Add Approvers to Group".
            2. What is the Expiration Date suppose to do? Is it that when that date comes, then that group of Approvers is skipped?
            3. What is the + icon to the right of the Expiration Date?
            4. Also, per the requirements, I can use a premade Group to select from already - can you add that functionality in there as well? Maybe at the top a control that you can pick from a premade or create new?

            Thanks,
            Robert

            cc: Samir and Kristen

            Show
            Robert.Malony Robert Malony (Inactive) added a comment - Hi Aruna Raheja , Looks good but a few quick question: Why are there two fields for Add a Group Name. THe first one at the top makes sense, but shouldn't the other textarea be named "Add Approvers to Group". What is the Expiration Date suppose to do? Is it that when that date comes, then that group of Approvers is skipped? What is the + icon to the right of the Expiration Date? Also, per the requirements, I can use a premade Group to select from already - can you add that functionality in there as well? Maybe at the top a control that you can pick from a premade or create new? Thanks, Robert cc: Samir and Kristen
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Fall Sprint 8 [ 165, 166, 167 ]
            Hide
            Permalink
            aruna.raheja Aruna Raheja added a comment - - edited

            Hi Robert Malony,

            Here are the answers to your questions:

            1. ** Why are there two fields for Add a Group Name. THe first one at the top makes sense, but shouldn't the other textarea be named "Add Approvers to Group". By mistake I forgot to change label names. It’s updated now kindly check
            2. What is the Expiration Date supposed to do? Is it that when that date comes, then that group of Approvers is skipped? Yes, that particular approver get automatically skipped
            3. ** What is the + icon to the right of the Expiration Date? This icon is used to add approver. You can check screen “1.4 Add New Approver” for reference
            4. Also, per the requirements, I can use a premade Group to select from already - can you add that functionality in there as well? Maybe at the top a control that you can pick from a premade or create new? I have a query on this, are we going to create group of user without expiry date or with expiry date

            Thanks,
            Aruna

            cc: Samir and Kristen

            Show
            aruna.raheja Aruna Raheja added a comment - - edited Hi Robert Malony , Here are the answers to your questions: ** Why are there two fields for Add a Group Name. THe first one at the top makes sense, but shouldn't the other textarea be named "Add Approvers to Group". By mistake I forgot to change label names. It’s updated now kindly check What is the Expiration Date supposed to do? Is it that when that date comes, then that group of Approvers is skipped? Yes, that particular approver get automatically skipped ** What is the + icon to the right of the Expiration Date? This icon is used to add approver. You can check screen “1.4 Add New Approver” for reference Also, per the requirements, I can use a premade Group to select from already - can you add that functionality in there as well? Maybe at the top a control that you can pick from a premade or create new? I have a query on this, are we going to create group of user without expiry date or with expiry date Thanks, Aruna cc:  Samir  and  Kristen
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.3 Add New Approver.png [ 113202 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.4 Add New Approver.png [ 113203 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.2 Add New Approver.png [ 113201 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.1 Approver List.png [ 113200 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.5 Approver List actions.png [ 113204 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.6 Approver List Copy.png [ 113205 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.1 Approver List.png [ 114000 ]
            Attachment 1.2 Add New Approver.png [ 114001 ]
            Attachment 1.3 Add New Approver.png [ 114002 ]
            Attachment 1.4 Add New Approver.png [ 114003 ]
            Attachment 1.5 Approver List actions.png [ 114004 ]
            Attachment 1.6 Approver List Copy.png [ 114005 ]
            Hide
            Permalink
            Robert.Malony Robert Malony (Inactive) added a comment -

            Hi Aruna Raheja,

            About number question number 4, the thought is that the Expiration Date is tied to that group to a specific document flow. Meaning that I'm not tying the Expiration Date to a specific group is ideal. That way, using a premade group is possible.

            Thanks,
            Robert

            cc: Samir and Kristen

            Show
            Robert.Malony Robert Malony (Inactive) added a comment - Hi Aruna Raheja , About number question number 4, the thought is that the Expiration Date is tied to that group to a specific document flow. Meaning that I'm not tying the Expiration Date to a specific group is ideal. That way, using a premade group is possible. Thanks, Robert cc: Samir and Kristen
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.5 Approver List actions.png [ 114004 ]
            aruna.raheja Aruna Raheja made changes -
            Attachment 1.5 Approver List actions.png [ 114818 ]
            Hide
            Permalink
            aruna.raheja Aruna Raheja added a comment -

            Hi Robert Malony : I have updated the mock 1.5, when you click on kaboob icon, it will provide you to copy that particular group. I think that is what you required. Do let me know if you have any other queries.

            Thanks,

            Aruna

            CC: Samir and Kristen

            Show
            aruna.raheja Aruna Raheja added a comment - Hi Robert Malony : I have updated the mock 1.5, when you click on kaboob icon, it will provide you to copy that particular group. I think that is what you required. Do let me know if you have any other queries. Thanks, Aruna CC: Samir and Kristen
            samir Samir made changes -
            Fix Version/s Between Fall and Winter 2019 [ 10919 ]
            Fix Version/s Enhancements - Fall [ 10610 ]
            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
            samir Samir made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Fall Sprint 8 [ 165, 166, 167 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 165, 166 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Fall release wrap - 1 [ 165, 166, 173 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Rank Ranked lower
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1 [ 165, 166, 173 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 2 [ 165, 166, 173, 174 ]
            samir Samir made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 2 [ 165, 166, 173, 174 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 3 [ 165, 166, 173, 177 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Original Estimate 32h [ 115200 ] 64h [ 230400 ]
            samir Samir made changes -
            Assignee Kristen [ ruel ] Narendra Kumar [ narendra.kumar ]
            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
            samir Samir made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 3 [ 165, 166, 173, 177 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 4 [ 165, 166, 173, 179 ]
            narendra.kumar Narendra Kumar made changes -
            Fix Version/s Winter 2020 Multiple Signers [ 11313 ]
            Fix Version/s Between Fall and Winter 2019 [ 10919 ]
            narendra.kumar Narendra Kumar made changes -
            Sprint DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1, DMS - Gap Fall & Win Sprint 4 [ 165, 166, 173, 179 ] DMS - Fall Sprint 6, DMS - Fall Sprint 7, DMS - Gap Fall & Win Sprint 1 [ 165, 166, 173 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1824 [ DMS-1824 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1825 [ DMS-1825 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1826 [ DMS-1826 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1827 [ DMS-1827 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1828 [ DMS-1828 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1829 [ DMS-1829 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1826 [ DMS-1826 ]
            narendra.kumar Narendra Kumar made changes -
            Link This issue relates to DMS-1826 [ DMS-1826 ]
            narendra.kumar Narendra Kumar made changes -
            Fix Version/s Multiple Signer [ 12111 ]
            Fix Version/s Winter 2020 Multiple Signers [ 11313 ]
            Transition Time In Source Status Execution Times
            Prasad Patil (Inactive) made transition -
            To Do Done
            		147d 8h 8m 1
            Rohan J Khandave (Inactive) made transition -
            Done To Do
            		42d 5h 38m 1

              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