Skip to main content

How to create and submit a new Self-Initiated Move in the Mobile Employee Experience

When the employee logs into the Mobile Employee Experience that is configured for Employee Self Moves, employees will be see a [Request a New Move] button.   Employees will be presented with just the

Updated over 2 weeks ago

When the employee logs into the Mobile Employee Experience that is configured for Employee Self Moves, employees will be see a [Request a New Move] button.

Employees will be presented with just the [Request a New Move] button if the employee has no assignments or active assignments records in the Equus Platform.

mceclip0.png

Employees with at least one active assignment record in Assignment will see "Requested Moves" in the navigation menu under active assignments. Click on the "Requested Moves" followed by "+ New Move" to proceed.

mceclip1.png

If multiple self-move forms (authorization templates) are available, the employee will first need to select the desired form and press [OK] to open the form.

mceclip2.png

If there is only one self-move form available, the form will automatically open. The form displays the configured fields on the Employee Completed Fields tab for that authorization template.

mceclip3.png

When all mandatory fields marked with

mceclip10.png

are populated, press the [Submit] button to submit a new self-move request. To cancel the request and return to the landing page, press [Cancel].

Things to note

  • Authorization templates configured for self-moves cannot be started by internal users. They can only be started by employees using the MEE.

  • The [Request a New Move] button and the "+ New Move" menu item honors the Relocation Term (Singular) system preference (RELOTERMSI).

  • The "Requested Moves" menu item honors the Relocation Term (Plural) system preference (RELOTERMPL).

  • The button only appears if the employee's company has at least one active authorization template with the <Employee Self-Start> control for step 1.

  • Once an employee submits a self-move request, an authorization is created and it behaves like a normal authorization in the system.

Did this answer your question?