-
Type:
New Feature
-
Status: To Do
-
Priority:
High
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Company:All Clients/Multiple Clients
What would it take for DMS to use CBAT tags from the requisition (Company) –
Is this value already coming to DMS as part of document generation? You can check the mapped fields - https://careerbuilder.atlassian.net/wiki/spaces/TSRShared/pages/496927041/DMS+Template+mapping+fields. If the data you are looking for isn’t mapped here then there is potential work on the CBAT team as well.
I have also taken a closer look at the list of fields and I am surprised that many fields are not part of it. I thought all fields available in CBAT would be mapped through DMS.
In this specific case, we need:
- req field: prop31
- User field: prop4 (user email from user selected on req field: prop185)
- User field: prop11 (user email signature from user selected on req field: prop185)
- User field: prop0, prop1 (user last and first name from user selected on req field: prop185)
But over we would expect to have all field values available as tags for DMS email (same as the tag for CBAT email template)
Field | Original Value | New Value |
---|---|---|
Description | *DMS to use CBAT tags from the requisition* |
*What would it take for DMS to use CBAT tags from the requisition (Company)* –
Is this value already coming to DMS as part of document generation? You can check the mapped fields - [https://careerbuilder.atlassian.net/wiki/spaces/TSRShared/pages/496927041/DMS+Template+mapping+fields]. If the data you are looking for isn’t mapped here then there is potential work on the CBAT team as well. I have also taken a closer look at the list of fields and I am surprised that many fields are not part of it. I thought all fields available in CBAT would be mapped through DMS. In this specific case, we need: * req field: prop31 * User field: prop4 (user email from user selected on req field: prop185) * User field: prop11 (user email signature from user selected on req field: prop185) * User field: prop0, prop1 (user last and first name from user selected on req field: prop185) But over we would expect to have all field values available as tags for DMS email (same as the tag for CBAT email template) |
Attachment | DMS to use CBAT tags.eml [ 157223 ] |
Ravi Banda, Samir, Harshveer Singh