POS End Of Day

The POS End Of Day process can be triggered by a scheduler or by a command from the POS Server.

All POS instances in one store should use the same approach - either the scheduler or the EOD command.


Configuration files	..\parameter\client\flow\endOfDayConfigs.properties ..\parameter\client\flow\terminalAdminEndOfDayConfigs.properties

The configuration is set in the file endOfDayConfigs.properties:

EndOfDayConfigs.Default.scheduledEod=true/false
EndOfDayConfigs.Default.silentMode=true/false
EndOfDayConfigs.Default.scheduledCronExpression

The configuration is set in the file terminalAdminEndOfDayConfigs.properties:

TerminalAdminEndOfDayConfigs.Default.silentMode=true/false
 TerminalAdminEndOfDayConfigs.Default.allActiveTerminals=true/false

Configuration for POS without Flow Service

If the POS is used without Mobile POS Clients, both trigger variants can be used.

The silentMode can be configured in both ways, according to project preferences (endOfDayConfigs.properties).

EndOfDayConfigs.Default.scheduledEod=true/false
EndOfDayConfigs.Default.silentMode=true/false
EndOfDayConfigs.Default.scheduledCronExpression=0 0 2 ? * * *

The POS without Flow Service uses only one payment terminal, which is why allActiveTerminals = false is recommended (terminalAdminEndOfDayConfigs.properties):

TerminalAdminEndOfDayConfigs.Default.silentMode=true/false
 TerminalAdminEndOfDayConfigs.Default.allActiveTerminals=false

Configuration for POS in Hybrid Mode

POS in hybrid mode means that mobile clients are connected to the POS via a Flow Service interface and the POS Client is also used.

In this architecture, it is recommended to use the scheduler as a trigger for the end-of-day process. The reason is that the EOD command is not generated by the POS Server if the POS Client is not used during the financial period. It is recommended to configure the scheduler for some time at night when no devices are used.

The silentMode can be configured in both ways, according to project preferences (endOfDayConfigs.properties).

EndOfDayConfigs.Default.scheduledEod=true
EndOfDayConfigs.Default.silentMode=true/false
EndOfDayConfigs.Default.scheduledCronExpression=0 0 2 ? * * *

terminalAdminEndOfDayConfigs.properties:

TerminalAdminEndOfDayConfigs.Default.silentMode=true/false
TerminalAdminEndOfDayConfigs.Default.allActiveTerminals=true

Configuration for Standalone Edge-Flow Service

For the standalone Edge-Flow Service, the scheduler has to be used to trigger the POS End of Day. POS Server does not create EOD commands in this case. It is recommended to configure the scheduler for some time at night when no devices are used.

The standalone Edge-Flow Service is a backend application. It does not have a UI and therefore always behaves as if silentMode = true. The value of the silentMode parameter is not considered in this case (endOfDayConfigs.properties).

EndOfDayConfigs.Default.scheduledEod=true
EndOfDayConfigs.Default.silentMode=true
EndOfDayConfigs.Default.scheduledCronExpression=0 0 2 ? * * *

As Flow Service maintains all EFT devices used by connected Mobile POS Clients, the terminal end-of-day process has to perform the action for all terminals (terminalAdminEndOfDayConfigs.properties).

TerminalAdminEndOfDayConfigs.Default.silentMode=true
TerminalAdminEndOfDayConfigs.Default.allActiveTerminals=true