Cascade Integration Limitation - AbsenceLoad.csv Import

Cascade Integration Limitation - Absenceload.csv sample file - In the above csv file, you can see 2 different operations NEW and DELETE.

How they Operates?

• New - Will add New Absence to the SWF
• Delete - Will delete the existing absence in the SWF.

Synergy Work Force does handle both functionality New and Delete for absences However, we must understand that in order to Delete an absence from the system, the corresponding absence must exist within SWF!

In the above example, Cascade is sending NEW and DELETE absence for same employee for same date in the same file. Synergy Work Force cannot handle this situation.

How Synel process the file?

The service downloads the file from their FTP, reads all the line and then process the data. At this stage, if you have DELETE line - SWF needs to have first existing Absence for the day for the employee. However, the absence does not exist yet because creation of absence is also in the same file.

What solution we must offer Cascade or clarify before we agree the requirement?

If they have NEW and DELETE absence for same date for same employee - why do even bother generating that information in the same export file? Its pointless exporting the information and its pointless for us to process it.

Other solution is for them to produce 2 separate files.

• All containing NEW Absence.
• All Containing DELETE absence

• First SWF will read and process New Absence file
• Second SWF will read and process Delete Absence File

Include DELETE operation in the next import file (RECOMMENDED)