Description

In the FNO there are customer users, producer users, partner users and self register users. For example, if the producer user would like to become a customer user or any other user, users can update their existing producer user account to customer user account including the associated roles.

Use Case

Before converting an existing user to a different user type, ensure that the customer type account ID or any other account ID exists in FNO. Hint: In the SOAP request, keep the user details as it is. Just update the Account ID and Roles with REPLACE(OperationType) in the 'updateUser' request.

Users can find the latest version of the 'UserAcctHierarchyService' from the https://<siteID>.flexnetoperations.com/flexnet/services, where <siteID> is the site ID for your organization, supplied by Revenera. (for example, https://flex1234-uat.flexnetoperations.com/flexnet/services )

In the API tool such as SOAP UI or Postman, load the WSDL endpoint URL. The UAT URL format for version 2 is: https://tenantID-uat.flexnetoperations.com/flexnet/services/v2/UserAcctHierarchyService?wsdl, where tenantID follows the format flexNNNN (for example, flex1234).

Use Case 1: Move Producer user to Customer user

1. Primarily, the user 'test03@gmail.com' was seen under "Producer Users" tab. Before execution:

2. Webservice updateUser request to update the user type from one to another:

3. After executing the 'updateUser' request, 'test03@gmail.com' seen under "Customer User". 

Result: The "Producer User" has been converted to "Customer User".

Sample Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:v2.webservices.operations.flexnet.com">
<soapenv:Header/>
<soapenv:Body>

<urn:updateUserRequest>
<urn:userData>
<urn:user>
<urn:userName>test03@gmail.com</urn:userName>
<urn:primaryKeys>
<urn:firstName>Test03</urn:firstName>
<urn:lastName>User03</urn:lastName>
<urn:emailAddress>test03@gmail.com</urn:emailAddress>
</urn:primaryKeys>
</urn:user>

<urn:acctRolesList>
<urn:acctRoles>
<urn:account>
<urn:primaryKeys>
<urn:id>CUST100</urn:id><!--Account id:-->
</urn:primaryKeys>
</urn:account>

<urn:roles>
<urn:role>
<urn:primaryKeys>
<urn:name>SuperPortal Role</urn:name><!--Role name 1:-->
</urn:primaryKeys>
</urn:role>
<urn:role>
<urn:primaryKeys>
<urn:name>Software Engineer I</urn:name><!--Role name 2:-->
</urn:primaryKeys>
</urn:role>
</urn:roles>
</urn:acctRoles>

<urn:opType>REPLACE</urn:opType><!--OperationType:-->
</urn:acctRolesList>
</urn:userData>
</urn:updateUserRequest>
</soapenv:Body>
</soapenv:Envelope>

Hence, we can use this method to move user from one type to another.