5.3.7 Request Information

Among the commands for request operations, the following command uses XML:

fscsm_request export (output of request information)

The format of the XML file corresponding to this command is explained below.

The elements of the XML are output using the following hierarchical structure:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<requests>
    <request>
        <requestId>Request ID</requestId>
        <requestName>Request Name</requestName>
        <requestType>Request Type</requestType>
        <applicantId>Applicant ID</applicantId>
        <requestStatus>Status</requestStatus>
        <requestProcesses>
            <requestProcess no="1">
                <requestRoute>role:bizSysProv_user</requestRoute>
                <passedDate>2016-03-02 14:32:33</passedDate>
                <passedRoute>user:userA</passedRoute>
            </requestProcess>
            <requestProcess no="2">
                <requestRoute>Information of Users Waiting for Request Operation</requestRoute>
                <passedDate>Date and Time of Request Operation</passedDate>
                <passedRoute>User Who Performed Request Operation</passedRoute>
                <comment>Comment Input When Request Operation Was Performed</comment>
            </requestProcess>
        </requestProcesses>
        <uibody>Details</uibody>
    </request>
</requests>

Element (Element Name or Element Name and Attribute)	Displayed	Output details
Element (Element Name or Element Name and Attribute)	Output	Output details
Request ID (requestId)	Yes	The request ID.
Request Name (requestName)	Yes	The request name is output as described below. "Request for <Operation> <Resource>" In <Resource>, the following values are entered: Menu Platform Service Organization User Project In <Operation>, the following values are entered: Adding Modifying Deleting
Request Type (requestType)	Yes	One of the following is output:
		Configuration Value	Requested Resources
		menus	Menus
		bizSystems	Platforms
		services	Services
		orgs	Organizations
		users	Users
		projects	Projects
Request ID (applicantId)	Yes	A user ID of the requester.
Status (requestStatus)	Yes	The current status of the request. One of the following is output:
		Configuration Value	Description
		running	Waiting processing
		completed	Approved
		canceled	Cancelled
		rejected	Rejected
		failed	Failed
Request Operation Number (requestProcess no)	Yes	As many requestProcess elements are output as the number of requests and approval types required for those requests. Request operation numbers are numbered and displayed in order according to the approval flow. "1" indicates a request and "2" and subsequent numbers indicate an approval.
Information of Users Waiting for Request Operation (requestRoute)	Yes	Outputs the information of users for whom request operations are performed. When requestProcess no is "1", the role ID of the requester is output in the following format in requestRoute: role: <Role ID of the Requester> When requestProcess no is "2" or later, the output format of requestRoute depends on the user type of the approving user. The format is as indicated in the following table.
		Displayed Value	Approval User
		role: <Role ID>	User belonging to planners or operators with the corresponding role. * When a request is made targeting multiple roles, these roles are output, separated using commas.
		org:<Organization ID>	User with the approver role of the corresponding organization
		project:<Project ID>	Project manager of the corresponding project
Date and Time of Request Operation (passedDate)	Yes	The date and time when a request was submitted or an approval was granted is output in the following format. This element is not output before the request is approved, rejected, or canceled. YYYY-MM-DD hh:mm:ss
User Who Performed Request Operation (passedRoute)	Yes	The ID of the user who performed request or approval is output as shown below. This element is not output before the request is approved, rejected, or canceled. user:<User ID>
Comment Input When Performing Request Operation (comment)	Yes	A comment entered during approval by the approving user. This element is not output before the request is approved, rejected, or canceled.
Request Details (uibody)	Yes	The details of the request are output in XML format. The XML format differs depending on the resource or operation targeted in the request, and it is same as the XML format used for the operation target resource for each resource. However, angle brackets in XML tags are output using the following escape characters: "<": "<" ">": ">" For details on the format of the XML, refer to the corresponding information in "5.3 Format of XML Files Used in Commands".