what’s new in microsoft dynamics™ ax 2009 – …hide\ax5\whats new in ax2009 tech.pdf · table...

$: WHAT’S NEW IN MICROSOFT DYNAMICS™ AX 2009 – …hide\AX5\Whats new in AX2009 Tech.pdf · Table of Contents i What’s New in Microsoft Dynamics™ AX 2009 0-1 E-Learning$
WHAT’S NEW IN MICROSOFT DYNAMICS™ AX 2009 – TECHNICAL

Microsoft Official Training Materials for Microsoft Dynamics ™ Your use of this content is subject to your current services agreement

February 2008 The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. © 2005 Microsoft Corporation. All rights reserved. Microsoft and Solomon are either trademarks or registered trademarks of Microsoft Corporation or Dynamics GP Software, Inc. or their affiliates in the United States and/or other countries. Dynamics GP Software, Inc. is a subsidiary of Microsoft Corporation. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.


Table of Contents

i

What’s New in Microsoft Dynamics™ AX 2009 0-1 E-Learning..........................................................................................................0-1 Instructor-Led Training .......................................................................................0-2 Training Materials...............................................................................................0-2 Certifications.......................................................................................................0-2 Learning Plans ...................................................................................................0-3 Elements of Training Materials for Microsoft Dynamics .....................................0-4 About This Training Material...............................................................................0-5

Chapter 1: General New Functionality 1-1 Objectives...........................................................................................................1-1 Introduction.........................................................................................................1-1 User Interface Refresh .......................................................................................1-2 Role Centers ......................................................................................................1-8 Workflow.............................................................................................................1-9 Contoso Demo Data Set ..................................................................................1-11 Summary ..........................................................................................................1-16 Test Your Knowledge .......................................................................................1-17 Quick Interaction: Lessons Learned.................................................................1-19 Solutions...........................................................................................................1-20

Chapter 2: Development Tools 2-1 Objectives...........................................................................................................2-1 Introduction.........................................................................................................2-1 Task Recorder....................................................................................................2-2 Role Centers ......................................................................................................2-4 Code Upgrade Tool Enhancements ...................................................................2-5 Cross Company Support ....................................................................................2-7 DateTime Date Type ..........................................................................................2-9 X++ SQL Enhancements..................................................................................2-10 Summary ..........................................................................................................2-11 Test Your Knowledge .......................................................................................2-12 Quick Interaction: Lessons Learned.................................................................2-14

Chapter 3: Workflow 3-1 Objectives...........................................................................................................3-1 Introduction.........................................................................................................3-1 Installing Workflow .............................................................................................3-2 Workflow Setup ..................................................................................................3-4 Developing a Workflow.......................................................................................3-5 Summary ..........................................................................................................3-17 Test Your Knowledge .......................................................................................3-18 Quick Interaction: Lessons Learned.................................................................3-19 Solutions...........................................................................................................3-20

Chapter 4: Enterprise Portal and Application Integration Framework4-1 Objectives...........................................................................................................4-1 Introduction.........................................................................................................4-1 Enterprise Portal Components ...........................................................................4-2


What’s New in Microsoft Dynamics™ AX 2009 - Technical

ii

Installing Enterprise Portal .................................................................................4-2 Role Centers and User Interface........................................................................4-3 Other Enterprise Portal Enhancements..............................................................4-3 Application Integration Framework Enhancements ............................................4-4 Summary ............................................................................................................4-7 Test Your Knowledge .........................................................................................4-8 Quick Interaction: Lessons Learned.................................................................4-10

Chapter 5: Deployment and Administration 5-1 Objectives...........................................................................................................5-1 Introduction.........................................................................................................5-1 Setup ..................................................................................................................5-2 Upgrades............................................................................................................5-5 Administration.....................................................................................................5-7 Summary ............................................................................................................5-8 Test Your Knowledge .........................................................................................5-9 Quick Interaction: Lessons Learned.................................................................5-11 Solutions...........................................................................................................5-12


Introduction to What’s New

0 - 1

WHAT’S NEW IN MICROSOFT DYNAMICS™ AX 2009

Training is a vital component of retaining the value of your Microsoft Dynamics™ investment. Quality training from industry experts helps keep you updated and develop skills to maximize the value of your solution. Whether choosing E-Learning, instructor-led training, or self-paced study using training materials, there is a type of training that meets your needs. Additionally, validate your training and demonstrate your expertise with one of many certifications for Microsoft Dynamics. Choose the training or certification type that best enables you to stay ahead of the competition.

E-Learning Online training for Microsoft Dynamics products helps increase your productivity without spending time away from your home or office. E-Learning allows you to learn at your own pace through flexible access to training, therefore proving beneficial for those lacking the time or budget to travel. E-Learning is composed of online training courses that are designed to cover detailed concepts on specific product areas and allow you to:

• Gain in-depth technical and business application training through daily on-demand training.

• Learn at your own pace; lessons can be stopped and restarted, skipped, or repeated.

• Save time and increase your productivity. • Receive product knowledge comparable to instructor-led

training without the need for travel or time away from the office.

• Gain beneficial training when preparing for Microsoft Dynamics certification exams.

• Find tips and tricks to show you how to increase productivity and save time.

• Learn about the changes in features and functionality of a new Microsoft Dynamics product version.

• Evaluate a new Microsoft Dynamics module or product.



0 - 2

Instructor-Led Training Instructor-led training helps you can gain a solid foundation or refresh your knowledge in Microsoft Dynamics products and processes while learning from an expert in an interactive environment. With courses on a variety of topics, you can:

• Follow demonstrations and attend presentations. • Receive hands-on product experience. • Participate in classroom activities and discussions with other

attendees. • Gain beneficial training when preparing for Microsoft

Dynamics certification exams.

Training Materials Training materials can be ordered for the purpose of self-paced study. These materials are comparable to courseware used with instructor-led training, and enable you to:

• Learn at your own pace, in your own time. • Refer to an abundance of tips, tricks, and insights. • Learn using a self-study format when preparing for

Microsoft Dynamics certification exams. For selected training materials, there is training material–local functionality available, which covers country specific features in the product. The training material–local functionality adds on to existing training materials and is designed to teach local functionality within a given country. Notice that training material–local functionality is used only in conjunction with the training material, not as stand-alone training materials.

Certifications Certifications help identify and distinguish an individual's technical skill set using a Microsoft Dynamics or related business product. Certifications for Microsoft Dynamics are widely recognized by industry employers and provide an objective validation of an individual's knowledge.



0 - 3

Organizations that employ certified individuals can benefit from a complete approach to learning; certified individuals have higher skills retention and increased productivity. Organizations can streamline their employee recruitment process and lower their external support costs plus downtime by maintaining technically skilled employees by requiring Microsoft Certified Business Management Solutions Specialist and Professional certifications.

Microsoft Certified Business Management Solutions Specialist The achievement of the Microsoft Certified Business Management Solutions Specialist certification demonstrates an individual's proficiency in one module of a Microsoft Dynamics or related business product. Microsoft Certified Business Management Solutions Specialists must pass a single certification exam for a Microsoft Dynamics or related business product to earn the title.

Microsoft Certified Business Management Solutions Professional The Microsoft Certified Business Management Solutions Professional is a premier certification where an individual has completed a pre-determined set of required and elective certification exams. These include certification exams for Microsoft Dynamics and related business products, as well as certification exams for other Microsoft technologies such as SQL Server. The pre-determined set of required and elective exams for this certification are focused on one of three specific knowledge areas— Applications, Developer, or Installation and Configuration—for one Microsoft Dynamics product. This certification demonstrates an individual's extensive knowledge of a Microsoft Dynamics product— more knowledge than what is needed to achieve a Microsoft Certified Business Management Solutions Specialist title.

Learning Plans Learning Plans can help you plan the best learning strategy for you and your organization. These plans illustrate module specific learning tracks that can be effortlessly targeted towards specific roles and also provide a learning track towards obtaining certifications. Learning plans can be found on both PartnerSource and CustomerSource.

NOTE: For more information on E-Learning, instructor-led training, training materials and certifications for Microsoft Dynamics, log in to PartnerSource or CustomerSource and visit Training & Certification.



0 - 4

Elements of Training Materials for Microsoft Dynamics Training Materials for Microsoft Dynamics products contain a number of sections or elements. Each chapter includes the following elements:

Objectives Each chapter begins with a statement of the learning objectives for that chapter. Learning objectives inform you about what needs to be done to successfully complete the chapter.

Introduction An introduction sets the stage for the learning to take place and prepares you with key statements of the chapter.

Topics Chapters are divided into topic areas, usually according to the learning objectives for the chapter. This is especially beneficial in large chapters so that the knowledge and skills to be learned are separated into more manageable units.

Test Your Knowledge The Test Your Knowledge section consists of review questions for each chapter or topic and is designed to help reinforce learning concepts. Questions can be short answer, true and false, multiple-choice, fill-in-the-blank, or any other type. Answers to questions are also provided.

Summary The summary wraps up the chapter by highlighting the important parts as well as providing a transition to the next chapter. The summary also offers an opportunity to refresh earlier learning.

Quick Interaction: Lessons Learned At the end of each chapter, you will find a Quick Interaction: Lessons Learned page. This interaction is designed to provide you with a moment to reflect on the material you have learned. By outlining three key points from the chapter, you are maximizing knowledge retention and providing yourself with an excellent resource for reviewing essential points after class.



0 - 5

About This Training Material Course Objectives The course is designed to equip course participants with the product knowledge, both at conceptual and functional levels, required when implementing and supporting Microsoft Dynamics AX 2009 at a wide range of wholesale and manufacturing companies.

Course Organization This course consists of the following chapters:

• Introduction

• Chapter 1: General new Functionality

• Chapter 2: Development Tools

• Chapter 3: WorkFlow

• Chapter 4: Enterprise Portal

• Chapter 5: Deployment & Administration

Description Microsoft Dynamics AX 2009 is an exciting new release that brings users new and improved functionality and a new user interface. This version introduces a number of new features in both the technical and application areas. This course provides information to help you recognize new features in Microsoft Dynamics Ax 2009. This course does not cover functionality that has not changed since the previous versions of Microsoft Dynamics AX 2009. It assumes course participants have baseline knowledge of the previous version. This course is not:

• Comprehensive training of the software. • Designed to prepare participants for any certification exam in

Microsoft Dynamics 2009. • Correcting errors from previously released content.

The purpose of this course is to introduce new features so that participants can learn about the main differences in the software since the last version.



0 - 6

Audience The intended audience is experienced systems consultants and systems developers typically working for a Microsoft Dynamics partner that is selling, consulting, implementing, and supporting Microsoft Dynamics AX 2009.

Prerequisites Before attending this course, students must have working experience with Microsoft Dynamics AX 4.0.

Certification Exams • None

Disclaimer

During the writing stage of the What’s New training content, functionalities in certain areas of Microsoft Dynamics AX 2009 were not fully implemented. An example of this includes the changes that are still occurring to the user interface. While the content has been approved and developed with the best knowledge, certain functionalities are still subject to change.



0 - 7

Student Objectives What do you hope to learn by participating in this course? List three main objectives below. 1.

2.

3.



0 - 8


Chapter 1: General New Functionality

1-1

CHAPTER 1: GENERAL NEW FUNCTIONALITY Objectives

The objectives are:

• Describe the new user interface in Microsoft Dynamics™ AX 2009. • Explain the purpose of Role Centers and Home Pages. • Describe the Workflow concept. • Review the structure and benefits of the new demo data set for

Microsoft Dynamics AX 2009

Introduction This course describes some of the general changes to Microsoft Dynamics™ AX 2009, including the redesign of the user interface, and the introduction of a new demo data company to improve user experience for demonstration and learning purposes.



1-2

User Interface Refresh Changes to the user interface have been made to:

• Better represent the Microsoft Dynamics brand (Powerful, Solid, Comfortable, and Compelling)

• Improve the user experience • Improve the learning experience • Leverage design concepts from Microsoft® Windows® Vista and

Microsoft® Office® 2007 • Introduce a new navigation model • Introduce an approval workflow process to allow better collaboration

around document processing

Breadcrumb Bar

The Breadcrumb bar (BCB) will be a new component that is added to Microsoft Dynamics AX 2009. The concept for this comes from Vista and, as the name implies, gives the user a “breadcrumb” trail of where in the program he or she has been and how to get back.

BCB allows the user to jump around or navigate to other areas in the system. The BCB is made up of two areas: travel buttons and the address bar. The address bar allows for navigation to other areas in the system, while the travel buttons allow sequential navigation backwards as well as forward when applicable.

FIGURE 1.1



1-3

Travel Buttons

Content Page history lists the travel buttons in Internet Explorer. Travel buttons of the BCB allow the user to go back to the previous page(s) as well as forward, if the user has gone to a previous visited page by means of the travel buttons. The other thing to note is that, the user can move directly to a previous page several levels back through the history drop-down arrow.

FIGURE 1.2

While the amount of history maintained is limited to the amount of the system's memory, this course only shows up to the previous ten items going backward or up to the next ten items, if navigated backward. This course does not maintain history across session.

Address Bar

The address bar allows for navigation to other areas in the system.

FIGURE 1.3

Command Bar

The command bar is intended to help users find the commands that are global to the workspace as well as commands that are applicable to the content page (in other words, the action pane).

FIGURE 1.4



1-4

Microsoft Dynamics AX 2009 menu is collapsed into a single menu that is found on the left side of the Client window.

Navigation Pane

The Navigation Pane is split into two parts.

• My Favorites • Area Page Link

FIGURE 1.5



1-5

My Favorites is a way to create shortcuts to forms, reports, and queries. As your list of favorite shortcuts grows, you can keep it organized by creating folders. To further organize your favorite shortcuts, create favorite groups.

Area Page Link lists the modules that you have permission to access. When you click a module in the Navigation Pane, the content area displays that module's area page. The Navigation Pane displays links to the area page, the available list pages, and other forms used with that module. From the Navigation Pane, you can quickly open modules, forms, and other pages.

Area Page

An area page is a Microsoft Dynamics AX 2009 navigation page that displays the contents of a module grouped into sections. Each Microsoft Dynamics AX 2009 module has one area page.

FIGURE 1.6



1-6

List Page

List Pages are used for finding a record and to initiate an action against that record.

The List Page consist of:

• An Action pane • A Filter pane • Data grid • A Preview pane • Visualizations

FIGURE 1.7

The List Page Filter Pane has the following features:

• Quick filter on selected field • Advanced filter uses and/or/operators • Save advanced search as personalization • Load task page filters • Application teams can define global filters in AOT



1-7

Action Pane

A Microsoft Dynamics AX 2009 action pane button is a control that represents a specific action. A button action is the task or operation that occurs when you click a button. Examples of button actions include opening another form, deleting a specified record, and printing a list of records.

FIGURE 2.8

The action pane uses the same button controls as other Microsoft Dynamics AX 2009 forms. When creating an action pane button, you populate properties that specify the appearance of the button, how it displays in the action pane, and the action that occurs when the button is clicked.

Filter Pane

To find and view an individual record or a group of related records, list pages include a filter pane. The filter pane contains the filter controls that you use to search all of the list page's records. The filter controls allow you to search a specified column for all records with a specified value.

FIGURE 1.9

To allow a search across more than one column, you must add additional filter controls. These additional filter controls allow your list page to support more complex searches.



1-8

Preview Pane

A list page can include a preview pane, which displays additional data about a specified record. The preview pane includes additional fields that allow you to view important information about a specific record without having to open the detail form of that record.

FIGURE 1.10

Role Centers Microsoft Dynamics AX 2009 includes customizable home pages called Role Centers. Role Centers display specific data, reports, alerts, and common tasks associated with a user's role in the organization. Users can access Role Centers from the Microsoft Dynamics AX 2009 client or from an Enterprise Portal Web site.

Role Centers

• Uses Enterprise Portal framework • Installs using Microsoft Dynamics AX 2009 setup • Uses SharePoint or MOSS Web parts • Uses SharePoint site for both EP and DAX client

Using Role Centers

A user profile is a set of default information for a specific role in an organization, such as Chief Financial Officer or Accounting Manager. The user profiles determine the content that is displayed on Role Center pages.

When a user is assigned to a profile, it specifies which Role Center the user sees when they open the Microsoft Dynamics AX 2009 client or an Enterprise Portal Web page.

Developers can create new role centers using the Homepage property.



1-9

Workflow In Microsoft Dynamics AX 2009, the term workflow is defined in two ways:

Workflow is a System

Workflow is a system that is included in Microsoft Dynamics AX 2009. The Workflow system provides functionality that can be used to create individual workflows, or business processes.

Workflow is a Business Process

A workflow represents a business process that defines how a document “flows” through the system by showing who must process and approve it.

Workflow Example

Consider the following illustration of an expense report workflow. This workflow shows who must process and approve expense reports.

FIGURE 1.11



1-10

To better understand this workflow, suppose that Shannon, a Machine Operator, submits an expense report for 7,000 U.S. dollars (USD). In this scenario, Lars, the Shop Supervisor, must review the receipts that Shannon routed to him. Then, Vince, the Operations Manager, and Sara, the CFO, must approve the expense report.

Now suppose that Shannon submits an expense report for 11,000 USD. In this scenario, Lars must review the receipts and Vince, Sara, and Phyliis, the Accounting Manager, must approve the expense report.

Workflow Benefits

There are several benefits of using the Workflow system in an organization. Here are a few key benefits:

• Consistent processes. The Workflow system enables managers to define the approval process for specific documents, such as purchase requisitions and expense reports. By using the Workflow system, managers ensure that documents are processed and approved in a consistent and efficient manner.

• Process visibility. The Workflow system allows managers to track the status and history of a specific workflow instance. This allows managers to analyze and determine if changes need to be made to the workflow to improve efficiency.

• Centralized work list. Users can view a centralized work list to view the Workflow tasks and approvals assigned to them. This work list is available from the Role Center pages in the Microsoft Dynamics AX 2009 client and Enterprise Portal.

Workflow Instance

A workflow instance is equivalent to a running workflow.

When a Microsoft Dynamics AX 2009 record is submitted to workflow:

• A combination of a workflow template and a workflow configuration are used to activate a workflow instance.

• Within the workflow instance, tasks and/or approvals are instantiated • Within each task/approval, a single step (task) or one or more steps

(approvals) are created to manage the handling of the workflow actions that can be taken.

• Within a step, one or more work items are created depending on how many Microsoft Dynamics AX 2009 users are assigned. Each work item creates a workflow notification that appears on a notification list.



1-11

The assigned Microsoft Dynamics AX 2009 user can then navigate to the form where he or she needs to take a workflow action, review the details, and then take an action and enter comments. This will cause the work item to be “completed,” and the associated workflow notification to be marked as completed, and eventually, the workflow action taken will cascade back to the workflow step, task/approval, and workflow instance.

Workflow Task

Microsoft Dynamics AX 2009 Workflow can be used to track documents or tasks from the start to the end of a work process. A workflow may contain one or many tasks; however, each task may only contain one step.

Tasks provide application-specific behavior that are defined in the AOT. Each task supports a single unit of work that is defined by one step. A task does not have a fixed outcome, but any number of custom outcomes can be added to the task, such as Completed or Skipped.

Workflow Approval

Approvals are specialized workflow elements designed to support approval scenarios. Approvals have a set of fixed outcomes that the workflow supports. The outcomes are as follows:

• Approve - Outcome type Complete. • Reject - Outcome type Return to the originator of the workflow. • RequestChange - Outcome type ChangeRequested from the

originator or another person in the workflow process.

Each approval outcome is associated with a specific Action Web Menu Item, Action Menu Item, and event handler. The Action Web Menu Item displays the action button name and dialog box when this action is selected from the Enterprise Portal work list or Enterprise Portal workflow controls. The Action Menu Item displays the action button name and dialog box when this action is selected from the unified work list or the client workflow controls.

Workflow Completed

When the final Workflow Task has been completed successfully, the Workflow is also completed.

Contoso Demo Data Set In Microsoft Dynamics AX 2009, a new demo data set for the company “Contoso Entertainment Systems (CES)” has been created to provide a wider range of data to support both legacy and new features, and to support the new multisite setup.

This data set will assist the instructor and learner when they perform demonstrations and learning about Microsoft Dynamics AX 2009.



1-12

Company Structure

Contoso Entertainment Systems (CES) started out as a family business in the 1970s when home stereo equipment was gaining popularity in the United States. Since then, CES has become a diverse global business headquartered in Seattle, Washington, USA.

The company structure of CES supports global sourcing, manufacturing, distribution and sales operations with multicurrency, intercompany trading, and consolidation.

Contoso Entertainment USA company (CEU) is the hub that consists of three production sites, including several warehouses.

• The first site manufactures high-end speakers and all of its components, and also serves as a backup manufacturing site for standard speakers to meet seasonal volume demands, as needed.

• The second site performs Home Theater System assembly. • The third site manufactures standard speakers.

The North American division procures raw materials, manufactures the sub-assemblies and finished goods, and then sells them to North American customers. It also sells the finished goods to Company Europe using intercompany trading. The business is a mixed make-to-order and make-to-stock model. The company occasionally uses sub-contractors to manufacture finished goods. The North American division plans and monitors the supply chain operations across all the divisions that include central forecasting and intercompany master planning. This company is also responsible for Shared Services, such as centralized payments and statements. Together with servicing North American clients, the division also offers project based product development and support based on unique client requirements.

Contoso Entertainment Europe company (CEE), situated in Germany, purchases finished goods from Company North America through intercompany trading. It also purchases some non-manufactured goods from vendors and suppliers in Europe, and distributes them to European customers. The business is a full package sourcing model with long lead times. Company Europe also services the finished goods for its European clients.

Contoso Entertainment Consolidation company (CEC), situated in USA, is a consolidation company that summarizes the financial information across all three divisions.



1-13

The following diagram shows the company structure and the sites.

FIGURE 1.12 CONTOSO ENTERTAINMENT COMPANY STRUCTURE

Product Catalog

CES sells a wide variety of products across their retail segments, store sales, wholesale sales, major accounts, and Internet sales.

The following diagram provides an overview of the product catalog.

FIGURE 1.13 CONTOSO ENTERTAINMENT PRODUCT CATALOG



1-14

The current product groups are as follows:

1. Speakers • High-end • Center Channel • Satellite • Subwoofer • Custom

2. Home Theater Systems

• 2.1 Channel • 5.1 Channel • Custom

3. Receivers

• 2.1 Channel • 5.1 Channel

4. Car Audio 5. Televisions

• LCD • Plasma • Projection • CRT (selling off existing inventory without additional purchases

planned)

6. Projectors • LCD • DLP • CRT

7. Digital Video Recorders and Players

• Standard DVR • High Definition DVR • DVD Players



1-15

8. Services • Installation • Maintenance and Repair • Professional Services

NOTE: All products mentioned are subject to change in the final demo data version

Most of the these CES products are purchased from vendors as finished goods and resold directly to its customers. These products include receivers, car audio systems, televisions, video projectors, and digital video recorders. However, CES produces two main types of audio speakers for home and commercial use to ensure superior quality of these items; these are their high-end, wood enclosure speakers, and their standard, plastic enclosure speakers. These speakers are produced at US based manufacturing sites. CES also kits the standard speakers (subwoofers, center channels, and satellites) together with procured receivers, into Home Theater Systems that are sold through retail outlets.

In addition to its tangible products, CES also offers installation, maintenance, and repair services.

CES also provides custom product configuration services so home theatre systems can be produced to the client's exact specifications. The customer can configure the items as they, or CES customer service representatives, enter the sales order.

The standard speakers, and many of the procured finished goods, are configured items, where a single item can be represented by different colors, sizes, and configurations. For example, the procured LCD television can come in two configurations of high definition and standard definition, three sizes of 37 inches, 42 inches, and 50 inches, and two colors of black and silver.

CES carefully monitors the quality of all its procured and manufactured items to ensure the satisfaction of its high-end customers.



1-16

Benefits of the Contoso Entertainment Company

The following list represents some of the benefits of the new Contoso Entertainment Company demo data set.

• The Contoso Entertainment company product catalog is easier for people to relate to, especially in Business Intelligence (BI) scenarios.

• The Contoso Entertainment company's product catalog enables extensive demos within Industry Solutions. For example, it is simple to build compelling scenarios around project and service that uses electronics installations.

• The Contoso Entertainment company's product catalog prepares for the extension to features in future Microsoft Dynamics AX releases.

Summary This course described some of the general changes to Microsoft Dynamics AX 2009, including the redesign of the user interface, the Workflow concept, and the introduction of a new demo data company to improve user experience for demonstration and learning purposes.



1-17

Test Your Knowledge Contoso Demo Data Set

1. What are the benefits of the new demo data set? (Select all that apply.)

( ) People can relate to it better, especially in BI scenarios. ( ) Enables the extension to demos within Industry Solutions. For example, it

is simple to build compelling scenarios around project and service using electronic installation

( ) Prepares for the extension to features in future Microsoft Dynamics AX releases.

( ) Provides a wider range of data to support both legacy and new features, and to support the new multisite set up.

User Interface

2. List some of the benefits of the new user interface. (Select all that apply.)

( ) Better represents the Microsoft Dynamics brand of being powerful, solid, comfortable, and compelling

( ) Improve the user experience ( ) Leverage design concepts from Vista and Office 2007 ( ) Improve the learning experience

Role Centers and Home Pages

3. Explain the purpose of Role Centers and Home Pages.



1-18

WorkFlow

4. List some of the benefits of Workflow. (Select all that apply.)

( ) Consistent processes: The Workflow system enables managers to Define the approval process for specific documents, such as purchase requisitions and expense reports.

( ) Process visibility: The Workflow system allows managers to track the status and history of a specific workflow instance.

( ) Centralized work list. Users can view a centralized work list to view the Workflow tasks and approvals assigned to them.



1-19

Quick Interaction: Lessons Learned Take a moment and write down three key points you have learned from this chapter:

1.

2.

3.



1-20

Solutions Test Your Knowledge

Contoso Demo Data Set

1. What are the benefits of the new demo data set? (Select all that apply.)

(√) People can relate to it better, especially in BI scenarios. (√) Enables the extension to demos within Industry Solutions. For example, it

is simple to build compelling scenarios around project and service using electronic installation

(√) Prepares for the extension to features in future Microsoft Dynamics AX releases.

(√) Provides a wider range of data to support both legacy and new features, and to support the new multisite set up.

User Interface

2. List some of the benefits of the new user interface. (Select all that apply.)

(√) Better represents the Microsoft Dynamics brand of being powerful, solid, comfortable, and compelling

(√) Improve the user experience (√) Leverage design concepts from Vista and Office 2007 (√) Improve the learning experience

Role Centers and Home Pages

3. Explain the purpose of Role Centers and Home Pages.

MODEL ANSWER - Role Centers and Home Pages are designed to help

increase usability for the individual user. Role Centers and Home Pages

displays specific data, reports, alerts, and common tasks associated with a

user's role in the organization.



1-21

WorkFlow

4. List some of the benefits of Workflow. (Select all that apply.)

(√) Consistent processes: The Workflow system enables managers to Define the approval process for specific documents, such as purchase requisitions and expense reports.

(√) Process visibility: The Workflow system allows managers to track the status and history of a specific workflow instance.

(√) Centralized work list. Users can view a centralized work list to view the Workflow tasks and approvals assigned to them.



1-22


Chapter 2: Development Tools

2-1

CHAPTER 2: DEVELOPMENT TOOLS Objectives

The objectives are:

• Describe the new Task Recorder feature in Microsoft Dynamics AX 2009

• Describe the new Role Centers feature in Microsoft Dynamics AX 2009

• Describe the Code Upgrade Tool enhancements • Examine Cross-Company Data Access. • Review the new DateTime data type. • Explain the X++ SQL enhancements

Introduction This course discusses the new features in Microsoft Dynamics™ AX 2009 that aid software developers in working with and programming to this product. These features include:

• Task Recorder • Role Centers • Code Upgrade Tool Enhancements • Cross Company Support • Date Time Support • X++ SQL Server Query Enhancements



2-2

Task Recorder The Task Recorder allows users to record their actions in Microsoft Dynamics AX, for example open a form, enter a value, or click a button and subsequently generate a document, presentation, or process diagram that describes those actions.

The documents that can be generated are training-oriented documentation in Microsoft Office® Word®, presentation content in Microsoft Office®

PowerPoint®, or process-oriented documentation in Microsoft Office® Visio®. For Microsoft Office Word and Microsoft Office PowerPoint documents, a template can be used for the document generation. The template can, for example, include company information and a logo. Possible uses of the documents are:

• Analyzing customer best practices • Documenting business processes • Creating control document • Documenting the use of customized solutions. • Documenting processes for customers’ employees. • Documenting bugs.

Using the Task Recorder

The following is an overview of the steps to record and document a process in Microsoft Dynamics AX 2009:

1. Open Task Recorder 2. Start recording. 3. Go through the sequence of actions in Microsoft Dynamics AX that

are to be recorded. For example, this may be how Microsoft Dynamics AX is used to handle the sales order process, from the initial creation of the sales order and until the order has been invoiced.

4. Stop recording and save the recorded actions. 5. Generate a document, presentation, or process diagram based on the

recording.

Scenario

Simon, the Systems Implementer, has been asked to document how Microsoft Dynamics AX is used to handle the sales order process, from the initial creation of the sales order until the order has been invoiced. Documenting a business process using the Task Recorder is accomplished by recoding a task and subsequently transforming the recording into a document.



2-3

Record a Task

To document how the sales order process is handled, Simon has to go through the individual steps in the task while recording.

1. Open the Task Recorder toolbar from the Tools > Start recording. 2. Create the sales order by opening the Create an electronic ICL

declaration form and creating the sales order header and one sales order line.

3. Print the picking list by opening the Picking list form, and then print the sales order picking list.

4. Print the packing slip by opening the Packing slip form and printing. 5. Open the Invoice form and print. 6. Click the Stop recording button on the Task Recorder toolbar. 7. Click Yes to save the recording and provide task name and a

description.

Generate Documents from the Recorded Script

After recording the sales order process, Simon now wants to generate a PowerPoint document presenting an overview of the process.

1. Open the Task Recorder toolbar from the Tools menu and click the Recorded tasks button.

2. Select the relevant task from the list of recorded tasks. 3. Click the Generate document... button. 4. Select the appropriate Microsoft Office PowerPoint template from

the Generate document form. 5. Click OK. 6. Microsoft Office PowerPoint will open and a presentation is

generated. 7. Save the presentation in an appropriate location.

Simon also wants to create a process overview. In the Recorded tasks dialog, he selects the same script, but in Document generator form, he chooses the Microsoft Office Visio format instead. When he clicks the OK button, Visio opens and a process overview is generated.

Finally, Simon wants to create a detailed document with instructions. In the Recorded tasks dialog, he selects the same script, but in the Document generator form chooses the Microsoft Office Word format. When he clicks the OK button, Word opens and a document is generated.



2-4

Role Centers Microsoft Dynamics AX has now included customizable home pages called Role Centers. Role Centers display specific data, reports, alerts, and common tasks associated with a user's role in the organization. Users can access Role Centers from the Microsoft Dynamics AX client or from an Enterprise Portal Web site.

A user profile is a set of default information for a specific role in an organization, such as Chief Financial Officer or Accounting Manager. The user profiles determine the content that is displayed on Role Center pages.

When a user is assigned to a profile, it specifies which Role Center the user sees when he or she opens the Microsoft Dynamics AX client or an Enterprise Portal Web page.

Role Centers Installation

Role Centers are deployed using Microsoft Dynamics AX 2009 setup.

To Install Role Centers and Enterprise Portal:

1. Insert the Microsoft Dynamics AX 2009 DVD into the drive. If the Microsoft Dynamics AX Setup Wizard does not launch automatically, double-click Setup.exe in the root directory of the DVD. If installing from a network location, share the installation files and connect to the shared location from the computer where the program will be installed.

2. On the Select maintenance mode screen, select Add or modify components and click Next.

3. Select Role Centers and Enterprise Portal, and then click Next. 4. Complete the installation wizard.

Role Centers Deployment

Complete the following procedures to deploy Role Centers on the Enterprise Portal Web server. After completing the following procedures, users can view Role Centers in either Enterprise Portal or the Microsoft Dynamics AX client.

Give Users Access to the SharePoint Site

After Role Centers and Enterprise Portal installation, the administrator will give users access to the Role Centers SharePoint site. If a user does not have access to the site, the user will receive an access error when attempting to view the Role Center page on either the Microsoft Dynamics AX client or in Enterprise Portal.

1. Open the Role Centers site in a Web browser. The default URL is http://server_name/sites/DynamicsAx.

2. On the Site Settings page, under Users and Permissions, click People and groups.



2-5

3. On the toolbar, click New > Add Users or New > New Group to add users or create a new group on the current site.

4. Assign users to SharePoint groups whenever possible to help minimize the amount of time spent administering individual user accounts.

5. It is possible to add all the members of an Active Directory group by entering the domain and group name as a new user. All authenticated users may be added by clicking the Add all authenticated users link on the Add Users page.

6. Grant each user or group permission on the site. To determine the desired user permissions, speak with the user's manager or group manager.

Import User Profiles

A user profile is a set of default information for a specific role in an organization. User profiles determine the content that is displayed on Role Center pages. Besides the standard profiles included in Microsoft Dynamics AX, administrators can create user profiles specific to their organization.

The file used for importing user profiles is in XML format. The simplest way to create a user profile import file is to export an existing user profile and use it as a template, making any necessary changes. Multiple user profiles can be included in a single import file. Once the import file is complete, the Administrator can use the Import button on the User profiles form to import the user profiles into Microsoft Dynamics AX.

Assign Users to Profiles

To specify which Role Centers the users see when they open the Microsoft Dynamics AX client or Enterprise Portal, the Administrator must assign the user to a user profile.

1. Open the User profiles form 2. Highlight the Profile ID 3. Click the Add User button 4. Select the User ID from the drop-down list 5. Select All companies or Select companies 6. Click on OK

After assigning users to a profile, those users must restart the Microsoft Dynamics AX client or refresh their Web browsers to view their Role Centers.

Code Upgrade Tool Enhancements Enhancements have been made to the Code Upgrade Tool to improve productivity during code upgrade by enabling access to conflicting customizations.



2-6

Upgrade Project

The upgrade checklist has a step to detect upgrade conflicts.

The code upgrade tool detects conflicts and produces projects with all conflicting elements.

Enhancements have been made in the following areas:

• Auto resolve simple conflicts for Properties on elements • Detect conflicts node by node. That way, it is less problematic for

the developer to find conflicts • Detect more conflicts types • Rerun option • Visual indicators • Progress tracking. The developer can mark conflicts as resolved

when they have been fixed.

Compare Tool

The compare tool shows changes between two versions of an element.

Enhancements have been made in the following areas:

• Information about the original (three-way compare) • Better handling of renamed nodes • Simplified access: Shortcut key + Moved to first level context menu

Estimation Report

When an upgrade project has been created, you can run the Estimate report to provide an overview of the amount of time the upgrade will take.

The estimate will be performed on default values for fixing different types of conflicts. These values can be changed to fit your skills and give a more reliable time estimate.

You have the option to set time for fixing the following conflicts so the Estimate report has values for calculation:

• Code • Property • Autoresolved property • Ordering • Overlayering • Deletion



2-7

You can also set additional estimates for:

• RecId and TableId relation missing • Field uses ‘recId’ and ‘tableId’ • Type extends ‘recId’ and ‘tableId’ • Record level security • Parameter validation • Use of dangerous API • Reference to unsigned .NET assembly • Validation of Display or Edit method

Cross Company Support This feature allows data from multiple companies to be displayed or edited with a single form. Microsoft Dynamics AX 2009 allow developers to make specific forms cross company and support the end user in working with cross company data.

To build a simple cross company form without any involved application logic, a developer sets the Form Datasource CrossCompanyAutoQuery property to Yes. This sets the form's auto query AllowCrossCompany property to Yes during form startup. The developer then needs to add the Company field to the grid and tab pages showing cross company data. The form's title and status bar show the company the form was opened in. Having a specific field for the Company lets the user know the company for the record. The typical form is now ready for use with cross company data.

A cross-company query returns data for several companies in a single run. A query does not have to be limited to returning data for the current session company. A cross-company query operates over all companies that you have read permissions for, or over a subset of companies that you specify.

How to Create a Cross-Company Query:

1. In X++, use the crossCompany keyword on the X++ select statement.

2. Set the allowCrossCompany property method to true on an instance of the Query class.

3. In the AOT, set the AllowCrossCompany property to Yes on a node under Query.



2-8

crossCompany Keyword on the X++ Select Statement

Create a cross-company query by using the crossCompany keyword on the X++ select statement. You have the option of adding a container variable of company identifiers immediately after the crossCompany keyword (separated by a colon). The container restricts the selected rows to those with a dataAreaId that match a value in the container.

The following code example populates a table buffer with all the BankAccountTable rows that have a dataAreaId of either cm1 or cm2. This example assumes that the user has authority to access data for these two companies. The first two dataAreaId values that are found will be printed.

static void JobDemoCrossCompany(Args _args)

{

BankAccountTable tabBAT; // saveDataPerCompany == true.

container conCompanies = [ 'cm1', 'cm2' ];

str sCompanyPrevious =" ";

int iCountCompanies = 0;

;

while select

crossCompany

: conCompanies

* from tabBAT

order by dataAreaId

{

if ( sCompanyPrevious != tabBAT .dataAreaId )

{

print( tabBAT .dataAreaId + " = tabBAT .dataAreaId" );

iCountCompanies++;

if ( iCountCompanies >= 2 )

{

break;

}

sCompanyPrevious = tabBAT .dataAreaId;

}

}

pause;

return;

}



2-9

Company Range Methods in AOT Reports

Override methods on the AOT report node to control the details of cross-company behavior. For example, you can override the report's init method with the following X++ code.

public void init()

{

super();

this .query() .allowCrossCompany( true );

this .query() .addCompanyRange( "dat" );

this .query() .addCompanyRange( "dmo" );

}

DateTime Date Type One Microsoft Dynamics AX Application Object Server (AOS) installation can meet the business needs of a company that has operations across multiple time zones including adjustments for Daylight Savings Time (DST). All date/time values are stored in Coordinated Universal Time (UTC).

When a date/time value is retrieved and displayed on a form, the date/time is shown in the user's preferred time zone. If the date/time value is edited and stored again, the value is converted from local time to UTC for storage.

Benefits of using DateTime

A DateTime data type is being added to the X++ language in support of applications features for storing and retrieving data from various time zones. This new type will be a combination of the existing Date and Time types and will be assignable from Date, Time, and str types.



2-10

The Microsoft Dynamics AX 2009 application is able to display the date time fields in the appropriate time zone, depending on either the client settings or on the time zone of the location. The time zone used will not depend on the AOS server time zone; the administrator can associate specific time zones with his or her Microsoft Dynamics AX companies and the application will use these time zones for all business processing.

static void Job1(Args _args)

{

UTCTimestamp myDateTime1;

;

myDateTime1 = 2007-10-20T14:31:55;

print myDateTime1;

pause;

}

In the United States time zone, the print myDateTime1 will look like this:

10/20/2007 02:31:55 pm

In the Danish time zone, the print myDateTime1 will give this result:

20/10/2007 14:31:55 pm

X++ SQL Enhancements Microsoft Dynamics AX X++ language supports various data access constructs to search, manipulate data, and build queries for SQL Server or Oracle database. Data search or manipulation can be performed on a row-by-row or set-based approach from X++. Though Microsoft Dynamics AX supports almost all of the SQL constructs today, many of these constructs have gaps in how they are implemented at the AOS data access layer. These gaps present problems for application programmers, causing them to create various work-around techniques that may impact the system performance and general productivity.

UPDATE_RECORDSET

The UPDATE_RECORDSET construct allows users to update multiple rows in a single trip to the database server. This allows certain tasks to be significantly accelerated by utilizing the power of the SQL Server. Upgrade scripts and various batch processes are the beneficiaries of this feature enhancement.

INSERT_RECORDSET

INSERT_RECORDSET now provides support for configuration key checks.



2-11

Order by and Group by

Currently, the order by and group by possibilities in X++ for either select statements or the Query framework are limited by the sequence of tables used in the statements. If tables T1 and T2 are joined, order by will come from T1 first and then T2. The fields in the order by cannot be mixed from T1 and T2 and cannot be reversed like, for example, ‘order by T1.F1, T2.F1, T1.F2’ or ‘order by T2.F1, T1.F1’. With this improvement in place, users may be able to consolidate different “flavors” of the same report into a single one. An example of this is Inventory management reports, where one can select order by item group and another version to order by inventory dimensions.

Row Count

Support row count after update_recordset and delete_from constructs. This feature introduces a new instance method that will return the row count impacted on a table when update_recordset or delete_from is issued. This allows the application programmers in various Microsoft Dynamics AX modules to do an update, assuming record(s) exists on a table, and not issue a “select” to see if a record exists.

Duplicate Key

The ability to catch duplicate key exception. The exception framework in X++ allows only the UpdateConflict exception introduced in Microsoft Dynamics AX 4.0 to be caught inside a transaction (ttsbegin..ttscommit). In a highly concurrent implementation, Microsoft Dynamics AX 4.0 postings in inventory and ledger modules tend to encounter another conflict type generated as part of an insert operation. These postings are required to proceed with an update if the record exists instead of rolling back the operation. Providing the “DuplicateKey” exception will allow the application programmers to achieve the same or ignore the error if the application logic allows it.

Summary Most, if not all, of the Microsoft Dynamics AX implementations around the world have some customization applied to the applications. The tools discussed in this course are designed to help the software developer or systems implementer to create and work with such customizations.



2-12

Test Your Knowledge Task Recorder

1. What is one task in your own business where you can use the Task Recorder?

Role Center

2. Describe, in one sentence, the purpose of the Microsoft Dynamics AX role centers.



2-13

Code Upgrade

3. List the three code upgrade tools discussed in this course.



2-14


1.

2.

3.


Chapter 3: Workflow

3-1

CHAPTER 3: WORKFLOW Objectives

The objectives are:

• Explain the installation and configuration of Workflow. • Review how to set up Workflow. • Describe Workflow from a Developer's point of view.

Introduction This lesson introduces the technical side of Workflow and discusses how to install and configure the components that are needed for workflow. The lessons and topics examine how to set up a Workflow with Tasks and Approvals, and finally how to develop a workflow in the Application Object Tree (AOT).



3-2

Installing Workflow Chris, the Operation Engineer, has to install and configure Workflow so that the Purchasing Manager can start to use this new feature. The core Microsoft Dynamics™ AX 2009 components have already been installed, therefore Chris only has to install the Workflow components. Chris must also create an Active Directory user for workflow.

Create Workflow System Account

The Workflow components on the Web server use the .NET Business Connector to communicate with the AOS. Chris must specify that the credentials the .NET Business Connector must use when logging into the AOS. These credentials are known as the Workflow system account.

Follow these steps to specify credentials for the Workflow system account.

1. Open the System accounts form, in one of the following ways: a. Click the System accounts option in the Initialization Checklist. b. Click the System accounts option in the Upgrade Checklist. c. Click Administration > Setup > Security > System accounts.

2. In the Workflow System Account area of the form, specify

credentials for the Workflow system account by entering a domain account, or by selecting an existing Microsoft Dynamics AX user account.

3. Click OK.

Create a Web site for Workflow

Chris must create a Web site for Workflow in Internet Information Services (IIS). During the Workflow installation, Chris will be asked to select this site.

The Web site created must be used only for Workflow. Other applications must not use this site.

NOTE: For instructions on how to create a Web site in IIS, please see the IIS documentation.

Install Workflow

1. Start the Microsoft Dynamics AX 2009 Setup program on the Web Server that will host the Workflow components

2. Select the preferred language for the setup wizard. Click OK. 3. The Microsoft Dynamics AX Setup wizard appears. Click Next. 4. Click Add or modify components on the Select maintenance page.

Click Next.


Chapter 3: Workflow

3-3

5. Select Workflow on the Select components page. Click Next. 6. The Identify the .NET Business Connector proxy account page

appears. The name of the proxy account must be displayed. Enter the password for the account. Click Next.

7. The Workflow: Configure IIS page appears. Select the Web site created in Create a Web site for Workflow. Click Next.

8. The Workflow: Specify an AOS account page appears. Enter the name of the AOS instance. If there are multiple AOS instances, specify the account each instance is running as. Use the following format for the account name: Domain\AccountName If an AOS instance is running as the Network Service account, then follow these steps: a. If the AOS instance is running on the same computer as the

Workflow Web site, enter: NT AUTHORITY\NETWORK SERVICE.

b. If the AOS instance and Workflow Web site are on separate computers, enter: Domain\ComputerName$. Click Next.

9. The Ready to install page appears. If IIS is to be restarted after the Workflow installation, select the Restart IIS after installation is completed check box.

10. Click Install to install Workflow. 11. After Workflow is installed, click Finish to close the setup wizard.

Verify the Workflow installation

After the Workflow installation is complete, verify that the Workflow Web site can be accessed.

1. Open the browser. 2. Enter the address of the Workflow Web site by using the following

format: http://ServerName:PortNumber/MicrosoftDynamicsAXWorkflow2009 a. ServerName is the name of the Web server where Workflow is

installed. b. PortNumber is the port the Web site is using. c. If the Web site is configured to use Secure Socket Layer (SSL),

use https instead of http in the URL.



3-4

Workflow Setup As part of setting up the Workflow system, it is necessary to run the Workflow Infrastructure Configuration wizard.

Run the Workflow Infrastructure Configuration Wizard 1. From a Microsoft Dynamics AX client, click Administration > Setup

> Workflow infrastructure configuration wizard. 2. The Welcome to the Workflow infrastructure configuration wizard

page appears. Click Next. 3. The Configure the Workflow Web server page appears. Enter the

URL of the Workflow Web site. a. If the Workflow Web site is using SSL, the URL is as follows:

https://ServerName:PortNumber/MicrosoftDynamicsAX2009. If the Workflow Web site does not use SSL, the URL is as follows:

b. http://ServerName:PortNumber/MicrosoftDynamicsAX2009. c. Click Validate to verify the URL. Click Next.

4. The Configure the Workflow processing batch job page appears.

a. If this new batch will be part of a batch group, select a group from the Batch group list.

b. Select a starting time for when the batch will run. c. Specify how frequently the batch will run by entering the

number of minutes in the Count field. d. To start the batch after completion of the wizard, select the check

box. Click Next.

5. The Configure the Workflow due date batch job page appears. a. If this new batch will be part of a batch group, select a group

from the Batch group list. b. Select a starting time for the batch. c. Specify how frequently the batch will run by entering the

number of minutes in the Count field. d. To start the batch after completion of the wizard, select the check

box. Click Next. e. Click Finish to close the wizard.


Chapter 3: Workflow

3-5

Developing a Workflow Developers use the AOT to create workflow templates. Workflow templates capture information about the following:

• Workflow categories (used for grouping and filtering in the UI) • What business document the workflow will operate over • What workflow elements (Tasks and Approvals) are required in the

workflow configuration • Which application event handlers will handle the events that are

raised as the workflow executes

Approvals are composed of workflow steps since they can have multiple steps. Elements have outcomes that are represented as buttons the user can select from when interacting with the workflow system.

Non-IT users will create workflow configurations. A Workflow Configuration is bound to a single Workflow Template, and there can be multiple Workflow Configurations for the same Workflow Template. Only a single WorkflowConfiguration for each WorkflowTemplate can be the default. The Workflow Configuration captures what tasks will be executed, who the tasks are assigned to, and how long it will take before a Task is escalated.

Workflow can be enabled throughout the various life cycle stages of a business document: Create, Update, Delete, Post, and so on. The Workflow runtime will execute the Workflow and assign Tasks to users. Users interact with the Workflow through a new unified Alerts/Workflow UI, from where they can take action (Approve, Reject, and so on) or they can browse to the business document and view all details before taking the workflow action from the business document form.

Workflow Owners will be alerted if a Workflow enters a faulted state. The owners will have an administrative UI from where they can inspect the stalled Workflow and determine how to correct the problem (Terminate or Resume).

The Workflow runtime will automatically track everything that happens in the Workflow as it is being executed.

Create a Workflow Template in AOT

In Microsoft Dynamics AX, developers can enable the workflow process for a workflow document by creating workflow templates that are used in the workflow configuration user interface.

A workflow template defines information about:

• Which workflow document to use. • Tasks and approvals that can be configured by the end-user.



3-6

• Workflow categories used for assigning a workflow template to a specific module.

• Menu items and event handlers.

The first step in creating a workflow is to add a workflow Template.

Isaac, the business software developer, right-clicks the “Workflow Templates” node in the AOT, selects “New template,” and names it “ExpenseReportApproval.”

Isaac sets the Label and HelpText on the property sheet.

Create a Workflow Category

When a workflow is created in Microsoft Dynamics AX, a workflow category must be created. The workflow category determines whether if a workflow template is available in a specific module.

For example, a workflow template for a customer invoice must not be available in the Master planning module. To make the workflow template available only in the Customer module, create a workflow category with the Customer module selected.

To create a workflow category:

1. In the AOT, expand the Workflow node. 2. Right-click the Workflow Categories node and then select New

Workflow Category. A new workflow category group displays under the Workflow Categories node.

3. Right-click the new workflow category and then click Properties. 4. In the Properties sheet, set the properties as required.

After a workflow category is created, it is possible bind the workflow category to a workflow template.

Create a Query

The Microsoft Dynamics AX workflow uses a query to expose document data to set up conditions for a workflow. The query identifies which document data is available to workflow users. This procedure describes how to create a query in the Application Object Tree (AOT), and if it is required, how to limit the number of data fields exposed for workflow conditions.

To create a query for a workflow:

1. In the AOT, right-click the Queries node, and then select New Query. A query group displays under the Queries node.

2. Right-click the new query, click Rename, and then enter a name for the query.


Chapter 3: Workflow

3-7

3. Expand the new query, right-click the Data Sources node, and then click New Data Source. A data source group named Address_1 displays under the Data Sources node.

4. Right-click Address_1 and then click Properties. 5. In the Properties sheet, set the Table property to the table that

contains the data for the business document. 6. The last step is to bind the query to the workflow template. In

workflow template Property sheet, set the Document property to the name of the query.

After a query is created, create a workflow document class. The workflow document class specifies the query name and if it is required, calculated fields.

Create a Workflow Document Class

The data that is used by a Microsoft Dynamics AX workflow is defined in a query. A limitation of a Microsoft Dynamics AX query is that calculated fields cannot be defined, for example, a dynamic sales total of all records in a table. Use calculated fields to define conditions for a workflow, for example, approvals based on total sales.

To define calculated fields, the workflow infrastructure provides the WorkflowDocument abstract class. The getQueryName method must be overridden to return the name of the query used in the workflow. Add calculated fields by adding parameter methods on the class. The following procedures show how to create a workflow document class, and optionally, add a calculated field.

class <MyWorkflowDocumentClassName> extends WorkflowDocument

{

}

QueryName getQueryName()

{

return querystr(<MyWorkflowDocumentClassName>);

}

Create a Workflow Task

Use Microsoft Dynamics AX workflow tasks to track documents or tasks from the start to the end of a work process. A workflow may contain one or many tasks. However, each task may only contain one step.

This procedure describes how to create a new workflow task in the Microsoft Dynamics AX 2009 Application Object Tree (AOT).



3-8

To create a workflow task:

1. In the AOT, expand the Workflow node. 2. Right-click the Tasks node and then select New Task. A new

workflow task group displays under the Tasks node. 3. Right-click the new task and then click Properties. 4. In the Properties sheet, set the following properties as required.

Create a Workflow Approval

Use workflow approvals to track the status of workflow document fixed outcomes such as “Approve”, “Reject”, or “Request Change.”

To create a workflow approval:

1. In the AOT, expand the Workflow node. 2. Right-click the Approvals node and then select New Approval. A

new workflow approval group displays under the Approvals node. 3. Right-click the new approval and then click Properties. 4. In the Properties sheet, set the following properties as required.

Create a Workflow Menu Item

After creating a task, approval, or outcome in a Microsoft Dynamics AX workflow, add it to a menu item. The end-user can start the task or approval by using the menu item as a part of the workflow process.

The following procedures describe how to add a task, approval, or outcome to an Action menu item, and then implement the class for the menu item.

To bind a task to an action or Web actions menu item:

1. In the AOT, expand the Menu Items node. 2. Right-click the ‘Action’ node, and then click New Menu Item. An

action menu item displays under the Menu Items node. 3. Right-click the new action menu item and then click Properties. 4. In the Properties sheet, set the properties.

Implement Providers

Use workflow providers to give application-specific information to a workflow instance at runtime. For example, use workflow providers to determine who has to approve an invoice, or by which date an invoice payment is considered late.


Chapter 3: Workflow

3-9

In Microsoft Dynamics AX workflow, there are three types of workflow providers that can be implemented, as shown in the following table.

Workflow Provider Description hierarchy provider Determines an end item given a particular start item.

due date provider Determines the day an item is due based on the start date.

participant provider Resolves a user group or role into one or more specific users.

Use the hierarchy provider to determine a specific end item, given a particular starting item. For example, it is possible to implement a hierarchy provider that determined the human resources representative for a specific employee.

The workflow infrastructure provides a default implementation of a hierarchy provider based on the organizational hierarchy available in the Microsoft Dynamics AX basic module.

Use a due date provider to determine a specific due date based on a particular starting date. The workflow infrastructure provides a default due date provider named WorkflowWorkCalenderDueDateProvider. To use this provider, set the DueDateProvider property on the workflow approval or task to WorkflowWorkCalenderDueDateProvider.

The default due date provider uses the general purpose calendar defined in the Basic module to resolve a time span into a date with consideration for non-workdays. For example, the default due date provider can determine the correct completion date for an expense report approval that must be approved within ten workdays. Any holidays or nonworking days configured in the Basic module calendar are automatically calculated into the approval completion date.

The WorkflowWorkCalenderDueDateProvider class implements the WorkflowDueDataProvider interface which contains the following methods:

• getCalenderTokens • resolve

The getCalenderTokens method is called when the workflow configuration user interface is rendered so that the user can select from the supported list of calendars. This method lists the calendar IDs defined in the Basic module Calendars menu item.

The resolve method is called on the execution of an approval step or task to determine the completion date of the step. For example, the configuration user must have an expense report approval within ten working days. When the approval step or task is executed, the due date provider's resolve method is called to return the actual due date.



3-10

The workflow infrastructure provides a default participant provider implementation that returns a list of users based on a Microsoft Dynamics AX user group. The default participant provider is named WorkflowUserGroupParticipantProvider. To use this provider, set the ParticipantProvider property on the workflow approval or task to WorkflowUserGroupParticipantProvider.

Implement a participant provider if a specific algorithm is needed for assigning work to users. For example, to load balance work, implement the WorkflowParticipantProvider interface that contains the following methods:

• getParticipantTokens • resolve

The getParticipantTokens method is called when the workflow configuration user interface is rendered. This method must return the list of supported participant tokens, such as role names, user group names, and so on. The resolve method is called on the execution of the actual approval step or task that requires a specific user. For example, the person who configures the workflow sets the approver of a step to Purchasing Manager. At the time that the specific approval step is executed, the participant provider's resolve method is called to return a specific purchasing manager.

Implement State Manager Class

As soon as the framework for the workflow template and approval are established, implement the various event handlers and other supporting types that are used by the workflow.

Define the ElementStateChangeManager.

The element state change manager is called by the event handlers to manage business state. This is basically a helper class that contains any implementation-specific information that is needed to manage state transitions for the workflow.

Note: State management can be implemented in many different ways. This design was chosen for simplicity of the sample.

1. Right-click Classes, point to New, and then click Class. 2. Name the class “ElementStateChangeManager”. 3. Right-click the ElementStateChangeManager class and then click

New Method.


Chapter 3: Workflow

3-11

Name the method “submit” and copy in the following code.

public static void submit(Common recordBuffer)

{

// elements is a table buffer for the Element table.

Elements elements = recordBuffer;

;

if(elements.RecId != 0)

{

// IMPORTANT: This section should validate the state transition.

elements.State = ElementStates::Submitted;

elements.write();

}

}

Create another new method, name it “start,” and copy in the following code.

public static void start(RecID _recID)

{

// Declare a table buffer.

Elements elements;

;

// Set the table to the record passed in

select forupdate issues where elements.RecId == _recID;

// if elements.RecID does not equal zero then the correct record is selected and the state can be changed.


{


elements.State = ElementStates::PendingApproval;

// Save the changes

elements.write();

}

}



3-12

Create another new method, name it “complete,” and copy in the following code.

public static void complete(RecID _recID)

{

Elements elements;

;

select forupdate elements where issues.RecId == _recID;

// if elements.RecID does not equal zero then the correct record is selected and can the state can be changed.


{


elements.State = ElementStates::Approved;

elements.write();

}

}

Workflow Event Handlers

At the workflow level, event handlers are provided for the workflow started, completed, canceled, and configuration data change events. Because there are no requirements to transition the document state in these event handlers, they can be implemented as required for the business logic. For example, the approval document state in a workflow that is started does not transition to Submitted until the user clicks the Submit button.

Event Description WorkflowStartedEventHandler This event raises when the

workflow instance starts.

WorkflowCompletedEventHandler This event raises when the workflow instance ends after it is completed.

WorkflowCanceledEventHandler This event raises when the workflow instance ends after it is canceled. Use this event handler to perform any cleanup operations needed.


Chapter 3: Workflow

3-13

Event Description WorkflowConfigDataChangeEventHandler This event raises when the

workflow configuration data changes. Use this event handler to determine when a configuration has changed. For example, when creating an association between a workflow and a workflow configuration, this event handler raises if the configuration was deleted or updated.

It is recommended that multiple event handler interfaces be implemented in a single class to reduce the number of classes shown in the Application Object Tree (AOT). For example, the following workflow event handler code example implements the Started, Completed and Canceled event handlers in one class.

public class PurchReqWorkflowEventHandler implements WorkflowStartedEventHandler, WorkflowCanceledEventHandler, WorkflowCompletedEventHandler

{

}

Task and approval event handlers are implemented at the workflow element level. Event handlers are provided for the following events:

• Started • Canceled • Completed • Returned • Change requested • Resubmitted

For tasks, only some of these event handlers will be implemented. For example, the started event handler must be used to transition the business document from the Submitted to the PendingApproval state.



3-14

For approvals, implement all the event handlers and use them to transition the state of the business document. One exception to this can occur when workflow has only one approver. In this case, transition the document state on the menu item instead. For example, change the document state from PendingApproval to Approved when the approver clicks OK on the form.

Event Description WorkflowElementStartedEventHandler This event raises when the

task or approval starts. For approvals, use this event to transition the business document from the Submitted state to the PendingApproval state.

WorkflowElementCanceledEventHandler This event raises when the task or approval is canceled. For approvals, use this event to transition the business document from the current state to the Canceled state.

WorkflowElementCompletedEventHandler This event raises when the task or approval is completed. For approvals, use this event to transition the business document from the PendingApproval state to the Approved state.

WorkflowElementReturnedEventHandler This event raises when the task or approval is returned to the originator. For approvals, use this event to transition the business document from the current state to RequestChange.

WorkflowElemChangeRequestedEventHandler This event raises when an approver requests a change to the task or approval. For approvals, this event must be used to transition the document from the “PendingApproval” state to the “RequestChange” state.


Chapter 3: Workflow

3-15

NOTE: The Return and ChangeRequested events share the same state in the recommended business state model. Implement these two events to distinguish between a workflow that is returned and a workflow that only needs a change. However, in both events, the behavior is the same in that a work item is created, and after the work item is complete, the business state is returned to Started.

It is recommended to implement multiple event handler interfaces in a single class to reduce the number of classes shown in the AOT. For example, the following approval event handler code example implements the Started, Completed, ChangeRequested, Returned and Canceled event handlers in one class.

Public class PurchReqApprovalEventHandler implements WorkflowElementCompletedEventhandler, WorkflowElementCanceledEventHandler, WorkflowElementReturnedEventHandler, WorkflowElemChangeRequestedEventHandler, WorkflowElementStartedEventHandler

{

}

Previously, the action menu item called IssueSubmitToWorkflow, was bound to the SubmitToWorkflowMenuItem property on the workflow template. In the following procedure, create and implement the class that will be used to start the workflow.

1. Create a new class and name it ElementsSubmitToWorkflow. 2. Add a main method and copy the following code into that method.

public static void main(Args args)

{

recID _recID;

CompanyID _companyID;

TableID _tableID;

WorkflowCorrelationID _workflowCorrelationID;

WorkflowTemplateName _workflowTemplateName;

WorkflowComment _initialNote;

;

_recID = args.record().RecId;

_tableID = args.record().TableId;

_companyID = args.record().DataAreaId;

_workflowTemplateName ="Element";

_initialNote ="";

// Initial note is what users type when they submit the workflow.

try

{



3-16

ttsbegin;

// Start the workflow

// TO DO - Save the correlation ID to use to cancel the workflow.

_workflowCorrelationID = Workflow::activateFromWorkflowTemplate(_workflowTemplateName, _companyID, _recID, _tableID, _initialNote);

// Set the workflow state to Submitted.

ElementStateChangeManager::submit(args.record());

ttscommit;

}

catch(exception::Error)

{

print "Error";

pause;

}

}

3. Select the ElementSubmitToWorkflow action menu item, right-

click and then click Properties. 4. Set the Object property to ElementSubmitToWorkflow.

Previously, an action menu item called ElementApprove was created and then bound to the ElementMenuItem property on the Approve outcome on ElementApproval. In this procedure, create and implement the class that will be used to approve the issue.

1. Create a new class and name it ElementApproveAction. 2. Add a main method and copy the following code into that method.

public static void main(Args _arg)

{

WorkflowWorkItemTable workItem;

;

ttsbegin;

if (_arg.menuItemName() =="ElementApprove")

{

select workItem where workItem.RefRecId == _arg.record().RecId && workItem.UserId == curuserid();

WorkflowWorkItem::takeAction(workItem.Id, 'Approve');

}

ttscommit;

}

3. Select the ElementApprove action menu item, right-click and then

click Properties. 4. Set the Object property to ElementApproveAction.


Chapter 3: Workflow

3-17

Summary This lesson explained the components that are required for the Workflow installation, and how Workflow is installed, and configured. Lessons and topics explained how to create and implement new Workflow elements. The lesson also contained basic explanations of the methods that are used in developing Workflow.



3-18

Test Your Knowledge Workflow Installation

1. Task: Chris has to install Workflow. The following are steps Chris will use to perform the Workflow install. Put the following steps in order:

Step _____ : Verify the Workflow installation

Step _____ : Create a Workflow system account

Step _____ : Create a Web site for Workflow

Step _____ : Install Workflow

Workflow Configurations

2. Which of following are true about Workflow Configurations? (Select all that apply.)

( ) A Workflow Configuration can be bound to many Workflow Templates. ( ) A Workflow Configuration is bound to a single Workflow Template. ( ) There can be multiple Workflow Configurations for the same Workflow

Template ( ) There can be only one Workflow Configuration for a Workflow Template

Workflow Problems

3. Which of the following are true about Workflows that enter a faulted state? (Select all that apply.)

( ) Workflow owners have an administrative UI they can use to inspect and correct the problem.

( ) Only Administrators are alerted if a Workflow enters a faulted state. ( ) Workflow owners have to contact an Administrator who will use an

administrative UI to inspect and correct the problem. ( ) Workflow owners will be alerted if a Workflow enters a faulted state.

Workflow Activation

4. In which of the following stages can Workflow be activated? (Select all that apply.)

( ) Create ( ) Update ( ) Delete ( ) Post


Chapter 3: Workflow

3-19


1.

2.

3.



3-20


Workflow Installation

1. Task: Chris has to install Workflow. The following are steps Chris will use to perform the Workflow install. Put the following steps in order:

Step 4 : Verify the Workflow installation

Step 1 : Create a Workflow system account

Step 2 : Create a Web site for Workflow

Step 3 : Install Workflow

Workflow Configurations

2. Which of following are true about Workflow Configurations? (Select all that apply.)

( ) A Workflow Configuration can be bound to many Workflow Templates. (√) A Workflow Configuration is bound to a single Workflow Template. (√) There can be multiple Workflow Configurations for the same Workflow

Template ( ) There can be only one Workflow Configuration for a Workflow Template

Workflow Problems

3. Which of the following are true about Workflows that enter a faulted state? (Select all that apply.)

(√) Workflow owners have an administrative UI they can use to inspect and correct the problem.

( ) Only Administrators are alerted if a Workflow enters a faulted state. ( ) Workflow owners have to contact an Administrator who will use an

administrative UI to inspect and correct the problem. (√) Workflow owners will be alerted if a Workflow enters a faulted state.


Chapter 3: Workflow

3-21

Workflow Activation

4. In which of the following stages can Workflow be activated? (Select all that apply.)

(√) Create (√) Update (√) Delete (√) Post



3-22


Chapter 4: Enterprise Portal and Application Integration Framework

4-1

CHAPTER 4: ENTERPRISE PORTAL AND APPLICATION INTEGRATION FRAMEWORK Objectives

The objectives are:

• Describe the major components that make up Enterprise Portal. • Review the Enterprise Portal installation process. • Examine the role centers and individual home pages available in

Enterprise Portal. • Identify additional Enterprise Portal enhancements. • Describe the Application Integration Framework enhancements.

Introduction Although neither Enterprise Portal nor the Application Integration Framework are new features in Microsoft Dynamics™ AX 2009, there are significant enhancements in both that warrants including them in this course.

Enterprise Portal is a collection of Web modules that gives you access to Microsoft Dynamics AX 2009 data and allows you to participate in business processes using Web-based forms. These modules and the portal system are built on Microsoft® Windows® SharePoint® Services or Microsoft® Office® SharePoint Server.

Application Integration Framework (AIF) enables companies to integrate Microsoft Dynamics AX 2009 and communicate with external business processes and partners through the exchange of XML over various transport media. AIF enables both business-to-business and application-to-application integration scenarios.



4-2

Enterprise Portal Components Enterprise Portal is a combination of several standard Microsoft technologies that extends the same user experience available in the Microsoft Dynamics AX 5.0 client to a Web-based portal. The major components include:

Windows SharePoint Services and Microsoft Office SharePoint Server Enterprise Portal in Microsoft Dynamics AX 5.0 requires either Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server.

.NET Business Connector Proxy Configuration Setup automates the process of configuring the proxy in various locations on the Enterprise Portal server. Setup prompts you for the proxy credentials when you install Enterprise Portal, and then configures the proxy credentials in the following locations:

• Microsoft Dynamics AX • Windows user groups • IIS • Microsoft® SQL Server®

IIS Setup automates the process of configuring security, ASP.NET, and application pools in IIS.

Site Creation and Deployment By default, when you install Enterprise Portal, Setup automatically creates an Enterprise Portal site, extends that site in Windows SharePoint Services or Office SharePoint Server, and deploys the site. For more information about creating and deploying an Enterprise Portal site, see the Microsoft Dynamics AX 2009 Enterprise Portal installation guide.

Installing Enterprise Portal Enterprise Portal is installed using Microsoft Dynamics AX 2009 Setup. Setup verifies if Internet Information Services (IIS) and either Windows SharePoint Services or Office SharePoint Server are already installed on the server. If these applications are not installed, Setup prompts you to install them. For more information about installing Enterprise Portal, see the Microsoft Dynamics AX 2009 Enterprise Portal installation guide.

IIS Setup automates the process of configuring security, ASP.NET, and application pools in IIS.



4-3

Site Creation and Deployment By default, when you install Enterprise Portal, Setup automatically creates an Enterprise Portal site, extends that site in Windows SharePoint Services or Office SharePoint Server, and deploys the site. For more information about creating and deploying an Enterprise Portal site, see the Microsoft Dynamics AX 2009 Enterprise Portal installation guide.

User profiles User profiles help to assign users to specific Role Centers. Microsoft Dynamics AX 2009 includes several default profiles that are defined for common roles. Customize these profiles or create new ones. For more information about Role Centers, see Administering Role Centers in the Microsoft Dynamics AX 2009 documentation. For more information about user profiles, see Manage user profiles for Role Centers Microsoft Dynamics AX 2009 documentation.

Role Centers and User Interface Microsoft Dynamics AX 5.0 and the Enterprise Portal framework include customizable home pages called Role Centers. Role Centers display reports and other business intelligence information, transaction data, alerts, links, and common tasks associated with a user's role in the company. Role Centers are available in both Enterprise Portal and the Microsoft Dynamics AX 2009 client.

The following enhancements have been made to the Enterprise Portal user interface:

• More interactive and responsive through the use of Asynchronous JavaScript and XML (AGAX) in the Web pages.

• Individual pages are refreshed when you click a link. • Actions can now be done on selected list items. You can see list

previews, and lists can be sorted, filtered, and grouped. Also, the list views can be changed.

• Accessing all Enterprise Portal pages is now consistent. • Enterprise Portal page layouts are dependent on Windows

SharePoint Services. • Multiple companies can be accessed through Enterprise Portal.

Other Enterprise Portal Enhancements Enterprise Portal also provides access to the following features in Microsoft Dynamics AX 2009 modules.

Expense Management Expense Management helps automate the processing of travel and entertainment expenses. It integrates with Financials and Project Accounting, and is available only with Enterprise Portal.



4-4

Returns Management Returns Management enables customers to initiate their own return processes using Enterprise Portal. Customers can print a return materials authorization document to enclose with their return shipments and track return statuses.

Purchase Requisition Purchase Requisition enables employees to enter requests for equipment, supplies, and other materials using Enterprise Portal. When the purchasing department approves a requisition, purchase orders automatically are created in the Microsoft Dynamics AX 2009 client.

Customer Relations Management (CRM) CRM provides the tools necessary to create and maintain a comprehensive set of data about customers and their information using Enterprise Portal. Employees can track information about prospective customers from the first point of contact, to customer purchases, to post-sale activities. CRM integrates with Financials and Supply Chain Management.

Service Management Service Management enables technicians to manage various aspects of their service requests using Enterprise Portal. Technicians can manage resource assignments, time tracking, customer history, future service plans, and resolution details.

Access to Multiple Companies Users who have access to multiple Microsoft Dynamics AX 2009 companies can use the company list to access the Enterprise Portal pages for another company, rather than having to open a separate Web site.

Application Integration Framework Enhancements Enhancements to Application Integration Framework (AIF) include the following:

• Create, read, update, and delete operations are now supported. • The programming model for AIF supports document services that

encapsulate business logic and are the interface between Microsoft Dynamics AX 2009 and external systems.

• AIF provides functionality for consuming external Web services from within X++.

• Performance improvements include the ability to scale up and handle more messages through parallel message processing and the addition of multiple AOSs.

• New document services for additional commonly-used documents.



4-5

Update and Delete

AIF now supports the ability to update and delete data in Microsoft Dynamics AX 2009 through document exchange. Two new actions enable the ability to update or delete a single record or multiple records. The Axd Wizard is now the AIF Document Service Wizard and enables developers to create custom documents that support updating and deleting data. The ability to update and delete data through AIF enables companies to fully integrate Microsoft Dynamics AX 2009 in their business processes.

Programming Model Changes

The document services can be customized by adding your own methods. Microsoft Dynamics AX 2009 now supports the ability to expose business logic implemented in X++ as Windows Communication Foundation (WCF) services. All services can be published though AIF asynchronous adapters or through WCF.

Documents are now exposed as services making them more flexible and customizable. Service operations can now be consumed from external AIF clients as well as directly from X++ code. In addition, AIF has been updated to enable developers to expose X++ business logic as WCF services. ASMX Web services have been replaced with WCF services enabling new functionality such as message encryption.

Consume Web Services

Microsoft Dynamics AX 2009 provides the ability to consume Web services from within X++. Creating a service reference to an external Web service generates a .NET service proxy that enables the service to be available through IntelliSense within X++. The external Web service can be consumed by Microsoft Dynamics AX 2009 using the .NET service proxy through Common Language Runtime (CLR) interoperablility.

Performance

AIF now supports the ability to scale up message processing when using the AIF adapters by adding AOSs. You can now define whether messages are processed sequentially or in parallel. If parallelism is implemented, messages can be processed in any order by multiple AOSs. After implementing parallel message processing, specific messages can still be designated for sequential processing.



4-6

New Documents

AIF includes support for an enlarged set of frequently used documents. Documents new to Microsoft Dynamics AX 2009 include the following.

Document Supported service operations (Create, Read, Update, Delete)

Address CRUD

Absence Request R

Bill of Materials (BOM) CR

Business Sector C

Cash Discount R

Contact Person CRUD

Credit Card C

Customer CRUD

Customer Group R

Customer Payment Journal C

Customer Quotation C

Expense Report CR

Fixed Asset CRU

Fixed Asset Condition R

Fixed Asset Group R

Fixed Asset Location R

Fixed Asset Major Type R

General Journal CR

Item CR

Item Dimension (Color) R

Item Dimension (Configuration) R

Item Dimension (Size) R

Item Dimension Combination R

Leads C

Payment Terms R

Product Groups R

Product Picking List C

Project Hour Journal C



4-7

Document Supported service operations (Create,

Read, Update, Delete) Return Order Acknowledgment R

Return Order Document CR

RFQ R

RFQ Reply C

Route Card C

Sales Confirmation R

Sales Quotation R

Sales Forecast DMP R

Service Agreement R

Service Order CR

Shipping Methods R

Transfer Order CR

Travel Card C

Unit R

Unit Conversion R

Vendor CR

Vendor Group CR

Vendor Payment R

Warehouse R

Work Center CR

Worker Attendance (In) CR

In addition to these new documents, the sales order document has been updated to support multi-site functionality as well as the ability to update and delete data.

Partners and customers can easily customize and extend the existing application programming interfaces (APIs) by using the Microsoft Dynamics AX 2009 software development kit (SDK). The SDK includes a new service wizard that developers can use to easily create their own custom document services.

Summary Although neither Enterprise Portal nor the Application Integration Framework are new features in Microsoft Dynamics AX 2009, there are significant enhancements in both.



4-8

Test Your Knowledge EP Components

1. List the components that Enterprise Portal is dependent upon.

Role Centers

2. What is the purpose of a role center?



4-9

EP Enhancements

3. List some of the other Enterprise Portal enhancements in Microsoft Dynamics AX 2009.

AIF Enhancements

4. List the AIF enhancements included with Microsoft Dynamics AX 2009.

New AIF Documents

5. List some of the new documents now available for electronic transfer using AIF.



4-10


1.

2.

3.


Chapter 5: Deployment and Administration

5-1

CHAPTER 5: DEPLOYMENT AND ADMINISTRATION Objectives

The objectives are:

• Describe the new features for installing and maintaining Microsoft Dynamics AX 2009

• Review the new features for upgrading Microsoft Dynamics AX 2009

• Examine what is new in administration for Microsoft Dynamics AX 2009

Introduction Part of the improvements to Microsoft Dynamics AX 2009 includes features specifically directed to help implementers and administrators to install, upgrade, and maintain Microsoft Dynamics AX.

The new Localized Installer can benefit implementers and administrators whose primary language is not U.S. English, and for users who have to have multiple versions of Microsoft Dynamics AX on their computers the new Side-by-Side Installation helps ease that installation process.

The Improved Service and Maintenance helps administrators keep Microsoft Dynamics AX 2009 current.

Upgrading to Microsoft Dynamics AX 2009 has improved by letting Customers to upgrade from two earlier versions. The upgrade process has been included as part of the batch process to help with the upgrade performance.

A new way to manage Time Zones will help improve product usability for companies that have users across multiple time zones, and a new Batch Job process has changed to help improve batch job performance and usability.



5-2

Setup This lesson describes the benefits of the new localized installer and how it can help companies who work in languages other than US English.

Next, an explanation of the new side-by-side installation for multiple version installations and how it can help users whose jobs require them to have multiple version of Microsoft Dynamics AX on their computers.

Finally, the lesson provides a description of the improved service and maintenance process and how it can help implementers and administrators keep their Microsoft Dynamics AX system up-to-date.

System Architecture

There are many changes to the new version. This topology diagram will show how the Microsoft Dynamics AX 2009 components work together with the Microsoft stack.

FIGURE 5.1



5-3

Localized Installer

In earlier versions of Microsoft Dynamics AX, setup features were available only in United States English. To accommodate the needs of a larger global market, Microsoft Dynamics AX setup features must be available in the language of different countries or regions. Now, with Microsoft Dynamics AX 2009 setup can now be run in some or all the languages offered within the Microsoft Dynamics AX application.

Microsoft Dynamics AX 2009 Installation

Simon is the System Implementer, whose first language is Spanish; he is therefore pleased to see that Microsoft Dynamics AX setup is now localized in his first language. His computer locale is set to use Spanish. Simon puts the Microsoft Dynamics AX 2009 DVD into his computer, the autorun screen opens, and the screens display in Spanish.

Simon then clicks a link to install Microsoft Dynamics AX 2009. The first screen prompts him for the setup display language, offering Spanish as the default. Simon accepts the default language by clicking Next, and when Microsoft Dynamics AX setup starts, the user interface shows Spanish text.

FIGURE 5.2

Side-by-Side Installation

In earlier versions of Microsoft Dynamics AX, it was possible to install more than one application on a computer; however, each application installation had to be in a separate root directory. Starting with Microsoft Dynamics AX 2009, installers can supply an application instance name and the installer will allow for both applications reside in the same folder.

During customization development for customers, partners frequently work in multiple versions of Microsoft Dynamics AX. Similarly, help desk personnel must be able to refer to several versions of Microsoft Dynamics AX to troubleshoot reported issues.



5-4

Partners who upgrade customers indicate that side-by-side support can be used during the upgrade process, and side-by-side installations are also useful for upgrade testing and data migration. The previously mentioned examples can be achieved by using separate hardware for each version, however, that can be both an inconvenience and an unnecessary expense.

Side-by-Side Installation 2

Customization development

Mort, the IT Systems Developer, develops the customizations for Fabrikam, but also does customizations for Northwind Traders and Global Trade & Manufacturing. All three companies are owned by the same parent company, but separate in every other way:

• Fabrikam is using Microsoft Dynamics AX 3.0 • Northwind Traders uses Microsoft Dynamics AX 4.0 • Global Trade & Manufacturing is starting with Microsoft Dynamics

AX 2009

Mort has only one development computer which already has both 3.0 and 4.0 versions installed and working. Mort receives the Microsoft Dynamics AX 2009 DVD, inserts it into his development computer, and starts setup. He is informed by the user interface that both 3.0 and 4.0 already exist on his computer, and that 2009 will be installed as a separate application.

Now Mort opens Microsoft Dynamics AX 3.0 when he has to do customizations for Fabrikam, Microsoft Dynamics AX 4.0 to work with Northwind Traders, and Microsoft Dynamics AX 2009 to work with Global Trade & Manufacturing.

Side-by-Side Installation 3

Another reason for having multiple version of Microsoft Dynamics installed is to be able to perform testing for upgrades.

Simon, the System Implementer, is sent to Northwind Traders to upgrade their production environment from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2009. He meets with Tim, the IT Operations Manager, who leads Simon to a computer that contains a single computer installation of Microsoft Dynamics AX 4.0, setup with Northwind Traders data and customizations, to test the upgrade.

Simon installs Microsoft Dynamics AX 2009 on the test computer and runs through the upgrade. After he troubleshoots any issues and verifies the data consistency, the system is shown as working satisfactorily. Now Simon is confident he can upgrade the production environment by using a similar process.



5-5

Improved Service and Maintenance

All components, other than the Application Object Server (AOS), reside in a single components installer (.msi) file so that most components can be patched by a single patch (.msp) file. Earlier versions of Microsoft Dynamics AX had multiple installer files that would require running the patch file multiple times. Combining the installer files into a single file will improve the Total Cost of Ownership for Microsoft Dynamics AX Customers.

Small-scale patch deployment Simon, the System Implementer, receives a Microsoft Dynamics AX Client patch from Sustained Engineering. He has only has two computers to apply the patch to, one with the Microsoft Dynamics AX Client and one with the .NET Business Connector. Simon manually runs the patch installer, first on the Client computer and again on the .NET Business Connector computer. After he is finished, both computers contain their respective fixes, installed from one patch installer.

Large-scale patch deployment Simon receives a Microsoft Dynamics AX Client patch from Sustained Engineering and has to roll the patch out to the 250 Microsoft Dynamics AX Clients in his production environment. In his development environment, Simon uses the Microsoft® Windows® installer command line properties to automate installation of the patch. After testing, Simon sends a link to the customized patch installer to the people who have to install the patch.

Kevin, the Sales Manager (one of the 250 employees), receives the e-mail and follows the instructions to start the patch installer from the provided location. After several moments, the installation is complete and Kevin's computer is set up with the new patch.

Upgrades The first part of this lesson explains the new multiple version upgrade feature and how it can benefit companies. The next part of this lesson will explain how adding upgrade as part of the batch process can benefit implementers and customers when they upgrade to Microsoft Dynamics AX 2009.

Upgrading Multiple Versions

Microsoft Dynamics AX 2009 is the first version with the ability to upgrade from more than one earlier version. The ability to upgrade to Microsoft Dynamics AX 2009 from 4.0 and 3.0 is a great advantage for both Customers and Partners.

The process for upgrading from Microsoft Dynamics AX 3.0 to 2009 resembles the Microsoft Dynamics AX 3.0 to 4.0 upgrade. The following provides an overview of the process:

• Prepare data for Microsoft Dynamics AX 2009 • Perform left justify on Microsoft Dynamics AX 3.0 data • Perform 64bit conversion for RecId



5-6

• Perform Unicode conversion • Move Microsoft Dynamics AX 3.0 data to Microsoft Dynamics AX

2009 database • Install Microsoft Dynamics AX 2009 and complete the upgrade

checklist

Multi-version Upgrade:

Simon, the System Implementer, wants to upgrade his customer's Microsoft Dynamics AX 3.0 (SP3 and greater) implementation to Microsoft Dynamics AX 2009. He installs Microsoft Dynamics AX 2009 and creates a new database, making sure not to start the AOS. He then follows the recommended process of prepping the Microsoft Dynamics AX 3.0 data for upgrade by running Left Justify, 64bit conversion, and Unicode conversion XPO's.

Simon uses database prep tool to move the data from Microsoft Dynamics AX 3.0 database to the newly created Microsoft Dynamics AX 2009 database. After moving the data he starts the AOS on Microsoft Dynamics AX 2009 and continues with the upgrade checklist.

Upgrade as Part of the Batch Process

The data upgrade process for Microsoft Dynamics AX 2009 has been modified to take advantage of the updated batch framework. A set of batch jobs are run on an Application Object Server (AOS) instance. Dependencies can be monitored between upgrade jobs by using the batch dependencies interface.

After the upgrade process starts, no active clients are required. By using the new test run functionality, the data upgrade process can complete with failures so that Implementers can find all error points in a single pass.

New batch framework provides the following improvements out of the box:

• Ability to run upgrade jobs on AOS • Ability to run upgrade jobs on multiple servers • No need for active clients open after upgrade is started • Parallelization achieved through number of batch threads • Centralized logging for better supportability and reporting • Constraint based dependency tree, used to continue on error/failure

Using the New Upgrade Batch Framework on the Server

Simon, the System Implementer, has started the upgrade process and the upgrade job starts to run for his Microsoft Dynamics AX 2009 implementation. Simon observes that he no longer has to have an active Microsoft Dynamics AX client open because the job is being managed at the server. An active Microsoft Dynamics AX client is needed only to start the upgrade and monitor the progress.



5-7

Administration This lesson explains the new time zone feature and how it can benefit companies that have users spread across multiple time zones. The next part will describe the improvements made to the batch job feature in Microsoft Dynamics AX 2009.

Time Zones

Earlier versions of Microsoft Dynamics AX did not support multiple time zones, without setting up an Application Object Server for each time zone. Otherwise, customers who have users spread across multiple time zones needed all the clients to use a single time zone.

Microsoft Dynamics AX 2009 supports multiple time zones without the need to set up an AOS for each time zone. Time zone preferences are set at the user level, and information in date and time fields is displayed in the user's preferred time zone. This is helpful for any customer who has Microsoft Dynamics AX users in multiple time zones.

All system Date and Time fields have been merged into DateTime fields that store values in Universal Coordinated Time (UTC). Microsoft Dynamics AX 2009 converts all DateTime data to UTC before saving it to the database. Microsoft Dynamics AX 2009 users can select a preferred time zone in which they want to view the DateTime data and the system will automatically convert the data into the user's preferred time zone when displaying it.

For Customers moving from an earlier version to Microsoft Dynamics AX 2009, the system date and time fields will be automatically merged and converted to UTC during the upgrade process. The Customer is asked to select a time zone to use as the source time zone for the data during the upgrade process. This time zone is then used to convert the stored data into UTC.

Batch Jobs

New in Microsoft Dynamics AX 2009 is the ability to run batch jobs on an Application Object Server (AOS) instance, without a client. The Batch Server can be set to run batch jobs at specific times for each AOS instance. Also, all running batch jobs in the environment can be managed from a single form. Dependencies between batch jobs have been improved so that Administrators can specify processing order and parallelism, plus any steps to take after batches have been run.

Batch Server Setup

Tim, the IT Operations Manager has been asked to set up an AOS as a batch server. The company is licensed for one AOS instance so, because of business processes, it can only be used as a batch server at certain times of the day. The AOS is available only for batch processing from 18:00 until 22:00 with a maximum of ten concurrent processes.



5-8

Set Up an AOS Instance as a Batch Server

1. Follow the path Administration > Setup > Server config. 2. On the Overview tab, verify that the Enable Batch check box is

marked. 3. Define the time that the AOS instance is available for batch

processing 4. Set the Number of batch sessions to 10. 5. Set the Exclusion Start Time to 22:00. 6. Set the Exclusion End Time to 18:00. 7. Close the form.

Summary This course explored the new Microsoft Dynamics AX 2009 features and how these features can help implementers and administrators to install, upgrade, and maintain Microsoft Dynamics AX.

The new Localized Installer can benefit people whose primary language is not U.S. English. Users who need multiple versions of Microsoft Dynamics AX can find benefit from the new Side-by-Side Installation. A new Service and Maintenance helps keep Microsoft Dynamics AX 2009 up-to-date.

Improvements to the upgrade will allow for Customers to upgrade from two earlier versions and including the upgrade as part of the batch process will help with the upgrade performance.

The new Time Zones will benefit companies with users across multiple time zones. Batch job performance has been helped by changes to the batch job process.



5-9

Test Your Knowledge Multiple Language Install

1. Simon is the system implementer; his first language is French and he is working on a computer set to the French locale. Simon wants to set up Microsoft Dynamics AX 2009 in his native, French language. What does Simon have to do after the setup autorun screen opens?

( ) Simon has to select French from the drop-down list. ( ) Nothing, the Microsoft Dynamics AX 2009 Setup program will

automatically select the language from the computer locale. ( ) The Microsoft Dynamics AX 2009 Setup program is available only in

English. ( ) Simon has to make sure he has the French version of Microsoft Dynamics

AX 2009.

Side-by-Side Install

2. A Partner has Microsoft Dynamics AX 3.0 and Microsoft Dynamics AX 4.0 installed on a computer but now has to install Microsoft Dynamics AX 2009. What steps must be taken to install the Microsoft Dynamics AX 2009 application?

( ) They must first create a new root directory for the Microsoft Dynamics AX 2009 application.

( ) Microsoft Dynamics AX 3.0 and Microsoft Dynamics AX 4.0 must be uninstalled first, and then Microsoft Dynamics AX 2009 can be installed.

( ) Just supply an application instance name and the installer will allow for installation of multiple applications.

( ) Starting with Microsoft Dynamics AX 2009, multiple applications cannot be installed on the same computer.

Service and Maintenance

3. True or False. Microsoft Dynamics AX 2009 has multiple install files which require running patch files multiple times.

( ) True ( ) False



5-10

Upgrades

4. Which of the following are true about the Microsoft Dynamics AX 2009 upgrade process? (Select all that apply.)

( ) Ability to run upgrade jobs on AOS ( ) Ability to run upgrade jobs on multiple servers ( ) An open, active client is needed after upgrade is started ( ) Constraint based dependency tree, used to continue on error/failure

Time Zones

Fill in the blanks to test your knowledge of this section.

5. Earlier versions of Microsoft Dynamics AX used these fields for storing time information. __________

6. Microsoft Dynamics AX 2009 uses this kind of field for storing time data. __________

7. In Microsoft Dynamics AX 2009 the date and time are converted and stored in this time. __________

Batch Jobs

8. Which of the following are new features for Batch Jobs in Microsoft Dynamics AX 2009? (Select all that apply.)

( ) Batch jobs run on the AOS without the need of a client. ( ) Each AOS can run batch jobs at a specific time. ( ) Administrators can specify additional steps to take after batches have been

run. ( ) All running batch jobs must be managed from their own form.



5-11


1.

2.

3.



5-12


Multiple Language Install

1. Simon is the system implementer; his first language is French and he is working on a computer set to the French locale. Simon wants to set up Microsoft Dynamics AX 2009 in his native, French language. What does Simon have to do after the setup autorun screen opens?

( ) Simon has to select French from the drop-down list. (•) Nothing, the Microsoft Dynamics AX 2009 Setup program will

automatically select the language from the computer locale. ( ) The Microsoft Dynamics AX 2009 Setup program is available only in

English. ( ) Simon has to make sure he has the French version of Microsoft Dynamics

AX 2009.

Side-by-Side Install

2. A Partner has Microsoft Dynamics AX 3.0 and Microsoft Dynamics AX 4.0 installed on a computer but now has to install Microsoft Dynamics AX 2009. What steps must be taken to install the Microsoft Dynamics AX 2009 application?

( ) They must first create a new root directory for the Microsoft Dynamics AX 2009 application.

( ) Microsoft Dynamics AX 3.0 and Microsoft Dynamics AX 4.0 must be uninstalled first, and then Microsoft Dynamics AX 2009 can be installed.

(•) Just supply an application instance name and the installer will allow for installation of multiple applications.

( ) Starting with Microsoft Dynamics AX 2009, multiple applications cannot be installed on the same computer.

Service and Maintenance

3. True or False. Microsoft Dynamics AX 2009 has multiple install files which require running patch files multiple times.

( ) True (•) False



5-13

Upgrades

4. Which of the following are true about the Microsoft Dynamics AX 2009 upgrade process? (Select all that apply.)

(√) Ability to run upgrade jobs on AOS (√) Ability to run upgrade jobs on multiple servers ( ) An open, active client is needed after upgrade is started (√) Constraint based dependency tree, used to continue on error/failure

Time Zones

Fill in the blanks to test your knowledge of this section.

5. Earlier versions of Microsoft Dynamics AX used these fields for storing time information. time and date

6. Microsoft Dynamics AX 2009 uses this kind of field for storing time data. datetime

7. In Microsoft Dynamics AX 2009 the date and time are converted and stored in this time. UTC

Batch Jobs

8. Which of the following are new features for Batch Jobs in Microsoft Dynamics AX 2009? (Select all that apply.)

(√) Batch jobs run on the AOS without the need of a client. (√) Each AOS can run batch jobs at a specific time. (√) Administrators can specify additional steps to take after batches have

been run. ( ) All running batch jobs must be managed from their own form.



5-14
