Workspaces in Sage 200 2013

With Sage 200 2013, we have redesigned and updated the look and feel of our Workspaces.  The workspaces provided with Sage 200 have been designed to demonstrate the information that can be shown on a workspace for each module, rather than for particular task or process, as this can vary greatly from business to business.

The workspaces can easily be customised to suit your requirements or current task. This can be done on several levels:

  • Change the data that is displayed in workspace for your current task.
  • Change the windows ( actions) that can be opened from a workspace to usit a task or process.
  • Sort and filter your data. You can create filters that are saved and can be used by everyone with access to a workspace, making it easy filter the data in the same way.
  • You can permanently change the content of the workspace and how it is displayed using the Workspace Designer.
  • Create new workspaces using existing content.
  • Create new content.

Further information on setting up and using this process is available via the online help area and from your business partner.

  • Hi Sage,  I just wanted to say how great in theory your new workspaces are.  They are a considerable improvement.  Unfortunately there appears to be severe memory issues.  

    For example, if I view the sales order list, all 4000 sales orders are loaded into memory regardless of how many are displayed on screen.  If we then switch to the Estimates list, all 4000 estimates are loaded into memory - meanwhile the Sales Orders are still loaded into memory.  If I then switch to the MRP recommendations list, all those items are loaded into memory too.

    By this time, if I run task manager I can see that the Sage200desktop.exe is running at 800,000k.  If I then switch to another workspace, for instance Stock Item list, Sage crashes.  

    -This issue was logged with Sage in December 2013.

    -This issue has been viewed by Sage support using Remote Desktop.

    -The Sage issue ref is 051213-6B5FF.

    -Our users are experiencing 4 to 5 crashes a day.

    -This issue can easily be recreated, just open up Task manager and load Sage 200, start to switch between workspaces and you will see the allocated memory creep up.

    - This issue is not hardware dependent.  It has been recreated on a PC with 12GB Ram, i7 processor.

    I would be interested to hear your thoughts on this issue.

  • Hi David,

    Thank you for your feedback on this, I'm sorry you're having some frustrating issues here and I'm going to ask someone from the customer services team to look into this for you. We will get back to you shortly.

    Thanks,

    Melissa

  • Thanks Melissa.  Quite amazingly I have just worked out what the problem is.  

    When using the menu on the left hand side of Sage 200, each time a menu button is pressed, a new workspace session is created (like opening a new tab in a web browser).  If you use the Workspace Menu instead to switch between workspaces, then new session aren't created and the memory management works well.

    I think the issue here is that there is no way to close the additional sessions which have been opened by using the menu on the left of Sage 200.  These should be automatically closed by Sage 200, or the user should have the ability to close these additional hidden tabs.  I will be advising our users to just use the Workspace menu to navigate from now on.  Thank you for your swift response.

  • Gosh, that was fast! So pleased you have found a way to solve the issue.

    For future reference, I've been advised that the fastest way to get help with this particular product is to speak with your Business Partner who should be able to advise or escalate it.

    Best wishes,

    Melissa

  • Thank you Melissa.  

    Unfortunately in this instance, neither the business partner nor the Sage support technician could resolve the issue.  They could recreate the issue but were unable to suggest a fix.  As I mentioned above, we logged this issue 6 months ago and the users have been experiencing several crashes a day since.  

    Hopefully anyone who reads this post will now be aware of this potential memory problem and how to fix it.