When it comes to user experience in the cloud, the process is much more streamlined than it was in S3. For example, when you go through cycle processing, it will walk you through based on your payroll schedule. You go through the steps based on your payroll cycle from calculating overtime all the way through the post payroll, which means that you will need to go to your payroll cycle to access that information. As you calculate your overtime, it brings up a button to process the next one, and the next, and so on until it is complete. The system won’t let you out of queue – it keeps showing the next process until you have completed everything. That feature is in line with most of CloudSuite in that it's very process oriented and not transactional.
One question we have received about this process is if we load pay history either during parallel testing or go live? For parallel testing, we load it directly. For our last round of parallel testing at our most recent implementation, we did have payroll history for current year. Infor supplies an interface for program that supplies that we use to load that goes through checks and balances, making sure that your check is in balance before it will actually load. You want to then make sure that program is complete before it puts it into a holding table. At that point you want to balance it, make sure it balances back to what you have in S3. Once it's balanced you, then you can process it to be loaded back to the resources.
