Setting system performance
The General > System Performance section allows you to enable or disable the full-text search functionality and limit the size of files that users can attach to Alloy Navigatorobjects.
Full-Text Search
If your Microsoft SQL Server installation includes the Full-Text Search component, you can enable the full-text search functionality in Alloy Navigator. When the full-text search functionality is enabled, the search engine provides fast results by operating on words and phrases contained in text fields.
INFO: For details on the Full-Text Search functionality, see Microsoft documentation, for example, Full-Text Search.
You can enable or disable the full-text search functionality in Alloy Navigator by the Enabled and Disabled radio buttons under Full-Text Search within the General > System Performance section. If your MS SQL Server installation does not include the Full-Text Search component, the Enabled and Disabled options in this section will appear dimmed and the corresponding warning will be displayed.
NOTE: If you are using Microsoft SQL Server 2005 with the Full-Text Search component installed and you want to enable the full-text search functionality in Alloy Navigator, make sure that Microsoft Full-Text Engine for SQL Server (MSFTESQL) service is running. In SQL Server 2008 and later versions, the Full-Text Engine resides in the SQL Server process (sqlservr.exe), and this check is not necessary.
To enable the full-text search functionality:
-
Under Full-Text Search, click Enabled.
-
Click Save on the Standard toolbar.
To disable the full-text search functionality:
-
Under Full-Text Search, click Disabled.
-
Click Save on the Standard toolbar.
Attachments
Under Attachments, you can put a limit on the size of attachments. Attachments are stored in the database, and large files attached to Alloy Navigator objects may significantly increase the database size and slow down Alloy Navigator. Alloy Navigator applies this limit to all attachments no matter whether their parent objects were created interactively or not. Specifically, when the Mail Connector encounters an incoming e-mail message with a large attachment, it will not attach that large file to the Alloy Navigator object but add a text file explaining that the message attachment has not been loaded due to exceeding the limit.
FOR CLOUD CUSTOMERS: Attachment size in our cloud (SaaS) instances is limited to 25 MB, and this limit cannot be increased. For details, see Installation Guide: Alloy Navigator Cloud (SaaS).
To limit the size of attachments:
-
Select the Limit attachment size check box and specify the limit in MB.
-
Click Save on the Standard toolbar.
To remove the size limitation:
-
Clear the Limit attachment size check box.
-
Click Save on the Standard toolbar.
Workflow Action Bar
The availability of workflow Step Actions is controlled by the user's security roles, the object’s type, and the object's status. In addition, some Steps may have additional criteria that control when the Step is available.
NOTE: You manage the availability of a Step on the Condition tab of the Step [ID] window. For details, see Configuring Steps.
Depending on the type of the object and effective permissions of the current user, some of the Steps are unavailable, and Alloy Navigator does not display commands for those Steps to the user. At the same time, some of available Steps may be disabled due to the status of the current object and/or the additional criteria.
Under Workflow Action Bar, you can specify whether to display dimmed commands for disabled Step Actions in the Actions menu and the Action Bar or hide those commands from users.
NOTE: The Workflow Action Bar option does not affect the visibility of Step Actions controlled by the user's security roles or the object's type.
To hide unavailable Step Actions from users:
To display unavailable Step Actions as disabled (dimmed):
-
Click Dim out unavailable Actions.
-
Click Save on the Standard toolbar.
For your changes to take effect, you and other users must restart the Desktop App and start a new Web App session.