CBATS : ATS Custom Fields in DMS

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.