To access these options
- Expand the Build Tables menu in the lefthand sidebar
- Select the table you wish to edit
- Click the pencil icon in the toolbar to edit the table, then select the table’s manage tab
- Click the Options button
If this is ticked (it is by default), users can add records to the table. Anyone with manage privileges on the table can add tables regardless.
Only from within tab
If this is ticked, users can add records but only when accessing this table’s form from within a tab of a parent record. This can help ensure that child records are always connected to a parent and aren’t created as ‘orphans’.
(Off by default). Show a clone record button when a user is viewing a record. This makes a simple copy of all data in the record. The contents of tabs are not cloned. A more advanced clone facility can be created with a workflow if desired.
(On by default). Allow records to be deleted by people with EDIT privileges as well as people with MANAGE privileges, who can always delete.
Showa button which allows links to individual records to be shared between users using email. Note - recipients still need a login and relevant privileges to see the record.
When a record’s created, run this workflow
Run a workflow immediately after the creation of a record. The workflow runs after any field default values have been set.
The workflow ‘knows’ metadata such as which user is logged in, which tile is open etc., so if you want to use those in a calculation in the workflow, you can do.
Run this workflow whenever each record is viewed
As well as running the workflow on record creation, also run it whenever a user views a record in this table. Be aware this may have a performance impact for users, if the workflow is resource intensive and/or multi-step.
Data entry from external sources
The options in this section are for configuring the table to allow an API request from an external source to create and edit records. See API usefor more information.
Records can be locked to prevent editing. You may like to do this based on criteria e.g. once a customer order has been sent, it should be locked against further changes.
To actually lock the record, a workflow can be used.
Locked records can be manually unlocked by someone with manage privileges on the table, but only one at a time.
When someone adds a comment to a record, when selecting recipients, they have the option to email those recipients, as well as adding the comment to the comment stream. Ticking this table option sets the default to send emails for any comment added to this table. Users can override this on an individual comment basis and recipients can override in their notification preferences.
Flag records with colour
Enter a field name here and add a field with the same name to a view, to flag records. The contents of the field must be one of the colour names as given on the screen. The field added to the view can be a calculation, specifically a hidden calculation. This will flag the view without showing the colour name on screen.
This option can also be used to colour items in a junction chooser (see tab option: Choose a record when a new item is added). In the junction table, set this option, then in the view used as a relation picker (set in the relation field options), add the colour calculation.
Accept emails to this address
The system can accept incoming emails and attach them to relevant records e.g. attaching an email from a customer to that customer’s record.
A particular email address can be set up to receive emails. The system can be configured to either accept emails from anyone, or just from users. If just from users, then users can forward any emails they receive to the system to have them imported, or BCC the address when sending to people.
The email text will be logged as a comment against the record, with the full email attached if it is HTML formatted or includes attachments. The table must have a comments field.
Please contact us if you’d like to set that up.
Emails are matched by creating a view containing the email addresses of potential recipients. An incoming email is attached to the record from this view which matches the sender’s email address. If there is no match, it is added to a ‘holding bay’ where users can view and manually attach emails to records.
Configuring the email address used
- viewname determines the view which agileBase queries to find the recipient email address. The comment will be added to the matching record in the view’s parent table, or a tab of the table, if Accept emails from parent table is enabled in a tab. If multiple tabs have this option enabled, then the tab with a name also matching viewname is used
- accountname determines the company account to look in
- domainname is the domain name of the agileBase server
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.