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.
Employee and user are not necessarily the same thing. An employee is a person who works for your company. A user is a person who has an account allowing them to access your xTuple database. There are scenarios where database users would not also be employees. For example, you may give user access to people who are not your employees (e.g., IT consultants). Conversely, there are also scenarios where employees wouldn't need user accounts. For example, you may have employees whose job doesn't require them to use a computer—and so there would be no need for them to have a user account.
The topic of project basics is covered in some detail in the manual Managing Projects with xTuple. The book can be read online for free or purchased for download through the xTuple MarketPlace.
If you are going to use credit card processing or if you're getting this message ERROR: function decrypt(bytea, bytea, unknown) does not exist then you need to install pgcrypto. Pgcrypto is a library used for encrypting sensitive data. The pgcrypto software is a popular add-on package included with the PostgreSQL source code distribution. The pgcrypto module is used by our credit card encryption functionality. Even if you are not processing credit cards, we still recommend that pgcrypto be installed.
First, we need to locate the pgcrypto.sql file. One typical path to this is:
If it isn't there you can always search for the file. You may need to perform the search as root (be patient, this takes a while):
find / | grep pgcrypto.sql
Or if you're on Windows just use the Windows file search.
Once you've located the file the next step is to install it. The command to install pgcrypto onto your database is:
psql -U mfgadmin NameOfDB < /wherever/the/file/is/pgcrypto.sql
Or if you prefer using pgAdmin, connect to the database you want to install pgcrypto and open/execute pgcrypto.sql through the SQL Editor. It is also a good idea to install pgcrypto.sql on the template1 database.
If you want to include FedEx in the list of shipping options for your xTupleCommerce customers, you'll need to acquire API keys from FedEx, for both your production and development environments. Once you have the information and have added the keys to the ERP, the keys will need to be added to the xTupleCommerce website.
Here is an outline of the fields you need for both the production and development keys:
The job cost recognition options establish the default costing behavior when creating work orders for average cost or job items. These defaults can be overridden at the item site level or at the level of specific work orders you create. If the to date option is specified, all of the WIP costs accumulated to date will be charged to the cost of sales when the item is shipped. If the proportional option is specified, a value up to the proportional value of the total quantity shipped will be charged to the cost of sales when the item is shipped. For an example of the proportional method, assume 3 items are to be shipped on a job work order and all the material has been issued—and if only 1 of the 3 is shipped—then 1/3 of the value charged to WIP at that point will be charged to the cost of sales.
When using Qt Linguist for translation work, you will see references to "contexts" and "sources."
A context is a business object, like the contact screen or the bill of materials screen.
A source is a specific string of text within a context. For example the “Bill of Materials” context contains 56 sources, including “Print”, “Save”, “Revision Date”, etc.
There are two methods for importing data into the database of xTuple ERP.
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.
See our Product Roadmap for a general idea of when xTuple ERP will be released next and what the major upcoming features will be.
Our goal is to have two features releases a year (x.y.0), one in June and the other in December, plus a few bug-fix releases. This schedule is not exact. Feature releases will be published when their defining features are complete. Bug-fix releases will be published as needed. Between August 2007 and July 2016 we published a release on average every 8 weeks, not counting betas and release candidates. That included 21 feature and 38 bug-fix releases (on average a little more frequently than 6 months and 3 months, respectively).
Yes, beginning with xTuple Connect version 3.8, support is available for SSL and TLS encryption for email sent over SMTP.
The address you should enter in the billing configuration is your remit-to address. This address is used in multiple reports, including invoices.
In order to forcefully disconnect a user from the database, you have to find the Process ID (pid) for the backend connection of that user. Each user connection to the database spawns a backend process for their connection. Once you know the pid for the process, you can kill the process. On unix the command would be "kill [pid]" while other OSes may have different ways to kill a process. In order to find the pid you can look at the pg_stat_activity table and the column procid should contain the number you need.
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.
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.
There are no restrictions on the file types you can add to the database. Everything from office documents to image files to CAD drawings and more is supported.
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.
Because non-Inventory Items, by defintion, do not have Item Sites, you cannot view receiving information for them on an individual Site basis. That's why you have to select the "All Sites" option on this report to see your non-Inventory activity.
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.
For more information, please see the Qt Product Information.
Yes, the configuration of extensions (e.g., modules, like CRM) needs to be performed on each database used by your company. This flexibility allows you to configure different databases for different purposes. For example, let's say you want to pilot new features in a sandbox database. You would want to enable those new features in the sandbox for testing purposes. However, you wouldn't want to turn those features on in your production database until after you have piloted them.
There is no specific limit to the size of files you can store in the database. You can store everything from small files to extremely large files in the database.
Hint: Keep in mind that storing large files in your database will increase the size of your database and will require you to monitor your hard drive consumption.
If you are interested in starting a new language translation, please see the article "Starting a new translation project."
If you would like to include UPS in the list of shipping options for your xTupleCommerce customers, you'll need to acquire API keys from UPS. Once you have the information and have added the keys to the ERP, the keys will need to be added to the xTupleCommerce website.
Here are the instructions on how to retrieve the API keys from UPS:
Note: Most systems delete old keys when new ones are created. Your keys could be used across multiple systems so it’s a very good idea to create these keys once and save the information in a safe place for future use.
If you don't remember which version of PostgreSQL you're running, you can always find out with the following SQL statement:
This is easy to do if you're familiar with pgAdmin. Simply connect to your server with pgAdmin. Select one of your databases. Open the SQL editor tool. Paste in the above command. Then execute the query. Your PostgreSQL version will be displayed in the results window.