RiSE

From the Staff site, go to Settings > RiSE > Quick setup:

These fields configure the basic global behavior of RiSE Content.

Note: All of these fields are duplicated in the other windows beneath Settings > RiSE > Quick setup. The presence of those fields in the default Quick setup window is meant to ensure that at least these very important basic configuration properties are set.
The Time zone (System.Database.TimeZoneId) setting can only be accessed at Settings > RiSE > Quick setup.

The default text in several of these setup fields includes text enclosed in brackets, such as [WebsiteName], [PageLinkURL], and so on. These are system variables that are replaced dynamically with context-specific information. You can remove them entirely if you do not want to use them, but you must not change them in any way if you plan to use them, or you will see unexpected results. If you are seeing unexpected results in the items these setup fields create the cause might be that some of these system variables were changed slightly. You can use the Reset to default value button to restore the default text (and therefore the original system variables).

• The path where the Image Manager should store images used in RiSE. The path should begin with ~/ and be a relative path from the website’s root folder. (CM.ImagePath) - Specifies the relative path of the file system folder on the iMIS application server and external web servers where images uploaded for use by CM should be stored. The root (~) of the path is the same as the physical path for the iMIS application in IIS (…\ASI\iMIS\Net by default). The default value for this field is ~/images.
• The maximum number of results returned for a search. (SE.MaximumResults) - Specifies the maximum number of search results that the system will display.
• The number of results to show per page. (SE.ResultsPerPage) - Specifies how many search results to display per page. If there is more than one page of search results, links are displayed at the bottom of each page that enable navigation among the result pages.
• Any content record with a Cache duration of “Default” will use this value. (CM.CacheDurationDefault) - Specifies the default system setting that will be used if Default is selected in the Cache duration field for a content record (Properties tab). Any content record with a Cache duration of Default will use this value.
• Content Item Allowed File Extensions (Asi.ContentItems.AllowedFileExtensions) - Specifies the file extensions you want to allow to be uploaded to the ContentItems folder in the Document system.

The following are the default allowed extensions:

• .js
• .html
• .htm
• .css
• .json
• .map
• .ts

Note: Some file extensions are always forbidden even if you enter them in the Content Item Allowed File Extensions field and remove them from the Content Item Forbidden File Extensions field.


• Content Item Forbidden File Extensions (Asi.ContentItems.ForbiddenFileExtensions) - Specifies the file extensions you want to forbid to be uploaded to the ContentItems folder in the Document system.

Note: Some file extensions will always be forbidden because they are in the default forbidden list, so even if they get added to the Content Item Allowed File Extensions field, they will not be allowed.

• Time zone (System.Database.TimeZoneId) - Set the time zone of an iMIS database instance independent of other databases that might be hosted on the same server. This ensures that the times generated are in the desired time zone for your organization.

Once this setting is specified during an initial setup, it is recommended that this setting not be modified.

If a web page has a calendar interface with Today selected, that date and time is based on the time zone of the machine on which the user interface is running.

Due to legal requirements related to Gift Aid (a program of HM Revenue and Customs), customers located in the United Kingdom must be hosted in the United Kingdom. The selected database time zone does not apply for UK customers; they must use a UK time zone.

Note: Once this setting is specified after installation, it is recommended that this setting not be modified. If you do modify the time zone on a database instance, there are several items to be aware of. For more information, see Configuring the system Time zone setting.

• Google Maps API keys [GoogleMapsKey] - In order to display a map using Google Maps, you must enter your Google Maps API key in this field. To learn how to obtain a Google Maps API key, see the Google Maps API documentation.

From the Staff site, go to Settings > RiSE > Page builder configuration.

These fields configure the global behavior of the Page Builder tool.

• The path where the Image Manager should store images used in RiSE. The path should begin with ~/ and be a relative path from the website's root folder (CM.ImagePath) - Specifies the relative path of the file system folder on the iMIS application server and external web servers where images uploaded for use by CM should be stored. The root (~) of the path is the same as the physical path for the iMIS application in IIS (C:\Program Files\ASI\iMIS\Net by default). The default value for this field is ~/images.
• With Content Manager, you can display multiple content records as a list of records. These content records may contain data types such as Word, Excel and PDF files. Similarly, you may upload multiple files to a single content record. This variable indicates whether or not the file type description should be displayed at the front-end next to the content record title (CM.ShowFileTypes) - Specifies which file extensions should prefixed before the content record's Title in the rendered results of a ContentTaggedList content item, if the content record contains a ContentFile content item that will download a file with the listed extension.
• Content Manager allows for the categorization and resultant display of content records based on date. This variable should be set to true if this above functionality is used, i.e. if a system that will prioritize search results, or display a new icon next to certain items is used (CM.UseImportantUntilDate) - Enables the behavior of the Mark as important until field in content records. When cleared, disables the field's behavior.
• The number of tries publishing servers will attempt before marking a content record as failed (CM.PublishingMaxNumOfAttempts) - Specifies how many times each publishing service will attempt to process a system publishing request for a content record before it flags the request as failed. This prevents overconsumption of system resources if there is a connection issue or other issue that is preventing the publishing service from successfully processing the request.
• Send email to content approver when content is requested for approval (CM.SendEmailOnApprovalRequest) - Sends an email to all people who have Content Approver permissions in at least one content authority group (CAG) to which they belong whenever anyone submits a content record publishing request. When cleared, disables email notification of publishing requests.
• Any content record with a Cache duration of "Default" will use this value (CM.CacheDurationDefault) - Specifies the default system setting that will be used if Default is selected in the Cache duration|topic= Configuration options: content records field for a content record (Properties tab). Any content record with a Cache duration of "Default" will use this value.

From the Staff site, go to Settings > RiSE > Search configuration.

These fields configure the global behavior of the search functionality.

• The message displayed to the user when no results match their search criteria (SE.NoResultsMessage) - Displays the message presented to the user when no results matching the search criteria were found.
• The maximum number of results returned for a search (SE.MaximumResults) - Specifies the maximum number of search results that the system will display.
• The message displayed when the user's search exceeds the value of the SE.MaximumResults variable. {0} will automatically be replaced by the value of the SE.MaximumResults variable (SE.ExceedMaxResultsMessage) - Specifies the search exceeded the maximum number of results set in SE.MaximumResults.
• The number of results to show per page (SE.ResultsPerPage) - Specifies how many search results to display per page. If there is more than one page of search results, links appear at the bottom of each page that enable navigation among the result pages.
• The message displayed to the user when there is an error running their search. {0} will automatically be replaced by the actual error message (SE.ProblemMessage) - Specifies what should be displayed to users when the search engine has a problem trying to perform the search. (This is not the same as when a search finds no results.) Adding the string {0} in this field passes through the system message for the actual error.
• Whether to display the Member Only Key in search results (SE.DisplayShowKey) - Displays a graphic icon shaped like a key next to every item in the search results list that is visible only to members of your organization. When cleared, no "key" icon is displayed even if the item is visible only to members. - Only users who are logged on to the website, and whose iMIS user record is associated with an iMIS contact record that is assigned a member type, will see this icon. For a content record to trigger this icon in search results, in the Properties section of the content record, the Content is restricted to members checkbox must be selected.
• This variable determines whether the variables SE.SearchKeywordHint, SE.SearchTitleHint, SE.SearchDescriptionHint, and SE.SearchBodyHint will be used to score results (SE.UseAdvancedRelevancy) - When enabled, uses the variables SE.SearchKeywordHint, SE.SearchTitleHint, SE.SearchDescriptionHint, and SE.SearchBodyHint to score search results.
• The weight of relevancy given to the body text of a record (SE.SearchBodyHint) - Specifies the search relevancy weighting given to results found in the body of the rendered content record (all the content item in the content record). The relevancy weighting for title, description, keywords, and body does not need to total 100. Instead, these weightings are both cumulative and relative to each other.
• The weight of relevancy given to the description text for a record (SE.SearchDescriptionHint) - Specifies the search relevancy weighting given to results found in the content record's Description/Summary field. The relevancy weighting for title, description, keywords, and body does not need to total 100. Instead, these weightings are both cumulative and relative to each other.
• The weight of relevancy given to the keywords for a record (SE.SearchKeywordHint) - Specifies the search relevancy weighting given to results found in the content record's Keywords/Metatags field. The relevancy weighting for title, description, keywords, and body does not need to total 100. Instead, these weightings are both cumulative and relative to each other.
• The weight of relevancy given to the title of a record (SE.SearchTitleHint) - Specifies the search relevancy weighting given to results found in the content record's Title field. The relevancy weighting for title, description, keywords, and body does not need to total 100. Instead, these weightings are both cumulative and relative to each other.

Staff users can configure the items that will be removed from the search index. Staff users can deselect specific index categories. Deselecting these index categories will remove these items from the existing index.

The following categories can be deselected:

• Contacts
• Events
• Posts
• Products and donation items
• Communities

Once the Staff user has made their changes and clicked Save, items from those categories will no longer be available in the search index.

Note: You must click Save after selecting or deselecting any category in order for the changes to take effect.

If previously disabled categories are re-enabled, items from these categories are automatically re-indexed.

Note: You can rebuild the search index through this page for the categories listed. For information about rebuilding the search index for content, see Rebuilding the search index for content.

From the Staff site, go to Settings > RiSE > Process automation.

These fields configure the global behavior of the Process automation feature:

• Number of days to retain successful task logs (DeleteSuccessLogsAfter) - Enter any numeric integer value to represent the number of days the database will retain the successful task logs until they are removed. For example, if the value 30 was entered, the logs presently display all of the Succeeded logs for the past 30 days.
• Number of days to retain failed task logs (DeleteFailedLogsAfter) - Enter any numeric integer value to represent the number of days the database will retain the failed task logs until they are removed. For example, if the value 90 was entered, the logs presently display all of the Failed logs for the past 90 days.
• Number of days to retain completed task logs (DeleteCompletedLogsAfter) - Enter any numeric integer value to represent the number of days the database will retain the completed task logs until they are removed. For example, if the value 1 was entered, the logs presently display all of the Completed logs for the past day.

Note: In the RiSE Workflow Settings window, be sure to change the default values of the ND.ExpirationEmailFromAddr and CM.ExpirationEmailFromAddr fields to the email address of a person in your organization.

You must be a member of the iMIS SysAdmin security role to access the Set up content management features.

These fields configure the global behavior of content authoring workflow. By default, these fields are found in the following locations:

From the Staff site, go to Settings > RiSE > Workflow configuration.

In the following fields that specify the variables Individual.FirstName and Individual.LastName, you can use any property from the Individual business object as long as you can express it with the format Individual.[property].

• Optional. The number of days before the expiration date of navigation items to give the first warning (ND.ExpirationWarningDays1) - Specifies the number of days before a navigation item has expired to send the first expiration warning email (ND.ExpirationWarningText). This value must be larger than the value specified for ND.ExpirationWarningDays2.
• Optional. The number of days before the expiration date of navigation items to give the second warning (ND.ExpirationWarningDays2) - Specifies the number of days before a navigation item has expired to send the second expiration warning email (ND.ExpirationWarningText). This value must be smaller than the value specified for ND.ExpirationWarningDays1.
• Optional. The number of days after the expiration date of navigation items to give the final warning (ND.FinalExpirationNoticeDays) - Specifies the number of days after a navigation item has expired to send the additional expiration notice email (ND.AddExpNoticeText).
• Optional. The number of days before the expiration date of content items to give the first warning (CM.ExpirationWarningDays1) - Specifies the number of days before a content record has expired to send the first expiration warning email (CM.ExpirationWarningText). This value must be larger than the value specified for CM.ExpirationWarningDays2.
• Optional. The number of days before the expiration date of content items to give the second warning (CM.ExpirationWarningDays2) - Specifies the number of days before a content record has expired to send the second expiration warning email (CM.ExpirationWarningText). This value must be smaller than the value specified for CM.ExpirationWarningDays1.
• Optional. The number of days after the expiration date of content items to give the final warning (CM.FinalExpirationNoticeDays) - Specifies the number of days after a content record has expired to send the first additional expiration notice email (CM.AddExpNoticeText). This value must be smaller than the value specified for CM.ExpAdditionalDays.
• Optional. The number of days after the expiration date of content items to give an additional notice (CM.ExpAdditionalDays) - Specifies the number of days after a content record has expired to send the second additional expiration notice email (CM.AddExpNoticeText). This value must be larger than the value specified for CM.FinalExpirationNoticeDays.