Issues while using SysWorkflowApprovalService externally

(0) Share

Report

Posted on by Community Member Microsoft Employee

Hello, i wish to create an application that could handle AX workflows externally.

For testing purposes, I created a Windows Console Application to handle Dynamics AX PO Workflows. I exposed the SysWorkflowApprovalService from the AOT and the application is successfully getting the values from it. In the tables the element has the status "Pending" but when i call the applyAction function with the correct parameters (values for context,action,workItemId,networkUserAlias,networkDomain,comment) i get this exception "The Element has already been Approved"

When i change the action to "complete" or "reject" the exception changes to "The Element has already been Rejected"
I tallied the actions from WorkflowAction.Name

Has anyone faced this issue? If yes, how did you overcome it?

*This post is locked for comments

All responses (2)

Answers (0)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Issues while using SysWorkflowApprovalService externally

Yes they are. Namely 'Approve' 'Reject' and 'Defer' (checked from WorkflowAction table)

The documentation at the msdn site for AOT objects claims that this is supposed to be included

Using the framework class. That's our project requirement
Sohaib Cheema 46,610 User Group Leader on at

Like (0)

Report

RE: Issues while using SysWorkflowApprovalService externally

The BaseEnum values, which are coming form C# console are those equal to expectations of AX??? I mean in terms of changing status of workflow.

and one more question, are you trying to change status of workflow step directly by .update method or trying to update workflow status by calling framework class?