Solved

IFS not updating when a Supplier Invoice is authorized in Notify Me Aurena 10

  • 5 August 2022
  • 4 replies
  • 210 views

Userlevel 6
Badge +15

Hi,

I have what appears to be identical issue to the following thread, however that thread is now locked and no answer was given. User acknowledges Posting Proposal in Notify Me but the transaction isn't acknowledging | IFS Community

 

We have installed Aurena 10 Notify Me and are trying to approve supplier invoices through the app, however whilst authorising, IFS never actually updates the invoice status.

We can see IFS is receiving some information as a background job is posted which updates the notifications to stop them from being sent to the device again.

 

There is an error obtained from the client

{"LoggedAt":"2022-08-05T12:49:23.259781+01:00","Name":"Exception","Properties":{"Exception":"<Ifs.Cloud.Client.Exceptions.CloudException><Message>400: Bad request: request method denied<\/Message><StackTrace>  at Ifs.Cloud.Client.Comm.CallRequest`1[T].ExecuteRequestAsync (System.Threading.CancellationToken cancellationToken) <0x103141910 + 0x00b88&gt; in &lt;0b09a6abb0334aa0a768ac0629b57dd5#01c59613b10d1840be59075db4889a65&gt;:0 \n  at Ifs.Cloud.Client.Comm.CallRequest`1[T].ExecuteRequestWithRetryAsync (System.Threading.CancellationToken cancellationToken) &lt;0x103140e70 + 0x0091c&gt; in &lt;0b09a6abb0334aa0a768ac0629b57dd5#01c59613b10d1840be59075db4889a65&gt;:0 \n  at Ifs.Cloud.Client.Comm.CloudResourceProxy`1[T].ExecutePutAsync () &lt;0x1031451c0 + 0x001f3&gt; in &lt;0b09a6abb0334aa0a768ac0629b57dd5#01c59613b10d1840be59075db4889a65&gt;:0 \n  at Ifs.Uma.Services.Comm.TouchApps.TouchAppsComms+&lt;&gt;c__DisplayClass50_0.&lt;RegisterForPushNotifications&gt;b__0 () &lt;0x103108060 + 0x001bf&gt; in &lt;918528201d6f4beda2b6c07afb3271f2#01c59613b10d1840be59075db4889a65&gt;:0 \n  at Ifs.Uma.Services.Comm.TouchApps.TouchAppsComms.HandleAuthenticatedRequest (System.Func`1[TResult] action, System.Boolean isInitializing) &lt;0x1031064a0 + 0x004cc&gt; in &lt;918528201d6f4beda2b6c07afb3271f2#01c59613b10d1840be59075db4889a65&gt;:0 \n  at Ifs.Uma.Services.Comm.TouchApps.TouchAppsComms.RegisterForPushNotifications (Ifs.Uma.Services.Comm.TouchApps.PushRegistration reg) &lt;0x103108320 + 0x00333&gt; in &lt;918528201d6f4beda2b6c07afb3271f2#01c59613b10d1840be59075db4889a65&gt;:0 \n  at Ifs.Uma.Framework.Services.PushNotificationServiceBase.RegisterForPushNotificationsAsync (System.String pnsHandle) &lt;0x10226cad0 + 0x0040b&gt; in &lt;680131cbb6bb44739f0b259548a9af7f#01c59613b10d1840be59075db4889a65&gt;:0 \n<\/StackTrace><\/Ifs.Cloud.Client.Exceptions.CloudException>","Kind":"Recoverable"}},

 

We have raised an IFS case in the portal, however this is stuck in a queue for 10 days now…

 

Thanks, Callum

icon

Best answer by JOOLSE 22 August 2022, 09:03

View original

4 replies

Userlevel 6
Badge +15

Had a bit of a brainwave whilst reading the error message ‘400: Bad Request’ - I checked the HttpServer1 and can see it is not working as expected which I believe is the root cause of the issues. However, I cannot confirm until I can arrange some downtime on the LIVE server to resolve the issue

I think its stuck in an intermediate where it is showing as ‘SHUTDOWN’, however this cannot be fully true as users would not be able to connect to IFS at all.

Userlevel 6
Badge +15

The HttpServer1 issue was not the root cause  (But least it’s fixed now)

 

We have found that if there is only one authorisation line on the posting proposal then Notify Me will authorise it correctly.

If there are multiple authorisation lines, Notify Me will only action the first line. (For example if there is an Acknowledge Line and an Authorise Line - Notify Me will work for the Acknowledger but will not do anything for the Authoriser)

 

Callum

Userlevel 5
Badge +10

Hi

I have discussed this issue with our experts in Financials and according to them it is a defect.

The answer I got from them was the following: “It works when both are Authorizers but not if the first one is Acknowledge and the second one is Authorizer.”

If you have alreddy raised a defect towards IFS, then we will hopfelly get it soon and can start work on the issue. 

Regards

Johan

Userlevel 6
Badge +15

Case raised with IFS a few weeks ago - bug has been identified - awaiting RnD fix

Reply