Home › Forums › Developers › General developer's discussion ›

Managing internal messaging

Submitted by Ben_Charlton on Wed, 15/07/2015 - 11:44
in

I think we may need a better or faster method to manage internal messages.

With the loaders returning errors as messages my inbox overloads occassionally...if I dont notice the issue straight away.

‹ Electronic S8 Register Order Generation and Order Delivery Status ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Managing internal messaging

Submitted by tgething (not verified) on Wed, 15/07/2015 - 12:18.

Agreed.  This is one of the reasons we do not use the in-build scheduler to run the docload processing.

One needs to be able to clear messages in bulk (as you can in most email systems). Although one can select multiple messages, pressing the Delete button on deletes only one.

Perhaps another thing to do is to have the docload processor remember the last error message sent and not repeat it if it the new one is a duplicate - so you don't get:

Regards, Tim G

 

Re: Managing internal messaging

Submitted by tanderson on Fri, 17/07/2015 - 12:24.

Raised as OVPMS-1638

Regards,

-Tim A

Re: Managing internal messaging

Submitted by tony on Fri, 17/07/2015 - 12:28.

Hi,

I suggest that the docloader should move files that have generated errors to another folder (Error folder).  This way they are easily recognised as invalid outside of open and dont generate any further error messages.

Cheers

Tony

 

Re: Managing internal messaging

Submitted by tgething (not verified) on Sat, 18/07/2015 - 06:57.

Tony - I agree that there needs to be a 'could not load' folder.  However, the problem is more that that.  For both the 'loaded' and 'not loaded' folders, the move operation needs to be 'move and silently overwrite any existing file of the same name' rather than simply 'move and report error if the file already exists'.

The docloader utility has the same problems - and for this reason the bat file that we use has the following logic:

  • if no files in results folder do not start docloader [this is simply for efficiency], else start docloader specifying tloaded as the destination folder
  • after docloader finishes move /Y any remaining files in the results folder to the notLoaded folder, and move /Y any files in the tloaded folder to the Loaded folder

The /Y option ensures that if a file of the same name exists in the destination folder it will be silently overwritten.

An alternative to 'move and silently overwrite' is of course to use a -1, -2 etc renaming convention.  However the 'silently overwrite approach has caused no problems for us.

Regards, Tim G

Syndicate content