Suggest a new Idea

  • 33

    Workflow history - comments fact box

    Suggested by Microsoft – Planned 2
    Category: Workflow

    When reviewign an invoice or approving an invoice there is no quick way to view the history and comments of previous workflow history. Whilst multiple clicks can see each particular comment 1 by 1 it woudl be more user friendly if a 'Workflow Fact Box" was availabel on the Right Hand Side that could be enabled to see all the history and comments with a scroll bar

  • 19

    Workflow Workspace

    Suggested by Josh KnoxUnder Review 2
    Category: Workflow

    Create a workspace where all workflows in the system are available at once (instead of clicking into each individual module to view the applicable workspaces).

  • 14

    Mobile approval workspace portal for all pending Workflow items for user

    Suggested by Mesut BOZTASNew 0
    Category: Workflow

    Create a new built-in workspace where all workflows in the system assigned to me are available at once in MOBILE app page.

    User can do invoice, expense and purchase order approvals only and they are seperate pages in mobile.
    I want an one page to manage pending worklows on mobile app like workflow item assigned to me listpage in client side.
  • 14

    Have the ability to setup workflow Escalation for a Work Item queue

    Suggested by Marian WriceUnder Review 1
    Category: Workflow

    In Dynamics 365 for finance and operations, there is an ability to setup the workflow and escalate if needed.

    In the current design, the users can only select to escalate the workflow to the following options:

    Hierarchy, Workflow user and users.

    If users are using the Work Item queue, they would like to be able to escalate the workflow to a specific queue instead.

    This option is currently not available in the application and will be nice to see as part of the standard workflow feature.

  • 8

    Making Workflow History more user friendly and visible

    Suggested by Natalie WebbCompleted 0
    Category: Workflow

    Currently it is difficult for an end user to go through the workflow history to actually find out where in the process that particular workflow is and where else it needs to go before it is completed. It would be great if this was made more visual with a checklist or flow chart

  • 7

    Worker field as origin of hierarchy

    Suggested by Fredrik SætreNew 0
    Category: Workflow

    When triggering workflows using an automated step (like vendor invoice automation), you would want to use one of the fields in the actual record as the origin of the hierarchy when doing assignments.

    The person requesting the invoice should be the base for the hierarchy.

    Today only workflow originator (the system account) or the workflow owner (worker creating the workflow) is possible to choose.

  • 7

    Unable to create/write "canSubmitToWorkflow" method (or) Standard override methods on table extensions in D365O

    Suggested by KrishnaSrikanth MUnder Review 2
    Category: Workflow

    I need to create a workflow for which "canSubmitToWorkflow" method needs to be created on standard table which doesn't have canSubmitToWorkflow standard method but development is to be done using extensions.

    In table extensions we can't override standard methods which in-turn can't create "canSubmitToWorkflow" method.


    Error message is :-

    "cannot define an extension method "canSubmitToWorkflow" in extension class "custTable_Extension" targeting type "custTable" because the type already defines a method with same name.

    As per above error & my understanding, "canSubmitToWorkflow" method is an override/standard method,

    by default every table consists some set of override methods and above method belongs to same.

    Even i have seen for events which are listed for table extensions as a separate node(Events)and i haven't find any event handler for "canSubmitToWorkflow" method as we have for others(onUpdated,onUpdating...etc)

  • 6

    Default order type not available in workflow condition

    Suggested by evert BosNew 1
    Category: Workflow

    Since we lost our item type BOM there have been so many situations where we have trouble in workflow conditions and other situations where I need to sort on "MAKE" versus 'BUY" items.

    Because the default order type is hiding in a supporting table of the item table, I can't use a condition on it in a workflow. Workflow conditions allows no joins.  In reqular queries I have to use  a Join.

    This is such a handicap that I would consider a change in the design. Get that default order type back into the inventtable. It would make a big difference. There is no good reason to hide it in the default order parameters table. It is not that I need an item to be purchased in site 1 and manufactured in site 2. I I really need that I have my item coverage to do that. 

  • 6

    Workflow reject to be reassigned to previous steps.

    Suggested by Annaick BoudinNew 1
    Category: Workflow

    Workflow with several approval steps is rejected on last one.

    Actual behavior: Workflow will have to be resubmitted by initial user.

    Expected result:  Workflow should then be reassigned to a selected step (n-1) 

  • 6

    Legal Entity specific Purchase Requisition workflow and Parameter

    Suggested by Corey WarawaNew 0
    Category: Workflow

    Dynamics should have the capability to make the Purchase Requisition workflow legal entity specific.

    The recommended solution is as follows:

    1. Still allow for an organization-wide Purchase Requisition workflow to be created.

    2. Enable legal entity specific Purchase Requisition workflow configurations.

    3. Create a parameter in Procurement and Sourcing to identify which Purchase Requisition workflow should be used for the legal entity.

    This recommendation will create configuration flexibility to allow organizations to make Dynamics work for their business.

    Currently, workflow for purchase requisitions is associated to the organization - meaning that it is used for all legal entities.  This is very limiting and challenging for organizations with multiple legal entities as the approval routing is rarely the same.

    Accordingly, this results in either:

    1. The workflow configuration becoming extremely complex and difficult to maintain due to multiple layers of conditions and task assignments.

    2. The business having to compromise and adjust their processes to fit with the system limitation.