For Employees to initiate move requests using the Mobile Employee Experience (MEE), configure the request form in the Employee Completed Fields tab in the Authorization Template. This will appear based on the following:
User has the appropriate security access and
Employee Completed Tab
The Employee Completed Fields tab determine what fields are shown to the employee on the Mobile Employee Experience (MEE) and to internal users viewing the first step of the Authorization.
Employee Completed Fields
Click
to add a row in the Employee Completed Fields section. For a field to appear in the MEE, select a Table Name followed by a Field Name.
Note: Only specific tables and specific field types are supported.
Select Table Name from the drop down list which lists the Standard Authorization tables and Authorization User Tables that are supported.
Below is the list of Standard Authorization Tables which also includes the custom field tables associated with the standard auth tables:
Auth Stage Assignment
Auth Stage Assignment Employee Contact
Auth Stage Assignment Mailing Address
Auth Stage Spouse Domestic Partner
Auth Stage Assignment Cost Center
Select Field Name: Once a Table Name is selected, a drop down list of respective fields that are supported are displayed. Authorization/Assignment Custom Fields are supported if these are enabled Assignment-level custom fields that have their "Authorization Screen Available" setting checked
The following field data types are not supported are field with these types will not appear in the Field Name drop down list.
Standard Authorization Tables | Authorization User Tables |
Account | Account |
Audit Fields | Document |
Auth ID | Hierarchical Lookup |
Auth Group ID | Resource |
Company Segments (From and To Level) | Rich Text |
Computed Columns | Vendor |
Document |
|
Hierarchical Fields |
|
Read-Only Fields |
|
Resource |
|
Rich Text |
|
Vendor |
|
Is Required: Use the "Required" checkbox to require that the employee fill out a field prior to submitting the form. In the Mobile Employee Experience, fields will have a required indicator.
Field Section
Use the Field Section to organize the fields so that employees will see so that they better understand the purpose of the information, use the field section.
Click on the
to create new field sections. The Employee Entered Data Section Details will open.
Enter a caption and sequence as required.
All fields are listed in the Employee Entered Data Fields grid. Tick Include in Section checkbox and populate the Section Sequence to define the order in the MEE.
Note, only fields that are not configured to appear in a section can be configured to appear in the selected field section. Once a field is selected to appear in a section, it cannot be selected to appear in a different section.
Click
when done. Remember to click
on the Authorization Template screen.
Here is how the above example looks in the MEE.
Things to note:
When there are more than two fields in a section, the fields appear in two columns. Odd fields appear in the left column and even fields appear in the right column. In a mobile phone view, all fields appear in one column.
There are examples of fields in the data dictionary that are required by default and will appear as mandatory fields when selected to appear in the MEE but do not have the Is Required checkbox ticked. The "To City" field is an example in the screenshots above. To use a field that is required by default but should not appear as mandatory on the form, create a DDMO entry that specifically makes the field not required for User Type = External Employee.
When adding Mailing Address Fields, they will always show last in their section regardless of sequence number.
When you have an existing authorization template with the Employee Self-Start step and you need to add or remove fields, as best practice recommendation, please inactivate the existing template, make a copy of it and use the copied version to make updates (i.e. add or remove fields). The updated version should be used moving forward. This will ensure employees that have already submitted will keep the version for audit trail and new request will follow the new fields and configuration moving forward