This came from a question - How to add a new item to an existing drop-down list?
It would be sensible to allow an option where ACT administrators can change the drop down list without having to go to Tools - Define Fields which means it throws everyone of the database or has to be done out of hours.
Simply allow an ACT administrator access to the dropdown list even when do not allow editing is ticked in the Define Fields area without having to go to define fields.
As a database administrator it would be useful for the inactivity timeout preference to be stored on a database level, and configurable through the Preferences pane when logged in via Web. This allows for a database administrator to customise the setting without needing to edit the web.config file or contact Act! Premium Cloud support.
The Import Wizard should have the default set at Custom by the Act! developers - it best to do this always to 'eyeball' the field selection.
Never use the 'Typical'!!
Currently a parity issue between APFW and Desktop - see screen shots below.
Adding to request feedback on this feature request.
Add Primary Fields column to Define Fields List for faster recognition of which fields are Primary FieldsStatus: Submitted for voting
Currently there are two ways to tell which fields are Primary Fields:
Option A: Go to Tools > Define Fields, then individually open the field and check to see if "Primary Field" is checked
Option B: Run a Field Detail report in Act! Diagnostics and swim through thousands of lines of text that, looking for the correct table and the correct field, and that line of text that says "Primary: True"
Both options are rather time consuming, and while Field Reports are useful for those who are a little more technically savvy, Option B is not very end-user friendly. I believe that this could be made more efficient and user friendly if a Primary Field column could be added in the Define Fields list, much like there's already a column that explains what Company Field a particular field is linked to, if any. For example:
The column could go next to the "Linked to Company Field" column and it would make it much faster to discern whether or not a field is a Primary field.
We receive as many e-mails as we send, and we receive them frequently, so why is this not an Activity option?
This is important now that the aAdd to Act Contact functionality in Outlook no longer works, with apparently no fix on the horizon - if at all.
Heard he was coming on board in some capacity. Hope they listen to him. Good product needs work.
Need support people that can speak english more clearly. Very frustrating talking with people in India that have thick accents and english is 2nd language. Simply obvious.
ACT needs to change the ability to set Privacy Preference for each activity as it was in previous versions.
For example: be able to make Meetings Public and To-Do's Private.
Simple thing that would really improve the product.
I would like to suggests that when using the opportunity list view expanding the size of the contacts column would allow all contacts linked to the company to be displayed in the list view. as currently it will still just display the contact that is alphabetically first with an ellipsis. this is not helpful when using this feature to track the opportunities associated with both dealer salesmen and end users.
I was merging two records this morning and it occurred to me that it is not infrequent when only a few fields have to be merged.
In fact, most of the fields were either blank or the same in both records.
So, my recommendation is to see if it is possible to eliminate from the merge process all fields that are the same in both records - either blank or the same data.
This would be particularly useful to us who have added a plethora of fields and same time as well.
Perhaps it would be helpful if you flagged the 4GB limitation next to the "Migrate existing data" button in the welcome email. Might save a bit of heartache. ;-)
Please allow users to select multiple Companies or Divisions in the Company list, right-click and Move. If all of the selected Companies are Divisions, allow them to promote them all. If they are all Companies, Divisions or a combination of, allow them to be moved under a new Company.
I would like to suggest that the existing Knowledge Base be updated to reflect the status of ACT! today and become more relevant to the latest versions.
Over time the KB has has grown with the release of new versions of the product and the Answer IDs need to be targeted towards the Versions in use.
While I realise that there are still users of the product older than 10 years , and my own experience goes back to ACT! 4,
it is perhaps time to move these older Answers IDs to a separate KB dealing with Obsolete or Obsolescent versions which are cluttering the KB.
I would suggest ant version older than 5-6 years should fall within this category since it is unlikely that SwiftPage Administrators want to be reviewing problems that should have been addressed and resolved during the life cycle of the older products.
In Updating the KB to reflect the current versions it is important that the Answer ID reflect the latest status Update Date and removes any reference to the older KB articles that are no longer relevant to Operating Systems earlier than Windows 8 or perhaps Vista at a pinch.( to cater for those users that have not kept up their systems maintenance.) Many of the existing problems with ACT! relate to the effects of Windows 10 and associated SQL Versions.
We do not need the KB cluttered with Obsolete and irrelevant History
One of the useful additions to Act! was the automatic "Last Reach", "Last Attempt", "Last Letter" etc System generated fields.
What would be really useful would be the ability to define new fields like these based on User Defined Activities.
So, for example, a customer wants to differentiate between a standard Meeting and a user defined "Maintenance Visit", they could schedule a "Maintenance Visit" for their engineer in the Calendar and, when Cleared, the system would automatically generate a date in the "Last Maintenance Visit" field. This field could then be available to Lookups or, indeed, Smart Tasks to better manage customer service.
i would like to see it possible to add more fields to the product table. currently we only have Description, Item#, Price and Cost, is would be great if we can add (as many) fields to this table as needed. So that i can use it, for example, as multi language product description (english, german, dutch) and make a template (currently with Excel Quote Invoicemaker) in multi languages, add manufacturer to the product, more pricing options.
At the moment, when you send an AEM mailer, the system records the date and time, the sender and the subject line of the email. This information also appears the call lists.
I would like an additional field, Campaign Name, that the recipient doesn't see, where I can describe the campaign in whatever detail I want in order to organise and sort multi-stage compaigns.
For example, I might have a mailer with a Subject line of " New Act is now available", but I might want to send it on multiple occasions to different groups. I could therefore use the Campaign Name to record "New Act V19.2 Mailer to Architects send 3 of 12".
Makes it easier to sort reports and call lists later.
The zip file that is created during a manual backup is: Act!+databasename.zip
I suggest that the Act! version number be added to the backup file name, or using the same naming as Act! Scheduler does.
A customer of mine recently did a manual backup, installed Act! v19 and did a new backup, overwriting his old backup, got problem with the installation and installed his old version of Act! just to find that the backup contained the v19 database and not his old one.
Of course he did not have any old backups saved.
This has happened before and will happen again.