CardFiles
CardFiles are records of the entities that you deal with, allowing for storage of address, contact and account term details. See the CardFiles topic for full details.
Term |
Explanation |
|---|---|
Customer CardFile |
An electronic record of an entity that you invoice for work carried out. If a card file is not a customer card file, you cannot invoice the entity. A card file can be both a customer and a vendor. |
Ship CardFile |
An entity address that you attend or ship to when completing work. A Ship card typically has a parent card file, which is the entity that you invoice for the work. |
User CardFile |
The entity record of a Jim2 user. |
CardFile Contacts |
Names and contact details of employees within a card file. This can also include contractors and sub-contractors, if necessary. |
Project
This will only show if you have Managed Services or Managed Print Services Editions. Used to batch jobs together for reporting and automation. A project may have a type, allowing differentiation of projects. Examples:
1.A project may represent a specific serialised pump, which can then have jobs linked to it.
2.A major works project requiring numerous jobs over an extended period.
3.An agreement with a customer to provide periodic preventative maintenance with the Project functionality, automatically creating the required jobs.
See the Managed Services Edition topic for more information.
Item
An Item (used only in jobs, quotes and projects) is used for three purposes:
1.To display the thing that is being serviced or repaired (eg. specific make and model of a pump).
2.To display the category of work being carried out (eg. onsite, rework).
3.To store a bill of materials for products that are manufactured.
See the Items topic for more information.
Throughout this Help file we refer to the term Jim2 objects, ie. CardFile, Jobs, Purchases, Items, etc. are Jim2 objects.
If the word Items appears in upper/lower case, it is not a general term and refers to the Jim2 object Items.