Details

    • Type: New Feature
    • Status: Done
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: CBAT Offer Letter - Fall
    • Labels:
      None

      Description

      Overview - DMS should be able to support Custom fields for each client. Custom field support for Clients – Understanding this is a critical and required ask from all clients related to whether govt forms, onboarding or offer letter forms. Beta testing will be difficult for clients who have lots of custom fields. Send Client specific Custom data fields (candidate & requisition) to DMS for mapping.

      Entry:

      • Template Library in DMS
      • User should be able to view them in System Fields.
      • CB AT user enters DMS from CB AT.
      • CB AT user uploads form.
      • CB AT sees mapping section populate with fields from CB AT.
      • CB AT shows custom fields within the system fields

      Acceptance criteria:

      • User should be able to view custom fields in the client specific System Fields section during Mapping of fields between form and system fields.
      • ATS should send all the fields to DMS and DMS creates tags for thoes custom fields
      • User should be able to Map custom fields to the Fields available in System Fields.
      • As a CB AT user, I want CB AT to send all clients specific custom attributes candidate and requisition fields from CB AT to the DMS so that fields can be prepopulated within a document system field section with information that a candidate has already given CB AT. 

      *IF I am using the DMS system, I am able to create forms with the ability to map fields from CB AT to the form.
      *IF I have uploaded a form in the DMS, I can use fields from CB AT to populate candidate & requisition information 

      Exit:

      • User Maps the field to create a template

      Dependencies:

      Client's custom fields tag should be stored in ATS

      HITT Contracting:

      o   62 Sertfi different documents in CBAT (including Offer letters)

      o   Using at least 11 custom fields

      -         Penhall:

      o   16 different documents in CBAT (Mostly offer letters)

      o   Using at least 5 custom fields

      -         Multi-Color Corporation:

      o   No Sertifi documents in CBAT toolbox.

      o   Looks like client is sending document from the Sertifi portal directly.

      • Type of documents:
      • Benefits Guide
      • Authorization form
      • New hire news letter

      o   might be a good fit for DMS as is, for the ad-hoc document sending.; for use in workflow: CSM would need to confirm how the client uses sertfi and gather an exhaustive list of document to ensure no custom fields would be need.

        Attachments

          Issue Links

            Activity

            Monika.Demla Monika Demla (Inactive) created issue -
            Monika.Demla Monika Demla (Inactive) made changes -
            Field Original Value New Value
            Issue Type Bug [ 1 ] New Feature [ 2 ]
            Monika.Demla Monika Demla (Inactive) made changes -
            Priority Medium [ 3 ] Critical [ 1 ]
            Hide
            Monika.Demla Monika Demla (Inactive) added a comment -

            This feature is critical for Beta clients as they will not be able to continue beta testing without seeing their set of data in the system.

            cc Ravi Banda

            Show
            Monika.Demla Monika Demla (Inactive) added a comment - This feature is critical for Beta clients as they will not be able to continue beta testing without seeing their set of data in the system. cc Ravi Banda
            Monika.Demla Monika Demla (Inactive) made changes -
            Link This issue is cloned by DMS-1376 [ DMS-1376 ]
            ramya.tantry Ramya Tantry (Inactive) made changes -
            Fix Version/s Enhancements - Fall [ 10610 ]
            Monika.Demla Monika Demla (Inactive) made changes -
            Description Overview - DMS should be able to support Custom fields for each client. Custom field support for Clients – Understanding this is a critical and required ask from all clients related to whether govt forms, onboarding or offer letter forms. Beta testing will be difficult for clients who have lots of custom fields

            Entry:

            Template Library in DMS

            Acceptance criteria:

            User should be able to view custom fields in the client specific *System Fields* section during Mapping of fields between form and system fields.

            HITT Contracting:

            o   62 sertfi different documents in CBAT (including Offer letters)

            o   Using at least 11 custom fields

             

            -         Penhall:

            o   16 different documents in CBAT (Mostly offer letters)

            o   Using at least 5 custom fields

             

            -         Multi-Color Corporation:

            o   No Sertifi documents in CBAT toolbox.

            o   Looks like client is sending document from the Sertifi portal directly.
             * Type of documents:
             * Benefits Guide
             * Authorization form
             * New hire news letter

            o   might be a good fit for DMS as is, for the ad-hoc document sending.; for use in workflow: CSM would need to confirm how the client uses sertfi and gather an exhaustive list of document to ensure no custom fields would be need.
            *Overview* - DMS should be able to support Custom fields for each client. Custom field support for Clients – Understanding this is a critical and required ask from all clients related to whether govt forms, onboarding or offer letter forms. Beta testing will be difficult for clients who have lots of custom fields

            *Entry:*
             * Template Library in DMS
             * User should be able to view them in System Fields.

            *Acceptance criteria:*
             * User should be able to view custom fields in the client specific *System Fields* section during Mapping of fields between form and system fields.
             * ATS should send all the fields to DMS and DMS creates tags for thoes custom fields
             * User should be able to Map custom fields to the Fields available in System Fields.

            *Exit:*
             * User Maps the field to create a template

            *Dependencies:*

            Client's custom fields tag should be stored in ATS

            HITT Contracting:

            o   62 Sertfi different documents in CBAT (including Offer letters)

            o   Using at least 11 custom fields

            -         Penhall:

            o   16 different documents in CBAT (Mostly offer letters)

            o   Using at least 5 custom fields

            -         Multi-Color Corporation:

            o   No Sertifi documents in CBAT toolbox.

            o   Looks like client is sending document from the Sertifi portal directly.
             * Type of documents:
             * Benefits Guide
             * Authorization form
             * New hire news letter

            o   might be a good fit for DMS as is, for the ad-hoc document sending.; for use in workflow: CSM would need to confirm how the client uses sertfi and gather an exhaustive list of document to ensure no custom fields would be need.
            Hide
            Monika.Demla Monika Demla (Inactive) added a comment -

            Ravi Banda / Swapnil Pandhare / Shamooka Mohapatra  - Let me know if you need more details.

            Show
            Monika.Demla Monika Demla (Inactive) added a comment - Ravi Banda / Swapnil Pandhare / Shamooka Mohapatra   - Let me know if you need more details.
            Monika.Demla Monika Demla (Inactive) made changes -
            Description *Overview* - DMS should be able to support Custom fields for each client. Custom field support for Clients – Understanding this is a critical and required ask from all clients related to whether govt forms, onboarding or offer letter forms. Beta testing will be difficult for clients who have lots of custom fields

            *Entry:*
             * Template Library in DMS
             * User should be able to view them in System Fields.

            *Acceptance criteria:*
             * User should be able to view custom fields in the client specific *System Fields* section during Mapping of fields between form and system fields.
             * ATS should send all the fields to DMS and DMS creates tags for thoes custom fields
             * User should be able to Map custom fields to the Fields available in System Fields.

            *Exit:*
             * User Maps the field to create a template

            *Dependencies:*

            Client's custom fields tag should be stored in ATS

            HITT Contracting:

            o   62 Sertfi different documents in CBAT (including Offer letters)

            o   Using at least 11 custom fields

            -         Penhall:

            o   16 different documents in CBAT (Mostly offer letters)

            o   Using at least 5 custom fields

            -         Multi-Color Corporation:

            o   No Sertifi documents in CBAT toolbox.

            o   Looks like client is sending document from the Sertifi portal directly.
             * Type of documents:
             * Benefits Guide
             * Authorization form
             * New hire news letter

            o   might be a good fit for DMS as is, for the ad-hoc document sending.; for use in workflow: CSM would need to confirm how the client uses sertfi and gather an exhaustive list of document to ensure no custom fields would be need.
            *Overview* - DMS should be able to support Custom fields for each client. Custom field support for Clients – Understanding this is a critical and required ask from all clients related to whether govt forms, onboarding or offer letter forms. Beta testing will be difficult for clients who have lots of custom fields. Send Client specific Custom data fields (candidate & requisition) to DMS for mapping.

            *Entry:*
             * Template Library in DMS
             * User should be able to view them in System Fields.
             * CB AT user enters DMS from CB AT.
             * CB AT user uploads form.
             * CB AT sees mapping section populate with fields from CB AT.
             * CB AT shows custom fields within the system fields

            *Acceptance criteria:*
             * User should be able to view custom fields in the client specific *System Fields* section during Mapping of fields between form and system fields.
             * ATS should send all the fields to DMS and DMS creates tags for thoes custom fields
             * User should be able to Map custom fields to the Fields available in System Fields.
             * As a CB AT user, I want CB AT to send all clients specific custom attributes candidate and requisition fields from CB AT to the DMS so that fields can be prepopulated within a document system field section with information that a candidate has already given CB AT. 

            *IF I am using the DMS system, I am able to create forms with the ability to map fields from CB AT to the form.
            *IF I have uploaded a form in the DMS, I can use fields from CB AT to populate candidate & requisition information 

            *Exit:*
             * User Maps the field to create a template

            *Dependencies:*

            Client's custom fields tag should be stored in ATS

            HITT Contracting:

            o   62 Sertfi different documents in CBAT (including Offer letters)

            o   Using at least 11 custom fields

            -         Penhall:

            o   16 different documents in CBAT (Mostly offer letters)

            o   Using at least 5 custom fields

            -         Multi-Color Corporation:

            o   No Sertifi documents in CBAT toolbox.

            o   Looks like client is sending document from the Sertifi portal directly.
             * Type of documents:
             * Benefits Guide
             * Authorization form
             * New hire news letter

            o   might be a good fit for DMS as is, for the ad-hoc document sending.; for use in workflow: CSM would need to confirm how the client uses sertfi and gather an exhaustive list of document to ensure no custom fields would be need.
            Monika.Demla Monika Demla (Inactive) made changes -
            Link This issue is cloned by DMS-1412 [ DMS-1412 ]
            Monika.Demla Monika Demla (Inactive) made changes -
            Summary Custom Fields ATS Custom Fields in DMS
            samir Samir made changes -
            Fix Version/s CBAT Offer Letter - Fall [ 10607 ]
            Fix Version/s Enhancements - Fall [ 10610 ]
            samir Samir made changes -
            Sprint DMS - Fall Sprint 3 [ 162 ]
            samir Samir made changes -
            Remaining Estimate 32h [ 115200 ]
            Original Estimate 32h [ 115200 ]
            samir Samir made changes -
            Sprint DMS - Fall Sprint 3 [ 162 ]
            samir Samir made changes -
            Sprint DMS - Fall Sprint 5 [ 164 ]
            Show
            samir Samir added a comment -   https://careerbuilder.atlassian.net/wiki/spaces/HCM/pages/460980460/ATS+Custom+Fields+in+DMS
            samir Samir made changes -
            Assignee Samir [ samir ] Rohan J Khandave [ rohan.khandave ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Status To Do [ 10000 ] In Progress [ 3 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Summary ATS Custom Fields in DMS CBATS : ATS Custom Fields in DMS
            rohan.khandave Rohan J Khandave (Inactive) logged work - 17/Jun/19 07:11 AM
            • Time Spent:
              4h
               

              Analysis

              Call with samir & Shared Documents.

            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Remaining Estimate 32h [ 115200 ] 28h [ 100800 ]
            Time Spent 4h [ 14400 ]
            Worklog Id 183596 [ 183596 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            Working on Analysis.

            Shared 3 approached data structure for custom fields implementation & discuss with samir.
            Custom Attributes DB.xlsx

            Below 2 files shared by Alex.
            Alex – Non custom fields.xlsx
            TSRShared-CustomfieldsforOfferLetter-100619-1038.pdf

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - Working on Analysis. Shared 3 approached data structure for custom fields implementation & discuss with samir. Custom Attributes DB.xlsx Below 2 files shared by Alex. Alex – Non custom fields.xlsx TSRShared-CustomfieldsforOfferLetter-100619-1038.pdf
            rohan.khandave Rohan J Khandave (Inactive) logged work - 19/Jun/19 07:19 AM
            • Time Spent:
              6h
               

              Call with Samir & Ravi

              Data base design analysis & created scripts.

            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Remaining Estimate 28h [ 100800 ] 22h [ 79200 ]
            Time Spent 4h [ 14400 ] 10h [ 36000 ]
            Worklog Id 184328 [ 184328 ]
            rohan.khandave Rohan J Khandave (Inactive) logged work - 20/Jun/19 07:22 AM
            • Time Spent:
              5.5h
               

              Discussion with Samir & Harshveer
              Code Analysis
              Created data structure on dummy database
              Added new columns into DmsFields table , Sourcesystemfields table

            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Remaining Estimate 22h [ 79200 ] 16.5h [ 59400 ]
            Time Spent 10h [ 36000 ] 15.5h [ 55800 ]
            Worklog Id 184330 [ 184330 ]
            samir Samir made changes -
            Epic Link DMS-473 [ 75966 ]
            rohan.khandave Rohan J Khandave (Inactive) logged work - 21/Jun/19 06:39 AM
            • Time Spent:
              5h
               

              Custom Field code changes analysis
              Created super admin user on production
              Remove custom fields added and reset field id column values.

            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Remaining Estimate 16.5h [ 59400 ] 11.5h [ 41400 ]
            Time Spent 15.5h [ 55800 ] 20.5h [ 73800 ]
            Worklog Id 184607 [ 184607 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 5 [ 164 ] DMS - Fall Sprint 5, DMS - Fall Sprint 6 [ 164, 165 ]
            rohan.khandave Rohan J Khandave (Inactive) logged work - 24/Jun/19 07:38 AM
            • Time Spent:
              3h
               

              Created system field & custom field list from payload provided by client.
              Created common document / excel to maintain them.
              Discussion with Ramya , Akash

            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Remaining Estimate 11.5h [ 41400 ] 8.5h [ 30600 ]
            Time Spent 20.5h [ 73800 ] 23.5h [ 84600 ]
            Worklog Id 184879 [ 184879 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Status In Progress [ 3 ] Code Review [ 11801 ]
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            Fields are added under DMS-1542.

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - Fields are added under DMS-1542 .
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Link This issue relates to DMS-1542 [ DMS-1542 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Link This issue relates to DMS-1542 [ DMS-1542 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Status Code Review [ 11801 ] In QA Testing [ 11901 ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Assignee Rohan J Khandave [ rohan.khandave ] Samir [ samir ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Link This issue relates to DMS-1542 [ DMS-1542 ]
            shashikant.mishra ShashiKant Mishra (Inactive) made changes -
            Sprint DMS - Fall Sprint 5, DMS - Fall Sprint 6 [ 164, 165 ] DMS - Fall Sprint 5, DMS - Fall Sprint 6, DMS - Fall Sprint 7 [ 164, 165, 166 ]
            priya.dhamande Priya Dhamande (Inactive) made changes -
            Assignee Samir [ samir ] Priya Dhamande [ priya.dhamande ]
            Hide
            priya.dhamande Priya Dhamande (Inactive) added a comment -

            Testing of this jira is covered under DMS-1542.

            Implementation and testing pending for HTML and TEXT type document. So, assigning to Rohan J Khandave, for implementation of HTMl and Text type document.

            Hrishikesh Deshpande Samir

            Show
            priya.dhamande Priya Dhamande (Inactive) added a comment - Testing of this jira is covered under DMS-1542 . Implementation and testing pending for HTML and TEXT type document. So, assigning to Rohan J Khandave , for implementation of HTMl and Text type document. Hrishikesh Deshpande Samir
            priya.dhamande Priya Dhamande (Inactive) made changes -
            Status In QA Testing [ 11901 ] In Progress [ 3 ]
            priya.dhamande Priya Dhamande (Inactive) made changes -
            Status In Progress [ 3 ] In Progress [ 3 ]
            priya.dhamande Priya Dhamande (Inactive) made changes -
            Status In Progress [ 3 ] To Do [ 10000 ]
            priya.dhamande Priya Dhamande (Inactive) made changes -
            Assignee Priya Dhamande [ priya.dhamande ] Rohan J Khandave [ rohan.khandave ]
            rohan.khandave Rohan J Khandave (Inactive) made changes -
            Resolution Done [ 10000 ]
            Status To Do [ 10000 ] Done [ 10001 ]
            Hide
            rohan.khandave Rohan J Khandave (Inactive) added a comment -

            We have created separate ticket for HTML , refer DMS-1546

            Show
            rohan.khandave Rohan J Khandave (Inactive) added a comment - We have created separate ticket for HTML , refer DMS-1546
            priya.dhamande Priya Dhamande (Inactive) logged work - 11/Jul/19 04:09 AM
            • Time Spent:
              2h
               

              preprod

            priya.dhamande Priya Dhamande (Inactive) made changes -
            Remaining Estimate 8.5h [ 30600 ] 6.5h [ 23400 ]
            Time Spent 23.5h [ 84600 ] 25.5h [ 91800 ]
            Worklog Id 187733 [ 187733 ]
            Transition Time In Source Status Execution Times
            Rohan J Khandave (Inactive) made transition -
            To Do In Progress
            39d 8h 52m 1
            Rohan J Khandave (Inactive) made transition -
            In Progress Code Review
            20d 23h 29m 1
            Rohan J Khandave (Inactive) made transition -
            Code Review In QA Testing
            1h 17m 1
            Priya Dhamande (Inactive) made transition -
            In QA Testing In Progress
            2d 4h 15m 1
            Priya Dhamande (Inactive) made transition -
            In Progress In Progress
            2s 1
            Priya Dhamande (Inactive) made transition -
            In Progress To Do
            2s 1
            Rohan J Khandave (Inactive) made transition -
            To Do Done
            2h 37m 1

              People

              Assignee:
              rohan.khandave Rohan J Khandave (Inactive)
              Reporter:
              Monika.Demla Monika Demla (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 32h
                  32h
                  Remaining:
                  Time Spent - 25.5h Remaining Estimate - 6.5h
                  6.5h
                  Logged:
                  Time Spent - 25.5h Remaining Estimate - 6.5h
                  25.5h