What are the considerations for using the Embedded Application Task type in journeys?
The Embedded Application Task type reduces navigation and allows the user to complete application tasks by using the task regions embedded in a journey task.
For example, you can perform tasks by viewing these embedded application regions:
- Document Records embedded task region to upload your birth certificate.
- Address embedded task region to provide your home address.
- Family and emergency contacts embedded task region to provide your emergency contact details.
- Specific sections related to the Skills and Qualifications embedded task region. For example, Accomplishments section to update accomplishments and Licenses and Certifications section to provide certification details.
- Specific tasks related to the Compensation area. For example, Salary task to review salary and Shares task to review employee stock options.
Here's some points to consider when you use the Embedded Application Task type:
- Only the Redwood pages and regions that are displayed in the Embedded Application Task list of values (LoV) are supported.
- Attachments uploaded as part of the approval process don't get stored in document records.
- The completion criteria are specific to the task for which they are configured. Therefore, you need to configure the completion criteria for each embedded application task according to your requirement.
- You have configured a completion criteria for an embedded application task and also configured approvals for the same task. In this case, the task can be marked as done only after the application task is approved.
- You can view and manage data in an embedded application task based on your data security access for that application task.
- If you have personalized your standalone Redwood pages, the personalizations don't reflect when the page is embedded as a journey task.
- Fields that are hidden in the region by default will continue to be hidden in the embedded application task region. Additionally, fields that are visible in the region by default will continue to be visible in the embedded application task region. This behavior can't be modified currently.
- If you change the task type configuration after the journey is assigned to an employee, the assigned journey will retain the earlier task type. However, any journey assigned after the configuration change will use the new task type. For example, if you assign a journey after changing the task type from Application Task to Embedded Application Task, the employee will see the embedded application task in the assigned journey.
- The Skill Center section isn't supported for the embedded application task in journeys. Therefore, even if you configure the embedded task with the section, it won't be displayed on the Journeys UI.
- All seeded and customer defined sections are available in the Sections LoV when
you configure these embedded application tasks:
- Skills and Qualifications
- Talent Ratings
- If you have set up approvals for a section in the Skills and Qualifications embedded application task, you must not select the section when you configure the task. This is because approval-enabled sections aren't currently supported.
- Business rules are supported for these embedded application task fragments in
journeys:
- Name
- Demographic Info
- Document Records
- Family and Emergency Contacts
- National Identifiers
- Biographical Info
- Driver’s Licenses
- Phone
- Other Communication
- Address
- Citizenship
- Passports
- Visas and Permits
- Disability Info
- Assignment
- Contract
- Weekly Working Hours
- Seniority Dates
- Salary
- Individual Compensation
- Payment Methods
- Stocks
- Recurring One Time Payments
- Business rules aren't currently supported for these embedded application task
fragments in journeys:
- Skills and Qualifications
- Talent Ratings
This table shows the list of supported embedded application tasks and additional details
about them.
Embedded Application Task | Performer | Read Only | Supports Completion Criteria | Approval Triggered |
---|---|---|---|---|
Additional Compensation | Worker | Yes | No | Not applicable |
Line Manager | ||||
HR Specialist | ||||
Address | Worker | No | Yes | Yes |
Assignment Details | Worker | Yes | No | Not applicable |
Biographical Info | Worker | No | Yes | Yes |
Citizenship | Worker | No | Yes | Yes |
Compensation Change Statements | Worker | Yes | No | Not applicable |
Line Manager | ||||
HR Specialist | ||||
Contract Information | Worker | Yes | No | Not applicable |
Demographic Info | Worker | No | Yes | Yes |
Disability Info | Worker | No | Yes | Yes |
Document Delivery Preferences | Worker | No | No | Not applicable |
Document Records | Worker | No | Yes | Yes |
Driver's licenses | Worker | No | Yes | Yes |
Email details | Worker | No | Yes | Yes |
Family and emergency contacts | Worker | No | No | Yes |
Name | Worker | No | Yes | Yes |
National Identifiers | Worker | No | Yes | Yes |
Other Communication Accounts | Worker | No | No | Yes |
Passports | Worker | No | Yes | Yes |
Payment Methods | Worker | No | Yes | No |
Personal Contributions | Worker | Yes | No | Not applicable |
Phone details | Worker | No | Yes | Yes |
Recurring and one-time payments | Worker | Yes | No | Not applicable |
Line Manager | ||||
HR Specialist | ||||
Salary | Worker | Yes | No | Not applicable |
Line Manager | ||||
HR Specialist | ||||
Shares | Worker | Yes | No | Not applicable |
Line Manager | ||||
HR Specialist | ||||
Skills and Qualifications | Worker | No | No | No |
Talent Ratings | Worker | No | No | No |
Visas and permits | Worker | No | Yes | Yes |
Weekly Working Hours | Worker | Yes | No | Not applicable |
Worker Seniority Dates | Worker | Yes | No | Not applicable |