One moment please...
 
Untitled Document

What roles and rights are required to use the webservice of Exact Synergy Enterprise?

Under normal circumstances, to use the webservice, a user must have at minimum the Professional role, as well as any CRUD rights relevant for their webservice usage.

Each webservice entity will have up to 4 function rights defined(for custom/configurator entities it is possible the same function right will cover multiple actions and/or entities), each of which will be mapped to a specific CRUD action for that entity. For example, the standard entity Account uses function rights 616, 617, 618 and 619 to grant access respectively to Create, Retrieve, Update and Delete on accounts.

In a new ESE administration, no roles exist that contain CRUD rights. For testing purposes the Administrator role can be used (as that by default contains all roles and rights), but in a production environment custom roles need to be created that contain the CRUD rights that need to be granted to individual users.

Custom roles can be created by going to  System\Setup\Security\Roles. To add CRUD rights to a custom role, go to menu patch System\Setup\Security\Function rights, select the module Web services (12), select the desired function right, press Edit and then press the New button next to the Roles header. In Role, select the custom role you created. Level should always be Corporate. It is not possible to limit CRUD rights to a specific division. Setting CRUD rights to any level other than Corporate will simply result in CRUD requests being refused and queries not returning any data.

After all desired function rights are added to the custom role, the role can be added to any employees who need to access the web service by opening their employee card and clicking on the Add button next to the Roles header.

For standard entities, the function rights will be in the format Entity services <action>: <entity>, so for updating accounts it will be Entity Services Update: Accounts. For custom entities it may be necessary to inspect the function rights in the Repository explorer as their name may follow a different naming convention.

 

 

Document Number: 28.225.667

Disclaimer
Despite the continued efforts of Exact to ensure that the information in this document is as complete and up-to-date as possible, Exact can not be held accountable for the correctness and/or completeness and/or specific applicability of the published and/or requested information in this document. Exact shall not be liable for any direct, indirect, incidental, special or consequential damages, lost profits or for business interruption arising out of the use of this document. The extraction and use of information from this document remains at all times completely within the user's own risk.