emeadaxsupport: Modifying Retail POS permissions and operations
This article will explain how to link Operations with Permissions and Permissions groups as well as how to enable a Manager override prompt for certain operations.
To get started, lets first define each of the 3 entities:
On the Permission group form, there is an option for "Allow create order". When marked the cashier with this permission group can create customer orders at POS that also creates orders directly in AX. If we open the Operations form, you will see that Operation ID 620 is for Create customer order and this has a Permission ID listed is 1020. Right click on 1020 and select View Details. This will open the Permissions form and you will see that 1020 relates to allowCreateOrder. If you look at the Operations list again, you will see that Operation 621-Create quotation also has Permission ID 1020 listed. What this means is when you place a checkmark next to the field "Allow create order" on the Permission group form, you also gain access to "Create quotation".
On the Operations form you will notice that many of the Operations are listed with Permission ID's of 0. This means that everyone has access to perform those functions. If you would like to limit these operations you can choose a Permission ID from the dropdown to associate it to a field on the Permission group form such as Manager Privileges.
The Permission ID and Permission ID2 fields allow you to assign two different Permissions to the operation. For example, we can set the 500-Void transaction Operation with a permission of 1001-allowTransactionVoiding as well as the 1002-managerPrivileges. This means 3 things:
MANAGER OVERRIDE PRIVILEGES
The Manager privileges option can be confusing as one may assume that this means they would have access to all operations. This is untrue. Selecting Manger privileges on the Permission group form gives the user access to any Operation that has the 1002-managerPrivileges Permission assigned to it. Normally a manager would have most of the options marked on the Permission group form, thus giving them access to practically all functionality at the POS. Adding Manager privileges to any of the Operations will prompt a cashier who doesn't have direct permissions for Manager login approval before continuing.
You can also follow Shane's blog below to add custom manager approvals:
Adding Manager Approval to Custom Operations
OPERATIONS NOT LISTED ON THE PERMISSION GROUP FORM
You may have noticed that there are about 24 Permissions, but there are about 128 Operations. Many of these are left with Permission ID's of 0, meaning they are open for everyone to use. Keep in mind, as a cashier, I probably wouldn't have access to edit the POS buttons available to me and thus would not have access to all of these Operations such as "Minimize POS" unless someone made that available.
If you wanted to link additional Operations to the Permission group form, the out of the box solution would be to assign the Permissions in the Operations form to link it to an existing Permission Group field option. Let's take the 1017-allowReturn permission and 114 Return transaction Operation. These are not available on the Permission group form. If you would like to toggle the access to this Operation, you could link this with another field such as "Allow transaction voiding". So for Operation 114-Return transaction, assign Permission ID 1001. Now if a cashier's Permission group has the "Allow transaction voiding" marked, they can also process Return transactions.
The POS permission group is assigned to a worker at the Job level. To view this through Retail, go to: Retail >> Common >> Workers >> select a worker >> in the right pane, expand Position assignment and click on the hyperlink for the Job >> expand the Job classification fast tab >> view the POS permission group
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
|emeadaxsupport: AX user sessions hanging following changes to security||Blog bot||DAX Blogs||1||11.08.2020 10:20|
|emeadaxsupport: AX 2012 for Retail: Common practices and brief explanations for daily EPOS procedures and operations||Blog bot||DAX Blogs||0||11.04.2015 02:19|
|emeadaxsupport: AX for Retail 2012 R2: Password maintenance in the POS||Blog bot||DAX Blogs||0||18.01.2014 02:26|
|emeadaxsupport: Retail POS Technical Reference: Microsoft Dynamics AX 2012 Feature Pack||Blog bot||DAX Blogs||1||26.04.2012 06:11|
|emeadaxsupport: New Content for Microsoft Dynamics AX 2012 : October 2011||Blog bot||DAX Blogs||0||27.10.2011 17:11|
|Опции темы||Поиск в этой теме|