Skip to main content
Version: FCP 25.11

Request Management

tip

Supported only in FCP-Suite and FCP-SE.

Request Management is used for data download approvals when the approval policy is enabled. All data download requests are initiated in the DM client, and approvals are performed in the Web UI.

Request Management in the Web UI​

Field descriptions:

  • Approval ID: Unique ID of the approval request.
  • Submitted at: Time when the request was submitted.
  • Updated at: Last modification time of the request.
  • Requester: The user who submitted the request.
  • Status: Current status. By default, only requests in approval are shown.

File Download and Approval​

File download and approval has two perspectives: the requester (regular user) who downloads files, and the approver who reviews the request. This section explains both.

Regular user: submit a download request and download files​

  • File downloads require the DM client because the Web admin UI does not support downloading. Click Download client at the top of the page to open the download page, choose the version for your OS, download, and install.
  • After installing the DM client, log in as a platform administrator and enable the approval workflow. Then, before downloading files, the user submits an approval request. After approval, the user can download the files.
  • Open the DM client, enter the platform address, username, and password, and click Log in. The user must have permission to access the Data Management list. Configure this in System Management > User Management.
  • After logging in, select the files you want and click Download.
  • A verification dialog appears. Click Download again to submit the approval request.
  • Click Request Management in the left navigation to view approval data.
  • Click an item to view request details.

Request detail fields:

  • Approval ID: Identifier used by approvers to locate the request.
  • Submitted at: Time when the request was initiated.
  • Updated at: Updated when the request is approved or rejected.
  • Requester: The user who submitted the request.
  • Status: Current approval/data transfer status.
  • Approval flow: Total number of approval steps.
  • Requested data: Data/files requested for download.
  • Approval history: Completed approval opinions, including approver, result, and comments.

After the approval flow is approved, the user goes to Request Management. When the status is Data move completed, click Download to start downloading files.

Status values​

  • Preparing data: Requested data is being copied from the requester directory to a staging area. After the copy completes, an email is sent to all level-1 approvers.
  • In approval: The request is in the multi-level approval flow. When it reaches a level, all approvers in that level receive approval emails.
  • Moving data: Approved requests wait for data to be moved from staging to a user-download directory. After the last approval level approves, an email notifies the requester that the request is approved.
  • Data move completed: The requester receives an email notification. Only in this status can the user download approved data from the DM client. Data in other statuses cannot be downloaded.
  • Rejected: The request was rejected.

Approver: review download requests​

Log in with an approver account. In Request Management, you can view requests in In approval status. Requests that display a pending action button require your review. To show all requests, remove the In approval filter.

Click an Approval ID to view details and add approval comments.

Request details:

  • Approval ID: Identifier used by approvers to locate the request.
  • Submitted at: Time when the request was initiated.
  • Updated at: Updated when the request is approved or rejected.
  • Requester: The user who submitted the request.
  • Status: Current approval/data transfer status.
  • Approval flow: Total number of approval steps.
  • Requested data: Data/files requested for download.
  • Approval comment:
    • Input: Enter comments, up to 120 characters.
    • Reject: Reject the request and end the approval flow.
    • Approve: If this is an intermediate approval level, approving moves the request to the next level. If this is the last level, approving marks the request as approved and ends the flow.
    • Approval history: Completed approvals with approver, time, and comments.

After you click Approve, the request moves to the next approver. If this is the last approval level, the system ends the flow, marks the request as approved, and emails the requester. After you click Reject, the system ends the flow, marks the request as rejected, and emails the requester.

Create and Use an Approval Cluster​

Create an approval cluster​

  • Step 1: Assign an approval subnet to users with approval permissions (administrators can skip this step)

    • In Cluster Management > Subnets, select the subnet to assign and click its name.
    • In Use permission, grant approvers read permission for this subnet.

  • Step 2: Create a cluster

    • Choose a None cluster.
    • Choose the approval subnet (if you cannot find it, contact an administrator).
    • Mount shared storage for the approval directory:
      • Address: The server that stores approval data. Contact the administrator for the server IP and directory.
      • Directory: After logging in to the cluster, open this path to view approval data.
        If mounting fails, contact Fastone support.

  • Wait until the cluster is created successfully, then log in via SSH or VNC.

View approval data​

  • Step 1: In Data Management > Approval management, find the approval ID you need to review.
  • Step 2: Log in to the cluster, open the mounted directory, and locate the approval data by approval ID.

After completing reviews, you can power off the cluster. The next time you need to view approval data, power on the node and reuse it. If you release the cluster, you must recreate it following the steps above to view approval data again.