Areas. Sage Evolution Standard

Below you will find brief information for software Evolution Standard. This user guide will help you to understand the basic functionality of the software which includes features like inventory management, sales and purchases, accounting, and contact management.

PDF
Document
Sage Evolution Standard User Guide | Manualzz

Advertisement

Advertisement

/

Advertisement

Key features

  • Inventory management

  • Sales and purchases

  • Accounting

  • Contact management

Frequently asked questions

You can create a new company database using the System Manager. To do so, click on the "New Database" button and follow the on-screen instructions. The software will guide you through the process of creating a new database and setting up your company's information.

You can back up your database using the Database Management Console. To do so, click on the "Backup" button and select the database you want to back up. The software will then allow you to choose a location to save your backup file.

You can create a new customer by going to the "Customers" tab in the "Accounts Receivable" module. Click on the "New" button and fill in the customer's information. The software will then create a new customer record.

To process a sales order, go to the "Sales Orders" tab in the "Order Entry" module. Click on the "New" button and fill in the order details. The software will then create a new sales order.

User questions

Y U

Michael Y.

Is it possible to add new custom columns or User Defined Fields to document lines or transaction batches, such as Accounts Payable batches, in Sage Evolution Standard?

Adding new custom columns (User Defined Fields) to document lines or transaction batches, like Accounts Payable batches, is not a supported feature in Sage Evolution Standard. While existing grid columns can be customized for display (visibility, width, and sequence), entirely new custom columns cannot be added.

N W

John N.

Is it possible to assign incidents to user groups?

Based on the provided document, you can assign agents to agent groups, which could be a way to manage incidents by grouping users. According to the manual, you use agent groups to group agents together by their function and set access control per group instead of per agent. This could streamline the process of managing incidents by assigning them to a group of users with similar roles or responsibilities. However, the document does not explicitly confirm assigning incidents directly to user groups, but managing access and permissions through agent groups is mentioned.

Preparing document for printing…
0%