User Request Business Process

Use the User Request business process to track the requests to update, deactivate, or create users in the system.

Characteristics

This is a Company-level business process with a workflow, provided in the system template.

Record Statuses

Status Resulting State
Canceled terminal
Completed terminal
Pending non-terminal

Workflow

The default workflow for the User Request business process is set up in a certain way; however, it may be used differently by your organization. Typically, a user with the necessary permissions can create the record and either move it directly to the end step or send it to others for review or approval. The recipients in the second step can approve or reject the record or send it on to others.

Creating a User Request Record

Create a User Request record by navigating to Information / General / User Request on the Company Workspace tab, or from the Tasks log on the Company Workspace or Home tab. Act on an existing User Request task that has been assigned to you from the Tasks log.

Complete the User Request form and attach related documents, if needed. After completing the form, select Send, and select an action in the Workflow Actions list to determine the next step in the workflow. Select Send to route the form to the next assignee.

Note:

You must enter a value in all required fields (*) before you can save the form.
  1. Go to the Company Workspace tab, and switch to User mode.
  2. In the left Navigator, select Company Logs, and then select User Request.
  3. On the User Request page, select Create. Refer to the tables below to complete the form. You can select Save at any time to save a draft version of the form. Draft versions are stored under Drafts.
  4. To add attachments, go to the Attachments tab, and select Attach Files"".
  5. After completing the form, select Send.
  6. On the Workflow Action Details tab, select who should receive this User Request.
    • If permitted, you can add users to the CC list. These users will receive a notification about this User Request but are not assigned a task.
    • If permitted, you can adjust task due dates for all users, or set individual task due dates for each assignee.
  7. Select Send.
  8. In the Notification window, review the content, and select OK.

    The record moves to the next step in the workflow.

Completing the User Request Form

Key Information

Field Name Access Description
User Request Type Required User request types include new, modify, or deactivate values.
External User Required Indicates whether the vendor (user) is not a Unifier user. If the vendor (user) is not a Unifier user, the Vendor field becomes required.

Details

Field Name Access Description
Groups Membership Required The permissions are granted to users, or groups, to allow them access to system features.
Reason Editable The reason for the user request

User Information

Field Name Access Description
User Editable Allows for selecting a Unifier user account
First Name Editable The user's first name
Last Name Editable The user's last name
E-Mail Editable The user's email address
Title Editable The user's title
Work Phone Editable The user's work phone number
Mobile Phone Editable The user's mobile phone number
Vendor Editable The vendor for the contract

Additional Attributes

Field Name Access Description
Employee ID Editable The ID of the employee
Role Editable Role (ID and Name) for the timesheet
Assigned Department Editable The assigned department
Manager Editable The manager of the person in the access request
Regular Hrs Editable Regular hours

Record Information

System information about this record

Field Name Access Description
Record Number Read-Only System-assigned record number
Status Read-Only Record status for a workflow BP record is based on the workflow action preceding the current workflow step.
Creator Read-Only Creator of this record
Creation Date Read-Only Date that this record was created
Record Last Update Date Read-Only Date that the record was last updated
Business Process Record URL Read-Only A shareable link to this record, for anyone with the necessary permissions