Tuesday, 9 June 2015

Workflow hierarchy assignment common errors explained and tester job [AX 2012]

Workflow hierarchy assignment has a lot of interdependent data that must be set up. If one of those is missing or is incorrect – the processor will just error out. Sometimes with very little information or confusing errors.

Below is an example of an error that is not very well written. It doesn’t tell you which record failed. Someone went into the effort of creating the labels correctly but did not use it properly.

image

Here are some common errors you would get while processing the workflow.

  • “The hierarchy provider did not return any users.” – Next Position was not found.
  • “Worker not found for position ID %1.” – No worker is attached to a position. Go to the worker and make sure they have a primary position. If no primary position exists, then the system will find the oldest position (one with the earliest start date). Also make sure the worker is an employee of the company to submit the workflow.
  • “User not found” – User not found for the worker. Check the user relations.
  • “User or job not found for position ID %1, worker %2, user %3. Verify that the position is assigned to a job.” – The position found does not have a job related to it.

Now here is a quick solution I put together to help you diagnose or test out your hierarchy. I wrote a job below for Expense lines but to change it to any other table is pretty straight forward. Fill in the missing information and run it. It will give you an infolog with the user id, worker id, position id, the reports to position id, their spending limit and approval limit.

Code:
static void navax_workflowHierarchyTester(Args _args)
{
WorkflowTypeName workflowTemplateName = 'TrvLineItemTemplate';
TrvExpTrans trvExpTrans;
TrvExpNumber trvExpNum = '000015'; //Expense id
str nodeId = '000530'; //Starting worker id

WorkflowHierarchyLevel level = 0;
WorkflowContext workflowContext;
SysWorkflowTable workflowTable;
WorkflowLimitHierarchyProvider workflowLimitHierarchyProvider;
WorkflowHierarchyProviderNode workflowHierarchyProviderNode;
HRPWorkerLimit workerLimit = new HRPWorkerLimit();
HcmWorker hcmWorker;
DirPersonUser dirPersonUser;
RefRecId hcmPositionRecId;
HcmPosition hcmPosition;
container spendingCon, approvalCon;
UserId userId;

select firstOnly workflowTable
where workflowTable.TemplateName == workflowTemplateName;

select firstOnly trvExpTrans
where trvExpTrans.ExpNumber == trvExpNum;


workflowContext = WorkflowContext::newWorkflowContext(
curext(),
tableNum(TrvExpTrans),
trvExpTrans.RecId,

workflowTable.WorkflowCorrelationId);

workflowLimitHierarchyProvider = new WorkflowLimitHierarchyProvider();

//Level 1
while (nodeId && level < 20) //20 is just a fall back. In case it goes into an endless loop.
{
workflowHierarchyProviderNode = workflowLimitHierarchyProvider.getNextNode(nodeId, level, workflowContext);
nodeId = workflowHierarchyProviderNode.getnodeId();
hcmWorker = HcmWorker::findByPersonnelNumber(nodeId);
userId = DirPersonUser::findParty(hcmWorker.Person).User;
hcmPositionRecId = HcmWorker::getPrimaryPosition(hcmWorker.RecId);
hcmPosition = HcmPosition::find(hcmPositionRecId);

spendingCon = workerLimit.getWorkerSigningLimit(
hcmWorker.RecId,
SourceDocumentRelationType::ExpenseReport,
HRPLimitType::Spending,
hcmPosition.PositionId);

approvalCon = workerLimit.getWorkerSigningLimit(
hcmWorker.RecId,
SourceDocumentRelationType::ExpenseReport,
HRPLimitType::Approval,
hcmPosition.PositionId);

info(strFmt("UserId: %1 | WorkerId: %2 | PositionId: %3 | ReportsToPosition: %4 | SpendingLimit: %5 | ApprovalLimit: %6",
userId,
hcmWorker.PersonnelNumber,
hcmPosition.PositionId,
hcmPosition.reportsToPosition(),
con2Str(spendingCon),
con2Str(approvalCon)
));

level++;
}
}



The final result looks like this.


image

4 comments:

Anonymous said...

Awesome, Munib!!!
Thank you very much for that!!!!

Assignment Help said...

Great information you shared with us.
Thanks..
Assignment help

Assignment Help said...

That was a great information you shared with us, It kept joined me regularly. Keep doing it
Thanks for shearing this....
Assignment help

Assignment Help said...

I feel a lot more people need to read this, very good info! …
Assignment Help Sydney