Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet

Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Wednesday, May 16, 2012

AX 2012 - Enterprise Portal Page Interaction Patterns

I hope everyone is doing good on this Wednesday! I wanted to write, and point out a great resource on Microsoft's MSDN that focus on AX 2012 - EP Page Interaction Patterns. This is a great resource for understanding the UX for EP, and the intended page interaction patterns set forth by Microsoft. When creating new pages, and extending a customers instance via Enterprise Portal, it is very important to have the same look and feel as the rest of EP.

With this in mind, lets check out the following resource page on MSDN: Page Interaction Patterns [AX 2012]

From the post.:
"The page types in Enterprise Portal work together to provide a consistent experience for the user. Some of the pages are displayed in the main browser window, although other pages are displayed in modal dialogs. The following diagrams describe the page interaction patterns for several common scenarios in Enterprise Portal. "

The page goes into walk through's that cover the six different page interaction patterns: View and Edit, Direct Edit, Edit with Additional Details, View and Edit Details, Two-phase Create and Create and submit to Workflow.

What I really want you to take away from this highlight post on this resource is two main points. The first being that of the resource itself so that you can become familiar with the desired page interaction types for EP. This is critical to understand to have valid design artifacts for projects and creating correct deliverable's and user experiences.

The Second point, is tied directly back to those design artifacts for projects. The page interaction type, and therefore this resource page, should be referenced in the design - as well as understood from the functional design point-of-view. Since the role and workload needs to be considered for the design of the deliverable, the page interaction type for such scope should be something that is determined early on.

This is why I think it's very important to understand these page interaction types. It has to be understood, and apart of the design process so that the custom scope that is being delivered fits into the rest of EP for AX 2012. I can't stress this point enough!

Well that's all for this post, but check back soon as I have up-coming book reviews, more on EP design and development, continued BI, and a whole lot more around AX 2012! Till Next Time!
Follow Me @:
RSS Feed  LinkedIn  Twitter

"Visit the Dynamics AX Community Page today!"

Labels: , , , , , , , , , , , ,


Post a Comment

<< Home

Copyright 2005-2011, J. Brandon George - All rights Reserved