xTuple Connect is required when you send email notifications using the xTuple Desktop.
xTuple Connect is required when you send email notifications using the xTuple Desktop.
The easiest way to make an item tax-exempt is to make sure it is not linked to a tax type. For an item to be taxable, it must have a tax type associated with it. If there's no tax type linked to an item, then tax won't be charged.
xTuple stores a minimum of the 5 most recent backups plus one backup each week for a minimum of 1 year. Because of network related problems the most recent backups may not always be consecutive by day.
Some information may not show up on the xTupleCommerce website immediately. Instead, it stays in the cache. Think of the cache as a net that holds on to some of the changes.
To manually flush the cache (release the net of changes), log in to your xTupleCommerce website. Then navigate to Admin > Icon > Flush all Cache and select to flush all the cache.
Note-If after flushing the cache the formatting of the site looks like it has changed, refresh the page and it should go back to normal.
If an employee is going to be changing shifts, a manager or other administrator needs to assign the new shift to the employee's master record. If the new shift isn't assigned to the employee, the rules of the old shift will continue to apply to the employee.
As of version 3.6.0, xTuple no longer supports the PowerPC Mac platform. Only the Intel Mac platform is supported. Prior versions of xTuple did support PowerPC Macs, but beginning with version 3.6.0 xTuple no longer supports PowerPC Macs.
Yes, by simply typing a new number in the incident's next number field, you can change the incident number sequence. Keep in mind that incident numbers must be numeric—and you cannot use the number of an incident that already exists.
If you are using sales orders to capture customer orders, then invoices do flow from sales orders. The typical progression goes as follows: sales order -> shipping -> billing/invoicing. You can also enter invoices without first having a sales order. This is more common in service businesses, where inventory is not a major focus.
The primary difference between returns and return authorization is their relative complexity. Returns are quick to process and complete. They are designed for simple scenarios. Return authorizations, on the other hand, are far more complex. They support complicated business processes in a way that simple returns do not.
Both the xTupleCommerce system and the ERP both integrate with a secure credit card payment gateway. The following graphic provides a high-level illustration of how the process works:
When storing a credit card on file, xTupleCommerce uses the CC Gateway tokens that represent the credit card information and customer data. In addition, the "Blowfish Security" algorithm for encrypting sensitive information is used in the PostgreSQL database, on the ERP side. This ensures that the customer information is never passed or stored as plain text, but rather as an encrypted string of letters and numbers that serve as a key to unlock that information. Without a direct connection to the CC Gateway system through the API integration, the keys are worthless, thus preventing attackers from obtaining the sensitive information.
When analyzing your data you can filter the results in several ways. For dimensions, select the dimension name in the rows or columns—then select the available members to show. You can also filter results by dragging dimensions to the filter section, and from there selecting the available members to show.
There are two methods for importing data into the database of xTuple ERP.
Transfer orders are distinct from inter-site transfers in three primary ways. First, transfer orders allow you to move multiple items all at once between sites—instead of just one item at a time. Second, transfer orders always involve an intermediate transit site, for tracking inventory while it is "in transit." And third, there are reports (i.e., paperwork) associated with transfer orders.
The calculation basis is used to determine how taxes should be applied. Choose the base price option to have taxes calculated off the base price of sold items. For those requiring more complex tax scenarios (i.e., nested taxes or "tax on tax"), the calculation basis can be linked to any other tax code which uses the same tax class. When another tax code is chosen as the calculation basis, taxes will be calculated against the derived amount from the referenced tax code.
Item sources identify the relationship between items and the vendors who supply them. Having item sources pre-defined helps accelerate purchase order entry. Purchase order accuracy also improves when item sources are used.
No, severities are optional. They are not required when entering incidents. You can enter incidents without assigning a severity.
You can create the contact associated with a prospect before, during, or after the point when you create the prospect. It's up to you. If you create the contact first, simply search for the contact when you are creating the prospect record—and this will associate the contact. Conversely, to create a contact while entering the prospect, simply choose to create one in the contact field.
Incident status colors make it easier to quickly identify the incidents you are looking for. To assign a color to an incident status, simply type the name of the color (or its hexadecimal equivalent) in the field next to the status name. For example, let's say you want all incidents with the status feedback to be highlighted in red. In the field next to Feedback, you could enter either the word red or #FF0000, the hex code for red. Now whenever you view the incident list you will see your color-coding.
The customer defaults create a template that is used whenever new customers are created. For example, if you want all your customers to have the same payment terms, specify default terms for your customers—and all newly-created customers will be assigned those terms. You don't need to specify every default to use this feature. To bypass an option, simply turn the option off or specify none.
An opportunity source describes the lead source for an opportunity. For example, if the lead originated from an existing customer, the source might be "Customer Referral." Similarly, if the lead heard about you on the radio, the source might be "Radio Commercial." And so on. Using the advanced search feature, you can filter on opportunities by source.
Our systems, both xTupleCommerce and the xTuple REST API, require an SSL (Secure Sockets Layer) certificate to function. SSL is a standard security technology for creating and encrypted connection between a server and a client (for example, between a user's browser and the webserver). It allows sensitive information to be transferred in a secure fashion. Without an SSL the data would be sent between the server and client in plain text, which is not secure. In plain text an attacker could intercept the plain text data and have access to sensitive information.
Neither the xTupleCommerce system or the ERP stores plain text credit card information in the database. Both systems integrate with Authorize.net via their API. The same SSL technology is used to encrypt and send information to and from Authorize.net and we rely on Authorize.net to store credit card information in a secure fashion.
When storing a credit card on file we use Authorize.net tokens that represent the credit card information and customer data. On the ERP Postgres database we use the Blowfish Security algorithm for encrypting sensitive information. This ensures that the customer information is never passed or stored as plain text, but rather a encrypted string of letters and numbers that serve as a key to unlock that information. Without a direct connection to the Authorize.net system through the API integration, the keys are worthless which prevent attackers from obtaining the sensitive information.
Enabling customer deposits makes it possible to account for deferred revenue—that is, cash receipts that are not applied to open invoices when they are received. When this option is enabled, two things will happen: 1) a customer deposit option will appear on the cash receipt screen and 2) your receivables account assignments screen will include a deferred revenue account option. This deferred revenue account will be used when customer deposits are posted. If you don't enable customer deposits, unapplied cash receipts will be distributed to a credit memo, which can be applied to an invoice at a later date.
Generally you should work on translating the most current version of the software. xTuple regularly releases updates to our products, identified by version numbers. Each version may contain new sections or changes to old sections. Generally, translators should translate the most recent version of the product, but if your installation uses an older version of the product you may want to work on translating that version.
Yes, you can enable all of the available costing methods—if that's what your business requires. However, in many cases, one of the costing methods (average or standard) is generally sufficient. When you enable a costing method, that means item sites will be able to use that costing method. Inventory costing is specified at the item site level.
If you are having trouble vouchering a Purchase Order because there are Returns logged against it, then you probably left out an important step: Creating a Credit Memo for the Return. To do this, go to the "Uninvoiced Receipts/Returns" report screen and right-click on the Return record. In the right-click menu is the option to create a Credit Memo for the Return. Once the Credit Memo has been created, you should be able to continue processing your Voucher. Later, you can apply the Credit Memo to an open Voucher.