Managing System Settings

Intro

Users with appropriate rights can access the “System” page in order to manage settings that affect the behavior of the ArcReporting environment for all users of the system.

Examples of such settings include:

• The amount of time users’ login sessions remain open when no user input/activity in ArcReporting is detected.
• The amount of time before prompting a user to re-enter his or her password, when no activity is detected for the browser window in which ArcReporting is running.
• Whether users may open more than one login session at a time.
• The frequency with which the ArcReporting messaging system checks for new messages and updates the Messages interface.
• The refresh interval for statuses of output requests in the Output Queue interface.
• The Output Rule Package used for custom processing of portfolio statement data.
• etc.

Tasks

• Specifying login session timeout (due to inactivity)

  When a user logs into the Arc Suite platform, he or she creates what is known as an active login “session”. You can define how long the session will remain active if no activity for the user is detected. Once the specified time has elapsed, a message will display to alert the user that his or her session has expired and that he/she has been logged out.

  

  To specify the length of time any given user’s session will remain active/open, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the time to wait (in minutes) for the “SessionLifeSpanInMinutes” item in the “System Settings” grid.

     In this example, the user would be logged out after 45 minutes of inactivity.

     • The default setting for your environment is “45”.
     • The value of this setting must always be greater than the value of the “SessionExpirationWarningInMinutes” setting.

  4. Click the “Save” button at lower-right of the page.

• Specifying the time before a screen lock displays (due to user inactivity in Arc Suite)

  When a user logs into the Arc Suite platform, he or she creates what is known as an active login “session”. If a user is not actively using Arc Suite, but his/her login session is still open, you can specify how long to wait before a screen lock displays for the browser window in which Arc Suite is running.

  

  • This setting and its associated user notification are only applicable to DFIN-managed SSO environments (i.e., the setting has no effect in client-managed SSO environments).
  • The screen lock applies to the current user only; other users with active login sessions may continue to work in Arc Suite from their own computers.
  • Any activity for the current user that may be in process at the time the screen lock displays (e.g., document processing, filing submission to the SEC, etc.) will continue uninterrupted.

  The screen lock requires the user to re-enter his or her password before allowing him or her back into the current session.

  Whether a user has stepped away from his or her desk to attend a meeting or go to lunch, or is simply performing other tasks on his or her computer, the screen lock will prevent unauthorized use of Arc Suite for the current login session once the specified time has elapsed.

  To specify the time to wait before prompting users to re-enter their password, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the time to wait (in seconds) for the “ActivityTimeoutInSeconds” item in the “System Settings” grid.

     In this example, the screen lock would display after 20 minutes (1200 seconds) of inactivity.

     The default setting for your environment is “1200”.

  4. Click the “Save” button at lower-right of the page.

• Specifying the timing of login session expiration notifications

  When a user logs into the Arc Suite platform, he or she creates what is known as an active login “session”. A session will automatically expire after a specified amount of time if no activity for the user is detected.

  

  The system can alert users that their session is about to expire, and you can specify how long beforehand they receive such alerts.

  To specify when a session expiration notification will display for any given user, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the amount of time (in minutes) for the “SessionExpirationWarningInMinutes” item in the “System Settings” grid.

     In this example, the user would receive an alert that his or her session will expire 3 minutes before the system automatically logs him/her out.

     If the user clicks the “OK” button on the alert dialogue, his or her login session is renewed and he/she will not be logged out.

     • The default setting for your environment is “5”.
     • The value of this setting must always be less than the value of the “SessionLifeSpanInMinutes” setting.

  4. Click the “Save” button at lower-right of the page.

• Specifying the timing of password expiration notifications

  Arc Suite employs an internal messaging system that permits communication between administrators and system users. It can also notify users about upcoming events and deliverable dates, etc.

  The system can alert users that their login password is about to expire, and you can specify how long beforehand they receive such alerts.

  This setting and its associated user notification are only applicable to DFIN-managed SSO environments (i.e., the setting has no effect in client-managed SSO environments).

  To specify when a password expiration notification will be delivered for any given user, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the amount of time (in days) for the “PasswordExpirationNotificationInDays” item in the “System Settings” grid.

     In this example, the user would receive an alert in his or her message box that his/her password will expire in 14 days.

     The default setting for your environment is “14”.

  4. Click the “Save” button at lower-right of the page.

• Allowing for multiple login sessions per user

  When a user logs into the Arc Suite platform, he or she creates what is known as an active login “session”. An attempt by a user to log into the system again from a different computer would cause his or her existing session to be closed, and any unsaved changes that he/she might have effected would be lost as that session was closed.

  If users may have occasion to carry out their Arc Suite tasks while working at more than one computer, you can facilitate their so doing by configuring your environment to allow multiple login sessions per user. Follow the steps outlined below to allow multiple sessions.

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “AllowMultipleSessions” item in the “System Settings” grid to “True”.

     • The default setting for your environment is “False”.

       • If this value is specified, an attempt by a user to log into the system from more than one computer causes his or her existing (first) session to be closed, and any unsaved changes he/she might have effected in that session to be lost.

     • A setting of “True” enables multiple login session functionality.

       • If this value is specified, a user may log into the system from more than one computer without affecting any existing session(s) that may already be open.

  4. Click the “Save” button at lower-right of the page.

• Specifying the Output Queue refresh interval

  The status of Arc Suite project output that has been submitted to the document processing service, or the status of filings submitted to the SEC, can be monitored via the Output Queue at far upper-right of the screen.

  You can specify the interval at which the queue checks for updated statuses (i.e., how often the queue is “refreshed”) by following the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the queue’s status retrieval interval (in seconds) for the “OutputQueueRefreshTimeInSeconds” item in the “System Settings” grid.

     In this example, users’ Output Queue would automatically be refreshed (to display the current status of output requests) every 5 seconds.

     The default setting for your environment is “5”.

  4. Click the “Save” button at lower-right of the page.

• Specifying the messaging system refresh interval

  Arc Suite employs an internal messaging system that permits communication between administrators and system users. It can also notify users about upcoming events and deliverable dates, etc.

  You can specify the interval at which the messaging system checks for new messages (i.e., how often it “refreshes” users’ message boxes) by following the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the message retrieval interval (in seconds) for the “MessageRetrievalIntervalInSeconds” item in the “System Settings” grid.

     In this example, users’ message boxes would automatically be refreshed (to display any messages that had been awaiting delivery to them) every 60 seconds.

     The default setting for your environment is “60”.

  4. Click the “Save” button at lower-right of the page.

• Specifying the filing mode for N-MFP1 submissions

  Arc Suite allows users to submit N-MFP1 data in one of several predefined modes via the “Filing Manager” page. The mode used is specified at the environment level.

  To specify the filing mode, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the desired setting for the “NMFPFilingMode” item in the “System Settings” grid.

     • The default setting for your environment is “Simulation”.

       • If this value is specified, a submitted filing will be sent to the SEC Simulator, either as a “Test” or “Live” submission type, as specified by the user.
     • A setting of “SEC - Test” causes a submitted filing to be sent to the SEC as a “Test” submission type (the “Live” option for “Submission Type” will be disabled on the “Submit Filing” dialogue).
     • A setting of “SEC - Live” causes a submitted filing to be sent to the SEC, either as a “Test” or “Live” submission type, as specified by the user.

  4. Click the “Save” button at lower-right of the page.

• Specifying the XML generation mode for N-MFP1 submissions

  Arc Suite allows users to submit either actual or sample N-MFP1 data via the “Filing Manager” page. The data generation mode used is specified at the environment level.

  To specify the type of data generated and submitted, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the desired setting for the “NMFPXMLGenerationMode” item in the “System Settings” grid.

     • The default setting for your environment is “<blank>” (i.e., the “System Settings” cell contains no value.

       • If no value is specified, actual N-MFP1 data populates the XML filing.
     • A setting of “hardcoded” causes the XML filing to be populated with hard-coded sample data.

  4. Click the “Save” button at lower-right of the page.

• Specifying timeout for N-MFP1 submissions (due to lack of response from recipient)

  Arc Suite allows users to submit N-MFP1 data to the SEC and/or the ICI via the “Filing Manager” page.

  To specify the length of time to wait for a valid submission status from the filing recipient, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the time to wait (in minutes) for the “NMFP2FilingTimeOutInMinutes” item in the “System Settings” grid.

     In this example, the filing submission attempt would time out after 60 minutes (1 hour), if no valid status is returned from the recipient.

     The default setting for your environment is “60”.

  4. Click the “Save” button at lower-right of the page.

• Specifying the URL for output processing

  Information contained in the Arc Suite database can be exported to a number of different formats, some of which require content processing prior to creating the final output document. Communication between your Arc Suite environment and the processing service is achieved through the specification of a unique URL via the “System” page.

  To set the URL that your environment will use, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the URL for the “AutoCompUrl” item in the “System Settings” grid.

     This URL can be obtained through your Donnelley Financial Solutions liaison.

  4. Click the “Save” button at lower-right of the page.

• Specifying the project output revisions grid refresh interval

  The status of Arc Suite project-, chapter- and section-level output that has been submitted to the document processing service can be monitored via the revisions grid on the “Output Management” tab of the “Project” page.

  You can specify the interval at which the system checks for updated statuses (i.e., how often the revisions grid is “refreshed”) by following the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the revision grid’s status retrieval interval (in seconds) for the “ProjectOutputRevisionGridRefreshTimeInSeconds” item in the “System Settings” grid.

     In this example, the grid would automatically be refreshed (to display the current status of output requests) every 10 seconds.

     The default setting for your environment is “10”.

  4. Click the “Save” button at lower-right of the page.

• Enabling audit logging across all application pages

  The Arc Suite platform features an internal auditing mechanism to track changes to all application data. The logged data is typically not visible to end users, except where leveraged in the various application audit reports (e.g., “Securities Audit Report”, “Text Snippet Audit Report”, “Fund Data Points Audit Report”, etc.). However, the data is used by Arc Suite support staff for troubleshooting purposes, as necessary.

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To enable generic audit logging across all application pages, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “DefaultAuditLoggingEnabled” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables generic audit logging functionality.

  4. Click the “Save” button at lower-right of the page.

• Specifying logging settings for financial/portfolio statement calculations

  For troubleshooting purposes, Arc Suite internal staff use the “CalculationLogging” system setting to track when financial or portfolio statement calculations are triggered, and when calculation statuses are reset to “Not Calculated”. The verbosity of the logged information can be adjusted, according to the value specified for this setting.

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To specify the calculation logging setting, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the desired setting for the “CalculationLogging” item in the “System Settings” grid.

     In this example, the logging functionality is enabled (using a setting value of “On”), and the log will record all available information pertaining to statement calculations.

     • The default setting for your environment is “On”.
     • A setting of “Off” disables calculation logging functionality.
     • Other settings to adjust data verbosity/granularity will be available in future product releases.

  4. Click the “Save” button at lower-right of the page.

• Specifying the timing of automatic project creation with respect to account periods

  By default, Arc Suite automatically creates account period-specific instances of project templates 15 days prior to the end of the current account period. The “AutoCreateAccountPeriodDaysBefore” system setting allows you to adjust the timing of automatic project creation to suit your production schedule.

  This is a database-level setting and therefore affects all projects within the database.

  To specify the timing of automatic project creation, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the desired value (in days) for the “AutoCreateAccountPeriodDaysBefore” item in the “System Settings” grid.

     In this example, projects will be automatically created 15 days prior to the end of each account period.

     • The default setting for your environment is “15”.

     • Numeric values between “-28” and “28” are valid; the effect of specific values is as follows:

       • A value of “0” causes new projects to be created on the end date of the current account period.
       • A non-numeric or blank setting causes new projects to be created on the end date of the current account period (same effect as a value of “0”).
       • Any value between and including “1” and “28” causes new projects to be created the specified number of days before the current account period end date.
       • Any value between and including “-1” and “-28” causes new projects to be created the specified number of days after the current account period end date.

     • The following figure offers examples of the effect of various values on different reporting periods:

       

  4. Click the “Save” button at lower-right of the page.

• Specifying the automatic association of new account periods with applicable complexes

  By default, Arc Suite automatically associates (and opens) a newly-created account period with all the applicable complexes, based on their project templates’ reporting cycles. The “EnableAutoAssociateComplexAccountPeriods” system setting allows you to specify whether or not that action is carried out.

  This is a database-level setting and therefore affects all projects within the database.

  To disable auto-association of new account periods with complexes, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableAutoAssociateComplexAccountPeriods” item in the “System Settings” grid to “False”.

     The default setting for your environment is “True”. This setting enables account period auto-association and opening functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling grid pagination for Fund Holdings

  To make the “Fund Holdings” page more responsive when dealing with large data sets in the “Holdings” tab, enable grid pagination functionality by following the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “FundHoldingsGridPagination” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”. A setting of “False” disables grid pagination functionality.

  4. Click the “Save” button at lower-right of the page.

• Specifying the number of records loaded to the Fund Holdings grid at once

  To make the “Fund Holdings” page more responsive when dealing with large data sets in the “Holdings” tab, specify the number of records to load into the grid at once by following the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the per-page number of records for the “FundHoldingsGridPageSize” item in the “System Settings” grid.

     In this example, 1,000 records at a time would be loaded in the grid .

     • The default setting for your environment is “1000”.
     • The “FundHoldingsGridPagination” setting must be set to “True” in order to use grid page size functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling project output logging

  Arc Suite support staff use certain database information surrounding project output events for troubleshooting purposes. The “OutputLogging” system setting allows them to turn output logging functionality on or off, as necessary.

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To specify that project output logging be enabled, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “OutputLogging” item in the “System Settings” grid to “On”.

     The default setting for your environment is “On”. A setting of “Off” disables output logging functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling circular reference checking functionality

  For troubleshooting purposes, Arc Suite internal staff use the “CircularReferenceCheck” system setting to enable/disable logic that evaluates user-defined formulas. When in use, the mechanism can reduce application performance significantly (i.e., increase the time it takes to generate project output).

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To enable circular reference checking functionality, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “CircularReferenceCheck” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”. This setting value disables circular reference checking functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling multi-threaded calculations for statement output

  During project output, Arc Suite carries out many mathematical calculations in order to produce the values that display in portfolio and financial statements. Arc Suite features the ability to calculate these values using multiple “engines” or “threads” at once, which can increase performance significantly (i.e., reduce the time it takes to generate project output).

  To enable multi-threaded calculations for statement output, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableOutputMultiThreadedCalculations” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables multi-threaded calculation functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling calculation claiming logic for statement output

  Arc Suite contains optional “calculation cliaming” logic that ensures calculation requests are carried out in the required sequence, for only unlocked funds and account periods.

  To enable calculation claiming logic for statement output, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableSmartCalculationClaiming” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables calculation claiming functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling bulk saving of calculation sheet value detail information

  By default, the detail information of calculation sheet values in Arc Suite is saved to the database row-by-row. The application also provides an option to save such information “en masse”, which can be more efficient.

  To enable bulk saving logic for calculation sheet value detail information, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableCalculationSheetValueDetailBulkSave” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”. A setting of “False” disables bulk saving functionality for calculation sheet value details.

  4. Click the “Save” button at lower-right of the page.

• Enabling multi-threaded evaluation of a statement’s conditional value(s)

  During project output, Arc Suite evaluates specific properties of a given portfolio or financial statement, according to user-defined conditional formulas, in order to produce the values that display in that statement. Arc Suite features the ability to evaluation these conditions using multiple “engines” or “threads” at once, which can increase performance significantly (i.e., reduce the time it takes to generate project output).

  To enable multi-threaded evaluation of statement conditional values, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “MultithreadedConditionalValueEvaluation” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”. This setting value disables multi-threaded conditional value evaluation functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling calculations for large portfolio data sets

  Arc Suite carries out many mathematical calculations in order to produce the values that display in ArcReporting portfolio and financial statements, particularly when the data set is large. Arc Suite features the ability to calculate these values using an alternative, optimized process, which can increase performance significantly (i.e., reduce the time it takes to calculate values).

  To enable this functionality, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableSmartPortfolioCalculation” item in the “System Settings” grid to “True”.

     • The following setup is required to use the new portfolio calculation mode:

       • Holdings data points used in calculation sheets or within a portfolio statement (e.g., “aggregation”) must be included in the “Calculations” tab grid on the “Portfolio Statement Templates” page.

         • If the portfolio statement is pulling from the fund’s primary statement, the data point(s) must be on the “Calculations” tab for that statement.
     • The default setting for your environment is “True”. A setting of “False” disables optimized portfolio calculation functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling bulk saving of portfolio statement values

  By default, the portfolio statement values in Arc Suite are saved to the database row-by-row. The application also provides an option to save such information “en masse”, which can be more efficient.

  To enable bulk saving logic for portfolio statement values, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnablePortfolioStatementValuesBulkSave” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables bulk saving functionality for portfolio statement values.

  4. Click the “Save” button at lower-right of the page.

• Enabling preview of large portfolio data sets

  Arc Suite carries out many mathematical calculations in order to produce the values that display in ArcReporting portfolio and financial statements, particularly when the data set is large. Arc Suite features the ability to calculate these values using an alternative, optimized process, which can increase performance significantly (i.e., reduce the time it takes to view and output values).

  To enable this functionality, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableSmartPortfolioPreview” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables optimized portfolio preview functionality.

  4. Click the “Save” button at lower-right of the page.

• Specifying the Output Rule Package for use in custom processing of portfolio statement data

  Portfolio statement information contained in the Arc Suite database can be processed according to custom parameters defined for use by your specific Arc Suite environment. Such processing definitions are contained in Output Rule Packages. The one used by your environment is specified via the “System” page.

  To set the rule package that your environment will use, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the package name for the “PortfolioOutputRulePackage” item in the “System Settings” grid.

     The package name for your environment can be obtained through your Donnelley Financial Solutions liaison.

  4. Click the “Save” button at lower-right of the page.

• Enabling execution of portfolio statement inline processing rules

  Portfolio statement information contained in the Arc Suite database can be processed by custom inline rules created for use by your specific Arc Suite environment. Whether or not inline portfolio statement rules may be run is specified via the “System” page.

  To specify that any configured inline rules be skipped during statement output, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “RunPortfolioInlineRules” item in the “System Settings” grid to “False”.

     The default setting for your environment is “False”. A setting of “True” allows any configured inline rules to be run.

  4. Click the “Save” button at lower-right of the page.

• Specifying processing method for EDGAR (HTML) output

  Project output of type “EDGAR (HTML)” can be processed by the Arc Suite processing service using either ShowXSF or DIV XML, depending on a given client’s needs and setup.

  To specify that “EDGAR (HTML)” output be processed using DIV XML, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “DIVXMLUseForEDGARHTML” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”. This setting value causes “EDGAR (HTML)” output be processed using ShowXSF.

  4. Click the “Save” button at lower-right of the page.

• Specifying processing method for Word output

  Project output of type “Word” can be processed by the Arc Suite processing service using either ShowXSF or DIV XML, depending on a given client’s needs and setup.

  To specify that “Word” output be processed using DIV XML, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “DIVXMLUseForWord” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”. This setting value causes “Word” output be processed using ShowXSF.

  4. Click the “Save” button at lower-right of the page.

• Enabling smart style logic for language-specific project output

  The length of textual content in a given project component (i.e., how much space it occupies) may differ dependent on the language that content is displayed in. This can affect page breaking and other aspects of style in project output. The ArcReporting output processor can account for such language-related differences in content length when the “EnableLanguageOnArcMLSection” system setting is turned on.

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To specify that smart style logic for language-specific project output be enabled, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableLanguageOnArcMLSection” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”. A setting of “False” disables smart style logic functionality for language-specific output.

  4. Click the “Save” button at lower-right of the page.

• Enabling use of the legacy publishing engine version for one or more complexes

  The logic used for publishing ArcReporting document output is updated occasionally, according to client needs and/or regulatory requirements. Typically, such updates do not impact existing document implementations, however there may be a need in some cases to temporarily continue publishing one or more documents using an older (“legacy”) version of the publishing engine.

  The “UseLegacyPublishingVersion” system setting allows you to either use the latest publishing engine version for all document output, use the legacy publishing engine version for all document output, or use the legacy version for only those documents associated with one or more specified complexes.

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To specify publishing engine version settings for your documents, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the “UseLegacyPublishingVersion” item in the “System Settings” grid to one of the following values.

     • “False”
     • “True”

     • A comma-delimited list of one or more complex codes (e.g., “C01,C02,C24,C26”)

       No spaces may exist between each comma and code in the list.

     The default setting for your environment is “False”. A setting of “True” causes the legacy publishing engine version to be used for all document output. A setting that includes one or more complex codes causes the legacy publishing engine version to be used only for documents associated with the specified complex(es).

  4. Click the “Save” button at lower-right of the page.

• Enabling use of the prior DivXML HTML engine version for one or more complexes

  The logic used for processing ArcReporting document output of types PDF, Blackline PDF and EDGAR (HTML) is updated occasionally, according to client needs and/or regulatory requirements. Typically, such updates do not impact existing document implementations, however there may be a need in some cases to temporarily continue processing one or more documents using an older version of the DivXML HTML engine.

  The “UsePriorDivXmlHtmlRelease” system setting allows you to either use the latest DivXML HTML engine version for all document output of the types noted above, use the prior DivXML HTML engine version for all document output of the above types, or use the prior version for only those documents of the above types associated with one or more specified complexes.

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To specify DivXML HTML engine version settings for your documents of types PDF, Blackline PDF and EDGAR (HTML), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the “UsePriorDivXmlHtmlRelease” item in the “System Settings” grid to one of the following values.

     • “False”
     • “True”

     • A comma-delimited list of one or more complex codes (e.g., “C01,C02,C24,C26”)

       No spaces may exist between each comma and code in the list.

     The default setting for your environment is “False”. A setting of “True” causes the prior DivXML HTML engine version to be used for all document output of types PDF, Blackline PDF and EDGAR (HTML). A setting that includes one or more complex codes causes the prior DivXML HTML engine version to be used only for documents of the above types associated with the specified complex(es).

  4. Click the “Save” button at lower-right of the page.

• Enabling the output and evaluation of data points in portfolio content

  Arc Suite allows you to insert variable data points of various types (e.g., “Account Period”, “Calculation Sheet”, “Class Data Point”, “Conditional Value”, “Exchange Rate”, “Fund Data Point”, “Page/Note Reference”, “Supplemental Data”, etc.) into project content, which evaluate to appropriate values in project output.

  Arc Suite support staff use the “PortfolioOutputDataPointTagging” system setting to turn data point output functionality on or off for troubleshooting purposes, as necessary; it is typically not a setting adjusted by application users.

  To enable the output and evaluation of data points in portfolio content, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “PortfolioOutputDataPointTagging” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables data point output functionality for portfolio content.

  4. Click the “Save” button at lower-right of the page.

• Enabling the output and evaluation of data points in financial content

  Arc Suite allows you to insert variable data points of various types (e.g., “Account Period”, “Calculation Sheet”, “Class Data Point”, “Conditional Value”, “Exchange Rate”, “Fund Data Point”, “Page/Note Reference”, “Supplemental Data”, etc.) into project content, which evaluate to appropriate values in project output.

  Arc Suite support staff use the “FinancialOutputDataPointTagging” system setting to turn data point output functionality on or off for troubleshooting purposes, as necessary; it is typically not a setting adjusted by application users.

  To enable the output and evaluation of data points in financial content, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “field” item in the “FinancialOutputDataPointTagging” grid to “System Settings”.

     The default setting for your environment is “True”. A setting of “False” disables data point output functionality for financial content.

  4. Click the “Save” button at lower-right of the page.

• Enabling the display and use of “Layout Code” fields for financial statement template output settings

  Arc Suite allows you to specify one or more “Layout Code” values for data in financial statement template output settings.

  To enable the display of “Layout Code” fields on the “Financial Statement Template Output Settings” page, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “DisplayFSTOSLayoutCode” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”.

  4. Click the “Save” button at lower-right of the page.

• Enabling the display of “Calculate single fund holdings” button and status label for portfolio fund holdings

  To enable the display of the “Calculate single fund holdings” button and associated status label on the “Fund Holdings” page, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “DisplayFundHoldingsCalculateButton” item in the “System Settings” grid to “True”.

     The default setting for your environment is “False”.

  4. Click the “Save” button at lower-right of the page.

• Enabling the display of T-journal account view on the “Financial Workbook” page

  To specify that the “Journal Entries” dialogue (invoked via the “Financial Workbook” page) display a T-journal account view (including beginning and ending balances), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableJournalEntryTLedgerView” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables T-journal account view functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling financial statement output optimization

  For troubleshooting purposes, Arc Suite internal staff use the “FinancialOutputEngineOptimization” system setting to evaluate the output of financial statement data, as necessary.

  This setting should not be adjusted without first consulting with your Donnelley Financial Solutions liaison.

  To specify that financial statement output optimization functionality be enabled, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “FinancialOutputEngineOptimization” item in the “System Settings” grid to “True”.

     The default setting for your environment is “True”. A setting of “False” disables financial statement output functionality.

  4. Click the “Save” button at lower-right of the page.

• Enabling display of root mapping in Financial Statement Mapping Audit Report

  You can opt to include an “Underlying Source” row for certain types of mapped items when outputting the Financial Statement Mapping Audit Report, providing an additional level of information.

  To enable this functionality, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableUnderlyingSourceForFSTMappingAuditReport” item in the “System Settings” grid to “True”.

     • The underlying source is at a fund level; it will not show a breakdown of class/currency values.

       • The underlying source is suppressed if it is a zero value.
       • Trial balance accounts are suppressed if beginning balance, cumulative debts, cumulative credits and ending balance are all zero.

       • Certain item types will not display an underlying source.

         • Holdings Category
         • Holdings Detail
         • Holdings Subtotal
         • Holdings Maturity Data Range
         • Class Balance Data Point
         • Supplemental Data Point
         • Items returned as part of a conditional calculation sheet
         • Items returned as part of a calculation sheet sub-total
     • The default setting for your environment is “False”. A setting of “False” prevents the display of “Underlying Source” rows in report output.

  4. Click the “Save” button at lower-right of the page.

• Specifying project-, chapter- and section-level output revision purge interval: include most recent revision

  Arc Suite project-, chapter- and section-level output that has been submitted to the document processing service can be viewed via the revisions grid on the “Output Management” tab of the “Project” page. Arc Suite allows you to purge old or irrelevant output revisions at a specified interval, and based on certain criteria.

  To specify the interval at which the system will purge all project, chapter and section output revisions from the database, based on publish date (including the most recent revision per output type), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the interval (in days) for the “urgeAllRevisionsInDays” item in the “System Settings” grid.

     In this example, the purge would be carried out every 1095 days.

     • The default setting for your environment is “1095” (3 years).

     • The user interface does not support validation for minimum/maximum/valid values for this setting. Therefore, the following logic is employed if you enter an invalid value or a value outside the accepted range:

       • If you enter a value less than “60” (60 days), the system will carry out the purge every 60 days.
       • If you enter a value greater than “2557” (7 years), the system will carry out the purge every 2557 days.
       • If you enter an invalid (e.g., non-numeric) value, the system will carry out the purge every 2557 days.
     • Any output revision of type “N-MFP (XML)” or “N-MFP Review Report” that meets the purge setting criteria, but that is associated with a pending or successful SEC and/or ICI filing, will not be purged.

  4. Click the “Save” button at lower-right of the page.

• Specifying project-, chapter- and section-level output revision purge interval: exclude most recent revision

  Arc Suite project-, chapter- and section-level output that has been submitted to the document processing service can be viewed via the revisions grid on the “Output Management” tab of the “Project” page. Arc Suite allows you to purge old or irrelevant output revisions at a specified interval, and based on certain criteria.

  To specify the interval at which the system will purge all project, chapter and section output revisions from the database, based on publish date (except the most recent revision per output type), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the interval (in days) for the “PurgeAllRevisionsExceptMostRecentInDays” item in the “System Settings” grid.

     In this example, the purge would be carried out every 365 days.

     • The default setting for your environment is “365” (1 year).

     • The user interface does not support validation for minimum/maximum/valid values for this setting. Therefore, the following logic is employed if you enter an invalid value or a value outside the accepted range:

       • If you enter a value less than “60” (60 days), the system will carry out the purge every 60 days.
       • If you enter a value greater than “2557” (7 years), the system will carry out the purge every 2557 days.
       • If you enter an invalid (e.g., non-numeric) value, the system will carry out the purge every 2557 days.
     • Any output revision of type “N-MFP (XML)” or “N-MFP Review Report” that meets the purge setting criteria, but that is associated with a pending or successful SEC and/or ICI filing, will not be purged.

  4. Click the “Save” button at lower-right of the page.

• Specifying project-, chapter- and section-level output revision purge interval: empty comments, exclude most recent revision

  Arc Suite project-, chapter- and section-level output that has been submitted to the document processing service can be viewed via the revisions grid on the “Output Management” tab of the “Project” page. Arc Suite allows you to purge old or irrelevant output revisions at a specified interval, and based on certain criteria.

  To specify the interval at which the system will purge all project, chapter and section output revisions that have an empty “Comments” field from the database (except the most recent revision per output type), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the interval (in days) for the “PurgeEmptyCommentRevisionsExceptMostRecentInDays” item in the “System Settings” grid.

     In this example, the purge would be carried out every 182 days.

     • The default setting for your environment is “182” (6 months).

     • The user interface does not support validation for minimum/maximum/valid values for this setting. Therefore, the following logic is employed if you enter an invalid value or a value outside the accepted range:

       • If you enter a value less than “60” (60 days), the system will carry out the purge every 60 days.
       • If you enter a value greater than “2557” (7 years), the system will carry out the purge every 2557 days.
       • If you enter an invalid (e.g., non-numeric) value, the system will carry out the purge every 2557 days.
     • Any output revision of type “N-MFP (XML)” or “N-MFP Review Report” that meets the purge setting criteria, but that is associated with a pending or successful SEC and/or ICI filing, will not be purged.

  4. Click the “Save” button at lower-right of the page.

• Specifying chapter- and section-level output revision purge interval: include most recent revision

  Arc Suite chapter- and section-level output that has been submitted to the document processing service can be viewed via the revisions grid on the “Output Management” tab of the “Project” page. Arc Suite allows you to purge old or irrelevant output revisions at a specified interval, and based on certain criteria.

  To specify the interval at which the system will purge all chapter and section output revisions from the database, based on publish date (including the most recent revision per output type), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the interval (in days) for the “PurgeAllChapterRevisionsInDays” item in the “System Settings” grid.

     In this example, the purge would be carried out every 365 days.

     • The default setting for your environment is “365” (1 year).

     • The user interface does not support validation for minimum/maximum/valid values for this setting. Therefore, the following logic is employed if you enter an invalid value or a value outside the accepted range:

       • If you enter a value less than “60” (60 days), the system will carry out the purge every 60 days.
       • If you enter a value greater than “2557” (7 years), the system will carry out the purge every 2557 days.
       • If you enter an invalid (e.g., non-numeric) value, the system will carry out the purge every 2557 days.

  4. Click the “Save” button at lower-right of the page.

• Specifying chapter- and section-level output revision purge interval: exclude most recent revision

  Arc Suite chapter- and section-level output that has been submitted to the document processing service can be viewed via the revisions grid on the “Output Management” tab of the “Project” page. Arc Suite allows you to purge old or irrelevant output revisions at a specified interval, and based on certain criteria.

  To specify the interval at which the system will purge all chapter and section output revisions from the database, based on publish date (except the most recent revision per output type), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the interval (in days) for the “PurgeAllChapterRevisionsExceptMostRecentInDays” item in the “System Settings” grid.

     In this example, the purge would be carried out every 90 days.

     • The default setting for your environment is “90” (3 months).

     • The user interface does not support validation for minimum/maximum/valid values for this setting. Therefore, the following logic is employed if you enter an invalid value or a value outside the accepted range:

       • If you enter a value less than “60” (60 days), the system will carry out the purge every 60 days.
       • If you enter a value greater than “2557” (7 years), the system will carry out the purge every 2557 days.
       • If you enter an invalid (e.g., non-numeric) value, the system will carry out the purge every 2557 days.

  4. Click the “Save” button at lower-right of the page.

• Specifying chapter- and section-level output revision purge interval: empty comments, exclude most recent revision

  Arc Suite chapter- and section-level output that has been submitted to the document processing service can be viewed via the revisions grid on the “Output Management” tab of the “Project” page. Arc Suite allows you to purge old or irrelevant output revisions at a specified interval, and based on certain criteria.

  To specify the interval at which the system will purge all chapter and section output revisions that have an empty “Comments” field from the database (except the most recent revision per output type), follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the interval (in days) for the “PurgeEmptyCommentChapterRevisionsExceptMostRecentInDays” item in the “System Settings” grid.

     In this example, the purge would be carried out every 90 days.

     • The default setting for your environment is “90” (3 months).

     • The user interface does not support validation for minimum/maximum/valid values for this setting. Therefore, the following logic is employed if you enter an invalid value or a value outside the accepted range:

       • If you enter a value less than “60” (60 days), the system will carry out the purge every 60 days.
       • If you enter a value greater than “2557” (7 years), the system will carry out the purge every 2557 days.
       • If you enter an invalid (e.g., non-numeric) value, the system will carry out the purge every 2557 days.

  4. Click the “Save” button at lower-right of the page.

• Enabling display of data diagnostic information

  In order to facilitate the management of information in Arc Suite, data must be retrieved, processed and displayed in the user interface. When updates to that data are made, the system must again process it and save the changes. In some cases, the data set being managed can be very large.

  You can enable the display of diagnostic information for data retrieval and processing, etc. (on pages where this functionality is implemented) by following the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the value of the “EnableDiagnostics” item in the “System Settings” grid to “True”.

     • The default setting for your environment is “False”. A setting of “False” disables the display of diagnostic information in all interfaces that support it.

     • The application interfaces that currently support display of diagnostic information are as follows:

       • Fund Holdings page, “Holdings” tab (ArcReporting only)

  4. Click the “Save” button at lower-right of the page.

• Specifying portfolio calculations historical data retention period

  Arc Suite stores portfolio statement calculation information in the database, for use in displaying values in the document preview page and in document output. Based on data-retention agreements with each client, DFIN staff can specify that this calculation information be purged after a certain period of time.

  This setting is intended to be used by DFIN staff only, or in consultation with them by client administrators.

  To specify the length of time the system will retain portfolio statement calculation records before purging them from the database, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Enter the period of time (in months) for the “PortfolioCalculationRetentionPeriodInMonths” item in the “System Settings” grid.

     In this example, any portfolio calculations would be stored in the database for 36 months, and would be purged after that time.

     • The default setting for your environment is “0”, however internal processing logic dictates that 36 months (3 years) will always be the minimum data retention period.

     • The user interface does not support validation for minimum/maximum/valid values for this setting. Therefore, the following logic is employed if you enter an invalid value or a value outside the accepted range:

       • If you enter a value less than “36” (3 years), the system will retain data for 36 months.
       • If you enter a value greater than “240” (20 years), the system will retain data for 240 months.
       • If you enter an invalid (e.g., non-numeric) value, the system will retain data for 240 months.

  4. Click the “Save” button at lower-right of the page.

• Enabling use of the app-tier footing engine for trial balance values

  The logic used for footing trail balance values is implemented in a stored procedure (data-tier) and also in the PortfolioManagement Service (app-tier).

  This setting is intended to be used by DFIN staff only, or in consultation with them by client administrators.

  To specify footing engine settings for your trial balance values, follow the steps outlined below:

  1. Expand the Environment Administration “Settings” menu.

     1. Click the “Home” button at the top of the application window to return to the landing page.

     2. Select “Environment Administration” from the administration area.

        

     3. Click the “Settings” menu to view available items.

  2. Click the “System” item.

     The “System” page displays.

     

  3. Set the “EnableAppTierFootingEngine” item in the “System Settings” grid to one of the following values.

     • “False”
     • “True”

     The default setting for your environment is “False”. A setting of “True” causes the app-tier footing engine to be used for all trial balance footing logic.

  4. Click the “Save” button at lower-right of the page.