Account Reconciliation process notifications

[jacobw]

Hi community,

Hoping someone could advise the best practice for using the notifications sequence with the Account Reconciliation (OFC 7.1) solution. I have established the notification settings as desired in the administrative section of the product and assigned to the account groups. My troubles arise when I go to use the out of the box DM sequence Process Notifications. I have not made any modifications to the DM sequence/step or the associated business rule. I can see that the DM sequence already has parameters provided for WFScenario and WFTime, with the respective substitution variables |WFScenario| and |WFTime| already entered for the values.

Do most customers just leave the supplied substitution variables as is and schedule the sequence through the task scheduler? Or is it recommended to replace the substitution variables with specific values?

I've had some issues where the sequence fails with a Ordinal 17 error. I've also had a case where the sequence completes but sent notification emails out to approver stating they had past due approvals when clearly the reconciliations were marked as complete in the solution.

Just trying to get more information on how this is supposed to be used correctly as I have not found much mentioned specifically around this in the solution guides. Thank you

[johnal67]

I'm not going to be any help, I came out here to ask the same question.  I'm hard coding the parameters in Task Scheduler, but the guide says once you setup the task scheduler you don't have to touch it again, and you control everything from the Notification Methods in RCM.  I'm also getting the Ordinal 17 fail now that all the recons have been completed and workflow locked.  I try to move from 2022M9 to 2022M10 with the parameter but it still fails.  I'm assuming that's because we haven't processed the new month.  I definitely need some guidance also.

[jacobw]

I have a ticket with support on this. I'll keep this thread updated with the findings.

[johnal67]

Anyone heard of any fixes on this?

[jacobw]

Reviewed my help desk tickets. Last response I received was from 2 months ago stating this will be fixed in the next release, OFC-PV710-SV200.

[akatsman]

Has there been any updates to this? I am not sure how the job runs constantly if its only set up in the task scheduler once.

[johnal67]

You set it up as a daily recurring item.  Let me know if that's not answering your question, because we do have it working now.  

[akatsman]

got it, so Im assuming you just set it up first thing in the morning to let you know the changes from the previous day?

How did you handle the substitution variables to make sure that it is running on the correct period? I would think that is tied to the user who set up the job.

[johnal67]

I have it set at a time early in the morning, so it won't get buried with other emails.  We have an admin user that changes the Global Period on the first day of close for the current closeout period.  For example, we just started August closeout week yesterday, and the date is set to 2023M8 until we start the next closeout at end of September.  

[akatsman]

Got it, that is what I was expecting, but wanted to make sure.