Open stephaniemoorer opened 2 months ago
Easy CSV may be a option, will need to be tested
Sample eCareer Applicant Report: https://docs.google.com/spreadsheets/d/1XEdKuNU-Xz4LvtpRRyHJ82SSTBQkYN_r/edit?gid=985246883#gid=985246883
Worked on this a little yesterday with Patrick
object_XX
field_XX
Import files by sending emails with attachments or a link in the email body text
Post imports to an API/Webhook
https://api.knack.com/v1/objects/object_XX/records
ENTER API KEY
(Knack)
2 . Key: X-Knack-Application-Id - Value: ENTER APP ID
(Knack) "field_334": {
"first": "{{ FIRST }}",
"last": "{{ LAST }}"
},
"field_328": "{{ PHONE }}",
"field_376": {
"email": "{{ EMAIL_ADDRESS }}",
"label": "{{ EMAIL_ADDRESS }}"
}
}
job_posting_managment
)
118701 | Signs and Markings Tech II
@ChrispinP Tried to do embed only works on like w3schools.com
This JSON is working correctly
{
"field_334": {
"first": "{{ FIRST }}",
"last": "{{ LAST }}"
},
"field_328": "{{ PHONE }}",
"field_376": {
"email": "{{ EMAIL_ADDRESS }}",
"label": "{{ EMAIL_ADDRESS }}"
}
}
job_posting_managment
. job_applicants_TEST_Knack_import
job_applicants_TEST_EasyCSV
Max from EasyCSV point me to a Knack API article: https://docs.knack.com/docs/working-with-fields. This is probably my issue, I need to have the corresponding Knack record id
.
Connections are stored as arrays of record IDs (strings), even when there is only one connected record. Each of these is the ID of a record of the object to which this field connects.
JSON // More than one connected record ["4fea069e9e8246001d000698", "4fea069e9e8246001d000699"]
// One connected record ["4fea069e9e8246001d000699"]
#\36 6fedacf65a69e031bf74e07
6fedacf65a69e031bf74e07
job_posting_management
had an additional "X" at the end
["
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
per the Knack Dev article - Working with Fields
Stephanie and I synced and we decided to do some usability tests on three different methods.
NUMBER OF CLICKS:
TIME IT TAKES TO COMPLETE TASK:
NUMBER OF CLICKS:
TIME IT TAKES TO COMPLETE TASK:
NUMBER OF CLICKS:
TIME IT TAKES TO COMPLETE TASK:
BLOCKER - Have devs assist on getting import to work properly, tying an applicant to the hiring record.
Option 4: Custom Solution (DTS Devs)
Christina and I synced on this to review the Spike issue I made and then we decided to test a little more.
job_posting_management
from the display PCN to just the PCN numberWhat we remembered, we can't import via a connection field. It has to be non-connection field, (ex. ID, email). So we're close now, we just need the assistance of the Devs to update the JSON to specify which field from the connected table we're importing.
these are the configurations we did to make it work
json that works
"field_334": {
"first": "{{ FIRST_NAME }}",
"last": "{{ LAST_NAME }}"
},
"field_328": "{{ PHONE }}",
"field_376": {
"email": "{{ EMAIL_ADDRESS }}",
"label": "{{ EMAIL_ADDRESS }}"
},
"field_227":"{{ JOB_POSTING_MANAGEMENT }}"
}
"field_334": {
"first": "{{ FIRST_NAME }}",
"last": "{{ LAST_NAME }}"
},
"field_328": "{{ PHONE }}",
"field_376": {
"email": "{{ EMAIL_ADDRESS }}",
"label": "{{ EMAIL_ADDRESS }}"
},
"field_318": {
"job_posting_management": "{{ JOB_POSTING_MANAGEMENT }}",
"pcn": "{{ PCN }}"
}
}
Stephanie and I synced, I had updated
NUMBER OF CLICKS:
13TIME IT TAKES TO COMPLETE TASK:
1:12 NUMBER OF CLICKS:
TIME IT TAKES TO COMPLETE TASK:
1:11 (only got 3 names in bc having to copy paste into 2 fields)
Enhancement: get way paste name and then separate the names into the correct fields. The level of effort to have a single field and then separate can be more work than this is.
Latest JSON
"field_334": {
"first": "{{ FIRST_NAME }}",
"last": "{{ LAST_NAME }}"
},
"field_328": "{{ PHONE }}",
"field_390": "{{ JOB_TITLE }}",
"field_391": "{{ REQUISITION }}",
"field_392": "{{ PCN }}",
"field_376": {
"email": "{{ EMAIL_ADDRESS }}",
"label": "{{ EMAIL_ADDRESS }}"
},
"field_318": {
"job_posting_management": "{{ JOB_POSTING_MANAGEMENT }}",
"pcn": "{{ PCN }}"
}
}
Ability to import Applicants from the eCareer Applicant List (excel spreadsheet) to Edit Applicants page in Knack TPW Hire/Hiring Management/ Edit Applicants.
Current Process
HR.Digital.Interview.Hiring.Packet.-.Sample.1
Future Process
We are developing a TPW Hire application that is a centralized place to manage job posting information, that replaces the spreadsheet.
Requested enhancement
However, HR recruiters download a report from the eCareer website and need the ability to import a spreadsheet into a Knack table
job_applicants
as a front-end user.Old Interview Packet -
HR.Digital.Interview.Hiring.Packet.-.Sample.1
Knack - job_applicants
TPW Hire - Candidate Matrix