-
Type:
New Feature
-
Status: Done
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: CBAT Offer Letter - Fall
-
Labels:None
-
Company:All Clients/Multiple Clients
-
Epic Link:
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.
Field | Original Value | New Value |
---|---|---|
Issue Type | Bug [ 1 ] | New Feature [ 2 ] |
Priority | Medium [ 3 ] | Critical [ 1 ] |
Fix Version/s | Enhancements - Fall [ 10610 ] |
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. |
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. |
Summary | Custom Fields | ATS Custom Fields in DMS |
Fix Version/s | CBAT Offer Letter - Fall [ 10607 ] | |
Fix Version/s | Enhancements - Fall [ 10610 ] |
Sprint | DMS - Fall Sprint 3 [ 162 ] |
Remaining Estimate | 32h [ 115200 ] | |
Original Estimate | 32h [ 115200 ] |
Sprint | DMS - Fall Sprint 3 [ 162 ] |
Sprint | DMS - Fall Sprint 5 [ 164 ] |
Assignee | Samir [ samir ] | Rohan J Khandave [ rohan.khandave ] |
Status | To Do [ 10000 ] | In Progress [ 3 ] |
Summary | ATS Custom Fields in DMS | CBATS : ATS Custom Fields in DMS |
-
- Time Spent:
- 4h
-
Analysis
Call with samir & Shared Documents.
Remaining Estimate | 32h [ 115200 ] | 28h [ 100800 ] |
Time Spent | 4h [ 14400 ] | |
Worklog Id | 183596 [ 183596 ] |
Attachment | TSRShared-CustomfieldsforOfferLetter-100619-1038.pdf [ 110581 ] | |
Attachment | Alex -- Non custom fields.xlsx [ 110582 ] | |
Attachment | Custom Attributes DB.xlsx [ 110583 ] |
-
- Time Spent:
- 6h
-
Call with Samir & Ravi
Data base design analysis & created scripts.
Remaining Estimate | 28h [ 100800 ] | 22h [ 79200 ] |
Time Spent | 4h [ 14400 ] | 10h [ 36000 ] |
Worklog Id | 184328 [ 184328 ] |
-
- Time Spent:
- 5.5h
-
Discussion with Samir & Harshveer
Code Analysis
Created data structure on dummy database
Added new columns into DmsFields table , Sourcesystemfields table
Remaining Estimate | 22h [ 79200 ] | 16.5h [ 59400 ] |
Time Spent | 10h [ 36000 ] | 15.5h [ 55800 ] |
Worklog Id | 184330 [ 184330 ] |
-
- Time Spent:
- 5h
-
Custom Field code changes analysis
Created super admin user on production
Remove custom fields added and reset field id column values.
Remaining Estimate | 16.5h [ 59400 ] | 11.5h [ 41400 ] |
Time Spent | 15.5h [ 55800 ] | 20.5h [ 73800 ] |
Worklog Id | 184607 [ 184607 ] |
Sprint | DMS - Fall Sprint 5 [ 164 ] | DMS - Fall Sprint 5, DMS - Fall Sprint 6 [ 164, 165 ] |
-
- 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
Remaining Estimate | 11.5h [ 41400 ] | 8.5h [ 30600 ] |
Time Spent | 20.5h [ 73800 ] | 23.5h [ 84600 ] |
Worklog Id | 184879 [ 184879 ] |
Status | In Progress [ 3 ] | Code Review [ 11801 ] |
Status | Code Review [ 11801 ] | In QA Testing [ 11901 ] |
Assignee | Rohan J Khandave [ rohan.khandave ] | Samir [ samir ] |
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 ] |
Assignee | Samir [ samir ] | Priya Dhamande [ priya.dhamande ] |
Status | In QA Testing [ 11901 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | To Do [ 10000 ] |
Assignee | Priya Dhamande [ priya.dhamande ] | Rohan J Khandave [ rohan.khandave ] |
Resolution | Done [ 10000 ] | |
Status | To Do [ 10000 ] | Done [ 10001 ] |
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 |
---|
|
39d 8h 52m | 1 |
|
20d 23h 29m | 1 |
|
1h 17m | 1 |
|
2d 4h 15m | 1 |
|
2s | 1 |
|
2s | 1 |
|
2h 37m | 1 |
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