09.12.2012 Views

ManageEngine ServiceDesk Plus 8.0 :: Admin Guide

ManageEngine ServiceDesk Plus 8.0 :: Admin Guide

ManageEngine ServiceDesk Plus 8.0 :: Admin Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>ManageEngine</strong> <strong>ServiceDesk</strong> <strong>Plus</strong> <strong>8.0</strong> :: <strong>Admin</strong> <strong>Guide</strong><br />

� If the 'reqDomainName' is empty, the user is identified based on the 'reqLoginName' with<br />

'reqDomainName' as an empty value.<br />

� If the requester does not fall under the above criteria, the user is identified based on the<br />

'reqEmailid'.<br />

� If the requester is unavailable in the above specified criteria, the user is identified based<br />

on the 'reqUserName'.<br />

� If the user cannot be identified from the above criteria, then the user is identified based on<br />

'userid'.<br />

� Based on the reqUserName or reqEmailId, if more than one users are identified then the<br />

user is not updated nor deleted.<br />

2. Login information of requesters cannot be edited through API.<br />

3. To enable 'Purchase Order Approver' role while editing a requester, 'email' should be<br />

specified along with 'approvePurchaseOrder' even if 'email' has been configured for the<br />

requester.<br />

4. Technician associated only to 'Not associated to any site' will not be allowed to create/edit<br />

requesters.<br />

5. If a technician with 'SD<strong>Admin</strong>' role provides values for 'techSiteName' and 'departmentName'<br />

which is unavailable in the database, then the requester is associated to the site and<br />

department specified in 'techSiteName' and 'departmentName'.<br />

6. If a technician with restricted access permission provides values for 'techSiteName' and<br />

'departmentName' which is unavailable in the database, then the requester is associated to<br />

'Not associated to any site'.<br />

The sample form to update requester can be accessed here.<br />

The requester details are updated successfully indicated with a Success message in the xml form.<br />

Delete Requester<br />

The details necessary for deleting a requester should be set in HttpRequest parameters and<br />

Httprequest parameter value for operation attribute should be 'Updaterequester'.<br />

targetURL=<br />

Attributes Comments<br />

"/servlets/requesterOperationServlet"<br />

target url for deleting requester<br />

operation='Deleterequesters' operation command for deleting requester<br />

name requester Name<br />

loginName Requester's loginName<br />

domainName Requester's login domain name<br />

emailId Requester's emailId<br />

userid Requester id<br />

username Login Name for SDP Authentication<br />

password Password for SDP Authentication<br />

DOMAIN_NAME Domain Name to which the user belongs.<br />

logonDomainName Authentication Mode [AD or Local Authentication].<br />

“AD_AUTH” refers to Active Directory Authentication.<br />

“Local Authentication” or empty value refers to Local<br />

Authentication.<br />

ZOHO Corp. 523

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!