web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Ledger daily general workflow - the creator should not be sent a work item to approve

(0) ShareShare
ReportReport
Posted on by

We are currently on 2012 r3 cu7 and want to implement the workflow for general journals

we don't want the person creating the journal to be able to approve it

so I have a list of users to assign to for each limit

how do I stop a user in the "assign to" list approving their own journals ?

I can see that there is a parameter in CU8 which stops this but wondered how others have solved this prior to the update

any help appreciated

thanks

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Jonathan  Halland Profile Picture
    11,310 on at
    RE: Ledger daily general workflow - the creator should not be sent a work item to approve

    Hi Dawn.  

    We either wrote a custom participant provider that did this determination in code, alternately create a calculated field to use in workflow conditions to determine whether the person who submitted is the next approver.

  • Community Member Profile Picture
    on at
    RE: Ledger daily general workflow - the creator should not be sent a work item to approve

    Thanks Jonathan I didn't know if there was a setting or configuration that I could do with out a development change

    I will pass this to our development team

    thanks again

  • André Arnaud de Calavon Profile Picture
    299,576 Super User 2025 Season 2 on at
    RE: Ledger daily general workflow - the creator should not be sent a work item to approve

    Hi Dawn,

    On each workflow configuration you can specify a Final approver. In case a submitter also approves the workflow, the approval will be forwarded to another person. In this case there is always someone checking the details.

    A customization like Jonathan mentioned is preventing it directly. In this scenario you can probably setup a manager as final approver and prevent a customization. When the manager gets too much work items assigned, fot sure he will speak with his team.

    Also you can add the name of the submitter in the workflow item, so it is visible who submitted it. Then teach the people to not approve there own submitted items.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Tocauer Profile Picture

Martin Tocauer 4

#2
Community Member Profile Picture

Community Member 2

#2
Nayyar Siddiqi Profile Picture

Nayyar Siddiqi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans