Hello,
Has anyone been able to use Transition Tasks to make a form that we could send to employees to ask them to confirm their current address, cell phone, personal email, emergency contact, etc.?
We use transition tasks for our Talent Acquisition module for onboarding paperwork but we didn't get much training on how the module works overall. I've tried making a form that would work for this but the data doesn't flow to the employee profile; I can only seem to use a transition task (outside of TA) to update delivered fields directly on Employee, like Sexual Orientation or Gender Identity. Phone Number (EmployeeContact), home address (EmployeeAddress), etc. don't seem to work because these fields aren't directly on the Employee business class.
What I've previously done is something like this:
- Create a TransitionContent, which includes text to display to the end user.
- Create a TransitionTask, which is the vessel by which the material is actually assigned to the user.
- Create/Add that Task to a TransitionProgram, which ultimately gets assigned to the user and carries the task to them.
I haven't found a way to make TransitionContent include fields to fill out, though. If I just want to give a candidate a simple Google-Doc-like form to type their phone number and have it go to their employee profile, I can't seem to find an easy way to do that?
For our candidate space, the fillable fields we use are all LPL-driven. We have to update ResourceTransitionTask.ContentAndInstructionsAction, create custom fields and then update an action configuration with Condition fields if we want to start collecting new data by adding a new field to one of our Tasks. This requires change control, dozens of custom fields, etc. and takes way too much time for this to be how this was designed to work.
An example form:
One of the fields on that form, used to display "Attendance/lateness and call out procedures":
And then here's the next statement beneath that, used to hold the manager's initials:
And then the manager/employee each take turns signing off on a bunch of these:
Then a custom action configuration turns this into a PDF after it's completed:
This data doesn't acutally feed to the employee profile, we just turn it into a PDF and put that PDF on the employee's Attachment section. But this is like 10 custom fields to have an employee sign off on the attendance policy; do we really need to configure LPL anytime we want to collect form data or am I approaching this incorrectly?
Has anyone found a way around this? Thanks for reading,
