Considerations for Using Embedded Application Task Type in Journeys

The Embedded Application Task type allows the user to complete application tasks and reduce navigation 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 for using 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.
  • 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 can view and manage data in an embedded application task based on your data security access for that application task.
  • Attachments uploaded as part of the approval process don’t get stored in document records.
  • Embedded journey tasks will use the approval rules that you have set up and not bypass them.
  • 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.
  • Only those embedded application tasks are supported where the worker is the task performer except for compensation-related embedded tasks.
  • If you have personalized your standalone Redwood pages, the personalizations don't reflect when the page is embedded as a journey task.
  • All seeded and customer defined sections are available when configuring the Skills and Qualifications embedded application task.
  • The compensation-related task data is read-only.
  • The document records that you submit from the Document Records embedded task region in Journeys will be routed for approvals if approval is configured. Additionally, you can view document records that are pending approval from the embedded journey task.
These are the supported embedded application tasks:
  • Additional Compensation
  • Address
  • Assignment Details
  • Biographical Info
  • Citizenship
  • Compensation-related application tasks
  • Contract Information
  • Demographic Info
  • Disability Info
  • Document Delivery Preferences
  • Document Records
  • Driver's licenses
  • Email details
  • Family and emergency contacts
  • Name
  • National Identifiers
  • Other Communication Accounts
  • Passports
  • Payment Methods
  • Phone details
  • Salary
  • Skills and Qualifications
  • Visas and permits
  • Weekly Working Hours
  • Worker Seniority Dates
The compensation-related application tasks are populated in the task setup UI based on the selected task performer. This table shows the embedded application tasks that the task performer can select in the task setup UI:
Task Performer Embedded Application Task
Worker Salary
Additional Compensation
Personal Contributions
Recurring and one-time payments
Shares
Compensation Change Statements
Line Manager and HR Specialist Salary
Additional Compensation
Recurring and one-time payments
Shares
Compensation Change Statements