Skip to main content

Security development tool [AX 2012]

There is a new tool released.

The Security Development Tool for Microsoft Dynamics AX 2012 is intended to help you more easily create and maintain security artefacts such as roles, duties, and privileges. The tool displays entry point permissions for a given role, duty, or privilege. Additional tools guide you through updates of the access levels for entry points. You can also use the tool to test a newly created or modified security role, duty, or privilege from the same interface, without using a different test user account. Additionally, you can use the tool to record business process flows and identify the entry points that are used.




How to install and how to use instructions are on technet
Download with the icon on the left and watch a 6 minute video on the right.


Key features:
  • Grant access via an entry point (easy as right click and grant access by adding to a duty)
  • Create a new privilege from the same view
  • Test the security by clicking open new workspace - it will simulate the role and allow you to test with your own account 
  • Record the entry points and will be presented on the form. Which you can then click and grant access.
  • View the effect on your license (Enterprise, functional etc). See what menu item has an effect on your license. See which configuration key is attached to what menu item. What layer it is in. Licensing is huge. As one menu item may change a user from a functional user to a enterprise user. License affect could be thousands of dollars.
Main thing you have to understand is modifying security roles from the front end will modify the AOT security element. It will sit in the layer you are in.
Lastly but not least, when installed from the model provided it will sit in your usr layer. It is pretty cool as it is self-contained and doesn’t overlap with the sys layer.


 Other links:
http://dynamics-ax.blogspot.com.au/2012/03/ax-2012-security-development-tool-beta.html



Popular posts from this blog

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more