Plan for testing Fiscal rollover with high volume numbers
bugfest would be where this would happen
very hard to see in testing how to analyze the output in a way of skimming
looking for some kind of big picture view of the rollover data
Some kind of feature like this could be implemented (Dennis B)
currently nothing in the UI that allows that skim (review dashboard, or something like that)
kinda of a 'test' of rollover before it is actually done, looking for a way to view the implications and review of that process before it happens as part of an overall workflow (no matter what happens in the background technically)
A set of APIs within the export module that would be called from other apps
if you started an export from somewhere, there would be a log
Proposing to add another tab for other jobs
Question from chat (I'm wondering if it might help to add a column containing a link to any associated error logs that are generated during the export?)
Viewing errors, etc?
The view of each log item would give some kind of details
Q: What about showing in a quicker view if there were errors, or if they could be highlighted for quicker recognition of those errors ?
An error file, perhaps?
from chat (In the KB Local Admin we have job results “Success”, “Partial success”, “Failure”, “Interrupted” )
from chat (“Success” means that it completed without any errors, “Partial success” completed with some errors, “Failure” means the job failed somehow, and “Interrupted” means that the job was prevented from finishing)
Any module that uses export functionality, this tab would track that activity
it could be searched and filtered
More efficient way to export things (from a technical perspective)
Mod audit, Mod finance, mod finance, etc, places to get information
from wherever one use in the UI, a request would be made to use this application
this app would need to be able to work with the other apps
this would be thus less impact on the other apps since the activity is happening separately in its own app
Springbatch tech for export
what is the export file going to be?
can the export be reduced to what is needed or will it pull everything that is preset in that export?
Might the type of data need some kind of profile (blueprint for the export itself)
How do we set up what to expect from the export, to better understand what is actually exported, or what was actually requested
Data Import updates: Schedule for EDIFACT, embedded MARC
