Custom fields overview [in-depth guide]
Guide contents: Define custom fields | Considerations | Add custom field | Layout | Display types | Display when | Parent field | Reporting | Exceptions | Resources
This is where you can create and maintain custom fields that are used throughout the system based on your requirements.
NOTE: Custom fields that you make here do not automatically show up in reporting, nor are they available in our non-modifiable standard reports.
Define custom fields
To start creating custom fields, go to Menu > Admin/manager > System setup > Custom fields.
Workamajig provides you with the ability to add customized input and reporting fields to key parts of the system. Utilizing this functionality will allow you to more precisely tailor the system to the business needs of your organization and the needs of your client and vendors.
You can create custom fields that will be available in the following areas: employee, company, contact, project, campaign, retainer, conversation, and opportunity.
Plan it out
In some cases, you can re-purpose an existing field that is not being used instead of creating a new custom field. For example, if you want to report on a client's PO number, then we suggest you use the Client project number field that is already available on projects. As you can relabel the fields on invoice layouts and reports and use the field as is.
If you do have many fields you want to add, think of what you want to show and why (as you may not be able to delete the fields later). Then explore the options of how the fields are populated and displayed that best suit your needs.
Plan accordingly, as there are limits on the number of characters that can be used in each of the available fields, this includes spaces.
Description = 300
Hint = 300
User text input field = 8000
In the reports and views that allow custom fields to be included, you will see these custom fields called out with a "CF_" in front of the field name. For example CF_Contact_MyCustomFieldName.
Also, note that you do not want to use any special characters (ie. !@#$%^&*) in the field name or caption, as this can cause issues with reports.
Deleting custom fields
In most cases, you will not be able to delete a custom field once it has been used at least once, where a record populated that field with data.
If you are unable to delete the field, then we suggest you ensure it's removed from the Available fields, and then uncheck Active from the setup of the field.
Add a custom field
Go to Menu > Admin/manager > System setup > Custom fields.
Choose your area of interest.
For example, this is what you might see if you click on Opportunity fields.
Click the plus sign next to Available fields to add your first custom field.
You will then be prompted to add the field details.
Field name: Enter a unique identifier for this field. NOTE: You cannot use special characters or spaces. Also, it cannot be changed after the initial save of the field. The field name is what you will see in the available fields list when creating a custom report. So plan ahead.
Caption: Enter the field's name as you want your users to see it when filling it out. NOTE: Do not use special characters.
Display type: Determines how the field works. Refer to the Display type section of this guide for more info.
Description: For admin use only. Appears when editing a field to retain a description of what the field is used for.
Hint: If populated, appears below the fields display type function.
Required: Check this box to make the field a requirement when users save the related record.
Active: Check this box to make the field Active/Inactive for use in the layout editor.
Display when: See the Display when section later in this guide for more info.
Click Save when done.
NOTE: You can edit everything but the field name after the initial save.
Each section has its own layout. This determines what users will see when populating these fields in the system.
Drag and drop the fields you want to use and place them in the order of your choosing.
A text box containing only numeric values.
NOTE: Only numbers, plus signs, negative signs, and decimal points can be entered. The system will display any needed commas.
A text box containing a date value.
Clicking on the calendar icon will open a date picker.
A single-line text box containing that allows all alphanumeric values.
Will not expand into more rows.
Pressing enter will Save.
A multiple-line text box that allows all alphanumeric values.
Also allows the user to format the text that is entered. Such as bold, size, and color.
Will expand if more rows are needed.
Pressing enter will go to the next line.
Creates a single option to check or not check. Think of it as a Yes or No only option.
Allows the user to choose any options from a list of checkboxes.
If required, then at least one checkbox must be chosen.
Allows the user to choose one option from a list of multiple options.
A select box containing a list of pre-determined values.
If required, then an option must be selected to Save.
The display type of drop-down now has an added conditional formatting that can be used called Parent field. See the Parent field section of this guide for more on this aspect.
Allows you to create a visual break in the form and be able to label the line as well.
Tabs allow you to separate your custom fields into categories that the users can then click onto and fill out related fields without seeing all fields.
For tabs to function properly, the first field in your layout must be a tab field.
NOTE: If you have required fields under multiple tabs, keep in mind that the rules of the fields being required still apply before you can Save.
Simply adds the display-only text in the form of the caption and text.
This is similar to the drop-down menu, but you can have the user pick and choose options from the list.
This option allows you to have one or more fields appear based on the user input data of another field. You can only do one level of result fields, meaning you cannot create a drop-down list that then opens more drop-down lists and so on. So get creative with your use of this feature.
The order of your selected fields is very important. You will want to ensure you put the results field(s) below the selection field, or else you may get odd-looking results when the fields appear.
How is a basic example of how this looks to your users:
Click an option that is related to a Display when action.
Then the field appears based on the prior condition being met.
This allows you to create conditional values that appear within a dropdown selection based on the selection of the parent field. This differs from Display when, as that shows/hides fields from being inputted altogether.
NOTE: This function only works with the dropdown display type.
Set up the "to be" parent field with the initial set of options. In this case Web, Print, and Misc.
Then set up the "results" field that will display the available dropdown options based on what is inputted into the parent field.
Options with no :: in them, will always show in the results field, regardless of the value selected in the parent field. In this example, "Other" is that option.
Here is the above setup example in action.
If no selection is chosen in the parent field, then only the options with no :: appear.
If Web is chosen from the parent field, then the options starting with "Web::" appear. Plus, any options with no "::" before them.
If Print is chosen from the parent field, then the options starting with "Print::" appear. Plus, any options with no "::" before them.
If Misc is chosen from the parent field, then only the options with no "::" before them appear in the Results field selection.
Custom fields appear as "CF_FieldName" in reports. You can edit the caption of the column so its looks cleaner in the report itself.
NOTE: Only active custom fields will appear in the list of fields you can add. However, fields added before them being made inactive will still be part of the report.
If the report is not displaying any information, this usually means improper data was entered in a date or numeric field. To check, simply change the field type to 'text'. Run the report to find the errant data. You can then change the field type back to 'date' or 'numeric'. If you are not using the fields for calculation purposes in Excel, you may want to keep the field as text to prevent this error.
Employee custom fields: Since many use these fields for sensitive staff-based information, these fields are not available to add to views. These fields are only visible within the employee record or via the custom report datasets: Time detail data (with employee custom fields) and employee data.