0
edits
Changes
→UTA Enhancements
* You can now set visibility logic on standard fields at all levels in the same manner that you set these conditions on custom fields.
* To set the visibility logic, navigate to the appropriate tandard field screen and enter the condition into the Visibility Condition column.
===[[Relating Contacts to the Universal Tracking Application#Tabs for Contact and Account Lists|Level 1: Tabs for Contact and Account Lists]]===
*If you associate a large number of contacts or accounts (companies) with Level 1 items, you can now display different users based on roles on different tabs (and different accounts based on account roles on different tabs).
* You can access the feature within the UTA Settings tab - Contact Tabs and Account Tabs hyperlinks in the Level 1 Settings section. You can associate as many tab names to roles as required. Tabs can also be deleted through the same screen.
===[[Relating Contacts to the Universal Tracking Application#Contact and Account Filters|Level 1: Contact and Account Filters]]===
* You can now configure visibility of the contacts/accounts associated with a Level 1 based on User Roles and Account Roles.
===[[Relating Contacts to the Universal Tracking Application#Tabs for Contact and Account Lists|Level 1: Tabs for Contact and Account Lists]]Restrictions===*If you associate a large You can now restrict the number of contacts or accounts (companies) belonging to a given [[Role]] that can be associated with a Level 1 items, you can now display different users based on roles on different tabs (and different accounts based on account roles on different tabs)record.:* You can access the feature within the UTA Settings tab - Contact Tabs and Account Tabs hyperlinks in the Level 1 Settings section. You can associate as many tab names to roles as required. Tabs This can also be deleted through the same screen. ===Disabling Specific Transaction Types by Template=== * You can now used to restrict the types total number of transactions available for each contacts that can be assigned to a Level 1 template typerecord.* If Level 1 Transactions are in use, within You can also restrict the Settings tab > Application Configuration, when you select one number of the times a given user can be assigned to a Level 1 templatesrecord, the Disabled Transaction Type section of check boxes will appear. One or many Transaction Types can be disabled per Level 1 Template. ===Contact Restrictions===You can now restrict the number of contacts belonging to times a given role that user can be associated assigned to the record with a Level 1 recordgiven [[Role]]. * To access this feature, click on the Contact Restrictions hyperlink on the UTA Settings tab.
===Multiple Contacts at Level 2===
===Level 2 Role Filtering===
You can restrict the selection of contacts associated with Level 2 items by role. Previously you could only restrict by specified named contacts. An additional lookup text area has been added the bottom of the Level 2 Types Settings page to specify the roles.
===Disabling Specific Transaction Types by Template===
* You can now restrict the types of transactions available for each Level 1 template type.
* If Level 1 Transactions are in use, within the Settings tab > Application Configuration, when you select one of the Level 1 templates, the Disabled Transaction Type section of check boxes will appear. One or many Transaction Types can be disabled per Level 1 Template.
===Level 3 Template Formulas===