Guidelines for Creating Role Centers

Microsoft Dynamics AX 2012 ships with 34 pre-defined user profiles. Microsoft
Dynamics AX users can be associated with any of these pre-defined profiles. It is
also possible to create additional user profiles to meet specific needs of users
within an organization.
In a role center, content is displayed inside SharePoint® web parts from a variety
of sources, as follows:

• Microsoft Dynamics AX

• Windows® SharePoint Services

• Microsoft® Office SharePoint Server 2007

The content should be specifically tailored for each role. Role centers in
Microsoft Dynamics AX should also meet the following criteria:• Simple and cleanly designed

• Simple to skim and read

• Aligned with the design guidelines

• Effortless to localize and customize

When creating a role center, follow these general guidelines:

• Identify the needs for a role. For example, consider the following:

o What information the role frequently needs to do the job

o Which information would help the role be more efficient at the  job

• Create content around the role's needs.

• Determine the best web part to display for each type of content.

• Validate the value of the role center with real users who match the role.

Prioritizing the content is imperative for a great user experience. Make sure that
critical content such as activities, work lists, key charts, and other important
components are visible at first glance and are clearly organized.
Tailor the content to be useful at a glance. The most important content should be
immediately visible at a screen resolution of 1280 x 800, without scrolling.
Web parts provide different formats for displaying data. Follow these guidelines
when creating web parts:

• Web parts should be organized in two columns.

• There should be at least four and a maximum of 10 web parts.

• The title of each web part in a role center should be in sentence case.

• All web part content should be sized appropriately. There should be
no scrollbars in the web part. All the content should be visible by
default.

• To maximize the use of vertical space, there should be no filter
controls (quick and advanced filters) displayed in a web part that
contains a grid.

• No error messages should be displayed by default in the web part.

An activities part contains data that is related to a user's relevant activities. When
creating activities parts, ensure the following:

• The activities part should have a title name that does not contain the
word "Cues."

• Each stack in the activities part should navigate to the appropriate list
page when it is clicked and it should have the same filter applied.
When a user navigates to that list page, it should also have the same
name as the activities stack title.

• The recommended number of stacks is six or fewer.



Regards,
Hossein Karimi