Skip to main content
Solved

"Repeat Media Output" doesn't send the Payment File to Server Location


Chandima Pathirana
Hero (Partner)
Forum|alt.badge.img+9

Issue: 

In Aurena version, once a supplier payment order is created using BACS payment method it will create the payment file to the Downloads folder in the user's computer and not in the server location - and there is no way to send it to the server location. Please refer the test plan to identify the issue.

Environment
App 10 - Aurena Versions

Steps followed
In Aurena version, once a supplier payment order is created using BACS payment method it will create the payment file to the Downloads folder in the user's computer and not in the server location and there is no way to send it to the server location.

Expected outcome? 
Users use the Server Location for payment files for security reasons, and if the file gets created in the users computer, then it's possible for a security breach to take place.

 

Can this be fixed ?

Best answer by Xavier Fernando

Hi CHPTLK,

When you execute repeat media output, if there is no new application message is created, that means usually relevant payment format does not go through Background functionality. In that case, there will be only one option as users will have to delete the payment order and re-create a new payment proposal

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

5 replies

Forum|alt.badge.img+8
  • Sidekick (Partner)
  • 25 replies
  • April 16, 2021

Hi there

When you map the output file directory in the form Payment Methods per Institute, you will notice two other fields a little to the right called “Server Output File Directory” and “Server Output File Directory History”.  

Have you tried to use this fields instead?


Ieva Rituma
Superhero (Employee)
Forum|alt.badge.img+16
  • Superhero (Employee)
  • 424 replies
  • April 16, 2021

It is correct, that there is no way to send the file to Server Location, if “Repeat Media Output” is used (either for supplier or from employee payments). The server location setup mentioned above only works when the file is initially created. 

The sending to the server location requires the “Run in Background” functionality which is not available when repeating media output. 

A customer case raised for this same issue: G2251657. This led to the customer needing to always cancel the payment orders and re-create a new payment proposal in order to enforce payment file security. 


Forum|alt.badge.img+20
  • Superhero (Employee)
  • 294 replies
  • Answer
  • April 16, 2021

Hi CHPTLK,

When you execute repeat media output, if there is no new application message is created, that means usually relevant payment format does not go through Background functionality. In that case, there will be only one option as users will have to delete the payment order and re-create a new payment proposal


Ieva Rituma
Superhero (Employee)
Forum|alt.badge.img+16
  • Superhero (Employee)
  • 424 replies
  • April 16, 2021

I’ve raised an idea for this in the Community because it’s been raised with me as an issue


Dhananga Jayatilake
Hero (Employee)
Forum|alt.badge.img+7

BACS Payment method normally creates the output file in txt format in user’s local machine. Therefore, even when you execute repeat media output no new application message will be created and server location used previously will be used.

As suggested users will have to delete the payment order and re-create a new payment proposal.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings