Dynamics 365 For Talent, game changing cloud app for end to end HCM and Talent Management from Microsoft

Check out the features coming in Dynamics 365 for Talent

Microsoft Dynamics 365 Blog

The date for the general availability for Dynamics 365 For Talent is nearing !! The Technical Preview is out now and you can get your hands on it to realize the tremendous potential and capabilities this new app brings out of the box, to help manage the end to end Human Capital Management (HCM) and Talent management functions of your organization.

D365 For Talent Tech Previewq

I have been evaluating this upcoming app for sometime now and I did play around the Technical Preview environment also. I would like to share some of my observations and how I think it will benefit for customers who already have subscribed to Dynamics 365 Enterprise edition and customers who are evaluating Dynamics 365 for their organization.

Note: In this post, I don’t intent to go deep into exploring features and functionality. I will do that later in future posts after General availability.

Take a quick look at the video below to get…

View original post 841 more words

Purchase Order Approval Workflow with Dynamics 365

By Adrianne Johnson, Socius

Workflow Overview

Workflow is a representation of a business process that defines who must complete a task, make a decision, or approve a document. Benefits of using workflows include consistent, to ensure documents are processed and approved in a consistent and efficient manner, processes visibility, which allows for tracking the status and history of a specific workflow.

Fig 1Figure 1: Workflow History

Users can view a centralized work list to view all workflow tasks and approvals assigned to them. In the Dynamics AX client, users can access their work list from the Role Center. In D365 for Operations, users can view their work items on the Dashboard, or through the Common module (Common> Work Items).

Procurement and Sourcing Workflows

Procurement and Sourcing workflows allow for purchase requisitions and purchase orders to be approved by a user other than the person who created the transaction. They provide the ability to track/limit spending, such as requiring approval if an order total is above a set amount. Automatic Actions can be set to automatically complete an action (approve, reject) if a certain condition is set. For example, automatically approve purchase order lines if the net amount is under $50k.

To ensure workflow is enabled when submitting a purchase order two setup steps are required.

    1. Procurement & Sourcing parameters must have “Activate Change Management” functionality turned on.
    2. At least one active Procurement & Sourcing workflow must be set up.

Fig 2Figure 2: Procurement & Sourcing Workflows

Purchase Order Workflow Scenario

For this example we will create a simple Purchase Order Workflow that requires review and approval if the total is $50,000 or more. If the purchase order is less than $50,000 the purchase order will be automatically approved. Purchase Orders that require approval will be routed to a specific user.

To create our workflow we will navigate to Procurement and Sourcing > Setup > Procurement and Sourcing Workflows. Select New > Purchase Order Workflow. When prompted sign in using your organization credentials. The Workflow editor will open.

Please note you may have to complete a onetime download of the workflow editor. Instructions for completing the download can be found here.

Workflow Editor

The workflow editor is a graphical user interface (GUI) that you can use to create Dynamics 365 Operations workflows by arranging workflow elements on a design surface. You can add, delete, and reposition elements that represent the tasks and approvals that make up the workflow. You can also add flow-controls, such as manual decisions, automated decisions, and parallel activities. As a result, you can create complex workflows that exactly model the business processes that you want to automate. This TechNet article can be review to understand the foundation of the workflow editor.

Fig 3Figure 3: Workflow Editor

Workflow Properties

To configure the properties of a workflow, open the workflow in the workflow editor. Click the canvas of the workflow editor and then click Properties to open the Properties form. Give the workflow a name such as Purchase Order Workflow. Update the owner if necessary.

Workflow Elements

On the far left side of the workflow editor you will find a list of workflow elements. Dynamics 365 for Operations offers various workflow elements that can be used to create the workflow to match the organizations business process.

Workflow elements for the purchase order workflow include:

  • Approve Purchase Order – Workflow step that allows for approval of the entire Purchase Order
    • The Approve Purchase Order, editable elements offers the same properties as the approval step along with allowing the approver to make changes to the purchase order before approving the purchase order
  • Conditional Decision – Allows for a visible condition and breakout of multiple paths in the workflow
  • Manal Decision – Allows for a visible condition and breakout of multiple paths in the workflow that the user must select from outcomes selected in the workflow
  • Parallel Activity – Allows for Two workflow activities to occur at the same time
  • Sub Workflow – Allows for a workflow to be embedded into this workflow
  • Review Purchase Order – Task the requires workflow activity, but is not recorded as an approval
    • This step is sometimes used by accounting to verify the correct financial dimensions are selected on purchase order lines
    • The Review Purchase Order, editable elements offers the same properties as the review step along with allowing the reviewer to make changes to the purchase order before completing the review

For this workflow we will utilize the Review Purchase Order and Approve Purchase Order workflow elements.

Fig 4

Workflow Creation

To build the workflow start by dragging and dropping workflow elements to create the workflow process.

  1. Click and hold the Review Purchase Order step and drop it under Start
  2. Click and hold the Approve Purchase Order step and drop it under Review
  3. Drag from Start to workflow element to End to connect all steps. Workflow should look like the picture.

You can utilize error pane to recognize additional configurations that are needed to configure the workflow. Errors will be removed as we complete the configuration of the workflow. Fig 5

Element Properties

Now that we have our workflow elements selected we need to configure additional settings for each element. You’ll notice that the review element has a red x in the upper right corner. This signals that there are additional configurations that need completed. Once all configurations are set the red x will be removed.

Basic Settings

In this tab you can update the name of the element and insert work item subject and instructions. Work item subject and instructions can be viewed by users who submit requisitions for processing.

  1. Click the Review step and then click properties in the ribbon. The properties window will open
  2. Click the Basic setting tab if needed
  3. Update Basic Settings to match screen shot below

Fig 6Figure 6: Properties – Basic Settings

Assignment

Fig 7D365 Operations offers multiple assignment types to assign review and approval steps. Options include

    • Participant – allows for Step to be assigned to users that carry specific security role or members of a user group
    • Hierarchy – utilizes the management hierarchy (if configured) to direct workflow from the originator through the management structure
    • Workflow users – allows for assignment to the originator or the owner of the workflow
    • User – allows the workflow step to be assignment to a specific user
    • None – default entry, must be updated to run the workflow (not valid for all workflow elements)
  1. Select the Assignment tab
  2. Select User in the assignment type tab
  3. Select the User tab and use the arrows to select the user that should complete the review
  4. Accept the defaults on the Time Limit tab

Fig 8Figure 8: Properties – User Assignment

Escalation

Escalations are user Used when a document is overdue (the time allotted for the user to act on the document expires) and the document needs to be assigned to another user for approval. Escalations will not be configured for this workflow.

Automatic Actions

You can configure Dynamics 365 for Operations to automatically act, reject or approve, on the document if specific conditions are met. For our workflow, we want Operations to automatically approve the purchase order if the total amount is less than $50,000.

  1. Close the Accounting Review Properties window.
  2. Select the Approve Purchase Order Step and open the properties window
  3. If desired, select the Basic Setting Tab to updated the Name of the step
  4. Select the Automatic Actions tab
  5. Select the enable automatic actions checkbox
  6. Select Add Condition
  7. Update the condition to match the screenshot below.
  8. In the Auto complete action field select Approve

Fig 9Figure 9: Automatic Approval

Notifications

Notifications allow alerts or emails to be sent to the recipient when the enabled event occurs on the purchase order. For our workflow we will enable the approve notification to be sent to the workflow originator, the user who submits the purchase order for approval.

  1. Click the Notifications Tab
  2. With the Approve workflow element selected, click the Level Down button
  3. Select Step 1
  4. Click the Basic setting tab if needed
  5. Updated the Work Item Subject and Work tem Instructions

Fig 10Figure 10: Notifications

  1. Select the Assignments Tab
  2. For Assignment Type select User
  3. Click the User tab and select the user that will be responsible for approving the purchase order

 

Conditions

Condition are used to specify when the approval step is required. Conditions can be set on the workflow or workflow element. Conditions are not needed for this workflow.

  1. Click on the conditions tab to review the options
  2. Save and Close the workflow. When asked to make the version active select yes.

Submit Purchase Order to workflow

Now that our workflow is created and activated users can begin to submit purchase orders for approval. A user creates a PO with an amount greater than $50,000 and submits the purchase order to workflow. Since the purchase order is less than $50,000 the purchase order will be automatically approved.

Fig 11Figure 11: Submit Purchase Order

When a user is assigned to review and approve the PO. The work items show up in the user’s Work Item list:

Fig 12Figure 12: Work Items List

The user can approve the PO from the Work Item list, or from the PO form.

Figure 13: Complete Review

The Workflow History shows the different workflow activities the PO went through.

Fig 15Figure 15: Workflow History

About the Author

Adrianne Johnson specializes in business process design and training in financial and supply chain areas. With experience in the food harvesting, bio-technology and manufacturing industry, Adrianne has help clients get the most out of their Dynamics solutions by improving business process efficiency and user adoption. To learn more about Socius and Dynamics 365 please visit us at www.socius1.com.


 Appendix:

Workflow Editor in D365

  1. Workflow editor is now a program that requires a 1-time download.
  2. When you select a workflow to edit, a .NET component downloads and a separate window opens (Microsoft.Dynamics.AX.Framework.Workflow.WorkflowEditorHost).
    1. In rare cases, something might happen with the downloaded application files.
    1. This is easily cleaned up by running a Command Prompt: rundll32 dfshim CleanOnlineAppCache
    2. The next time you click on a workflow, the extension will re-download.

Lifecycle Services & Business Process Modeler

LCS LibraryHere is a preview of a whitepaper post that will be up on the Socius site in the next couple days.  My thanks to Jonathan Myer on the Socius team for drafting a fantastic how-to post:

Utilizing Lifecycle Services & Business Process Model Management

LCS Business Process Modeler Overview

Lifecycle Services, a cloud project lifecycle management platform, allows for multiple user personas through a wide range of services and tools. Among these different offerings, the most applicable tool for end users and functional consultants is the Business Process Modeler. The Business Process Modeler (BPM) allows users to build out business process libraries for their specific end-to-end scenarios through the incorporation of business hierarchies.

Building & Utilizing Hierarchies

Business process hierarchies are defined by users or consultants based on specific requirements of the end users. Socius utilizes an adaptive implementation methodology (AIM) which allows our implementation team to both utilize repeatable processes & structure content based on the client’s individual needs. Generally, we recommend a hierarchy structure by Module, Process Area, Category/Area, and then requirement ID. This allows for a clear separation and organization of processes by granularity and detail level.

Build a BPM Library

  1. Sign into Lifecycle Services site and then Dynamics 365 for Operations project
  2. Click the Business Process modeler tool

 

  1. Right click on an existing library to create a new library
  1. After creating a new library, add a business process hierarchy by selecting Author and Edit view underneath the Overview view
  1. Drag the new process obelisk under Core Business Processes to begin creating the top level of the hierarchy.
  2. Name the business process per the hierarchy constructed.
  1. Add links and helpful resources to each business process node using process details menu items
  1. Switch back to the Overview tab and open one of the business processes, which will currently be empty, and contain two tabs:2) Visio will allow users to personalize their business process nodes by uploading process documents.
  2. 1) Flowchart will display automatically created flowcharts based on Dynamics 365 for Operations (D365EO) task recordings which capture step by step business processes.
  3. You’re now ready to begin creating process recordings in D365EO

Dynamics 365 for Operations Integration

After the library hierarchy (our platform) has been built, begin to construct task recordings inside of our Dynamics 365 for Operations Browser Client. These recordings will be saved to specific levels in our platform to be later used for training and testing purposes.

  1. Log in to the D365EO web client
  2. Once authenticated navigate to settings in the top right ribbon and select task recorder
  3. Four different options are presented: (create recording, play recording as guide, edit recording, and playback recording), create a recording and save it to the library.
    1. To create a new recording click create recording
    2. Assign a meaningful name like create a sales order (process #) and description and press start to begin executing the business process
    3. Note that steps are recorded in the right task recorder pane and may be edited by utilizing the pen:
    4. Once complete, press stop and save to specific business process node created in LCS
  4. Review the process flow that was generated inside LCS and make adjustments as necessary

 

Endless applications

The power of the business process modeler lies in the ability for end users to learn autonomously and develop skills and knowledge around their company’s core Dynamics 365 for Operations business processes.  There is clear merit in utilization of BPM for companies with high turnover or seasonal employees that may engage with the BPM as a training guide. Further, companies that require documented business processes may utilize BPM as compliance resource that may be managed within the organization.

For more information about Lifecycle Services, Business Process Modeler or Dynamics 365 Enterprise products, contact Socius at our website or 1- 800-589-6614.

 

Dynamics 365 Roadmap

I’ll admit that keeping up with the releases of new functionality for Dynamics 365 is no small task.  The pace of new functionality is exceeding anything I’ve seen before in my career, and outpacing my ability to blog about it.

Everyone in the Dynamics space should keep this page from Microsoft at the forefront of their reading to understand what has been released and what is upcoming.

https://roadmap.dynamics.com/

I encourage customers and potential customers of the product to reach out to their Microsoft partner with any questions about the latest versions and licensing.

Demo Data for Dynamics 365 Operations

I am working with a new Dynamics 365 Enterprise Operations #MSDYN365 environment and one of the first things I did was generate relevant demo data.  In the past, when using a Contoso environment, we would have transactions from years ago and would spend time staging current data.  Now, utilizing the Generate Data option in MSDYN365, I was able to generate current and relevant purchase and sales data.

demo-data

Demo Data may be generated for the areas to the right on the screenshot above, selections may be turned on or off.  I left them all on and the system took about 15 minutes to generate transactions.

 

demo-data-results

The Generate Data options may be utilized repeatedly so that demonstration data may be kept current.      Will you utilize this feature when using your demonstration environment?