Large Data Background Save Example

[keiko.kasho]

Hello, can someone please provide an example where we have an app that uses large data background save and explain why we use it for that use case?

[keiko.kasho]

[keiko.kasho]

I noticed sales orders has it configured.

NW help says “Customers can specify their own low timeout threshold. For example, Composite applications may have async save enabled when the application has save logic that has a run long time. If the save hits the threshold, users would receive a notification that the save is continuing in the background and would be navigated back to their previous location to continue working.” in https://login.dmsplus-test.coxautoinc.com/#/drilllink?NwDrillApplication=contentviewer&NwDrillForm=other&nwId=znwNo-Code%20PlatformFamily.znwNo-Code%20PlatformConcepts.znwCox%20Automotive%20DMS%2BNATE.NateDevelopmentConsiderations.

May someone please clarify how to specific your own time out threshold? Is that in a LB? What LB is that in for sales orders?

[Aaron.C]

I can’t tell you exactly where its used/configured but it is not via Logic Block. I don’t know that the statement on the help text about “Customers can specify” is entirely accurate. They may be able to by some sort of request but I also don’t see a place where this would be defined by environment or tenant

[cheyanne.schwiethale]

@keiko.kasho the async save timeout threshold is a server config property (defaulted to 25 seconds). The timeout threshold is generic across your environment for all applications that opt-in to this behavior, not on an app-by-app basis.

I see that you found the Sales Order example - that’s the example I was going to point you to as well.

For future reference:

• You opt-in to async save on the application level.

  • If your application is an HD app, you will configure these settings on the Header app of the HD.

• The two fields that matter are the Descriptive Field and Background Operations fields.

  • Descriptive Field should be a field that helps to uniquely identify a record in your application (e.g. SalesOrderID) and will be included in your success or failure notifications upon completion or failure of your save.
  • The Background Operations lookup is where you will opt-in to this behavior. Select Large Data Background Save.

[cheyanne.schwiethale]

Help documentation has been updated.