The manual details the T6 Planning Solution, a highly flexible and fully customizable application designed to adapt to a variety of models without the need for additional customizations. Dividing parameters into global and application-specific, the manual guides users on how to configure the application through the T6 Planning portal, highlighting the importance of synchronization and server restart after changes.
To be able to view and configure parameters within T6, the following requirements must be met:
Parameters are divided into two types:
To configure the parameters, access the main T6 menu, expand the Settings section, and select the Parameters option.
A side panel will open where we will configure the parameters, with the option to configure global parameters or parameters for a specific application. The panel opens by default in the Global tab; to switch to application parameters, simply click on the Application tab.
To change the value of a parameter, click on the desired parameter and change its value. As soon as you leave the field, the new parameter value will be saved in the database.
Below are the complete lists of global and application parameters.
The following listing displays the name, code, possible values, and description of each parameter:
Name | Code | Possible Values | Description |
---|---|---|---|
Journal Considers Account Type | JournalConsidersAccountType | Yes / No | Considers the account type within the consolidation adjustment. |
Name | Code | Possible Values | Description |
---|---|---|---|
Header Image | HeaderImage | Dropdown | Click the dropdown to display the images saved in the system and select an image for the header. |
Login Image | LoginImage | Dropdown | Click the dropdown to display the images saved in the system and select an image for the login page. |
User Control Header GesMed | UserControlHeaderGesMed | Text | Never change. Defines the user control used for the theme in question. |
User Control Header MicroStrategy | UserControlHeaderMicroStrategy | Text | Never change. Defines the user control used for the theme in question. |
User Control Header MicroStrategy 9 | UserControlHeaderMicroStrategy9 | Text | Never change. Defines the user control used for the theme in question. |
User Control Header QlikView | UserControlHeaderQlikView | Text | Never change. Defines the user control used for the QlikView theme. |
User Control Header SAP | UserControlHeaderSAP | Text | Never change. Defines the user control used for the theme in question. |
User Control Header Standard | UserControlHeaderStandard | Text | Never change. Defines the user control used for the theme in question. |
Name | Code | Possible Values | Description |
---|---|---|---|
Maximum rows to preview in data load | MaximumRowsInDataLoadPreview | Number | Defines the maximum number of records to be displayed in the data load source preview. |
Total records to be committed when running fact data load | TotalRowsToCommitInDataLoadFact | Text | Data type for selection-type attributes. For example, varchar (500). |
Name | Code | Possible Values | Description |
---|---|---|---|
Email Sender | emailSender | Text | Sender of emails sent by T6 Planning. For example, T6Planning@T6Planning.com. |
Email Subject | emailSubjectTag | Text | This text is concatenated at the beginning of the email subject, allg the creation of an identifier in all emails sent by T6 Planning. If left blank, it will not be used. |
Enable SSL SMTP | emailSmtpSSL | Yes / No | Indicates whether T6 Planning will use email sending via SMTP using the SSL security protocol. |
Proxy Domain | proxyDomain | Text | Domain used for authentication in the Proxy used for email sending. If left blank, it will not be used. |
Proxy Password | proxyPassword | Text | Password of the user used for authentication in the Proxy for sending emails. If left blank, it will not be used. |
Proxy Port | proxyPort | Number | Proxy server port number used for sending emails. If left blank, it will not be used. |
Proxy Server | proxyHost | Text | Proxy server address used for email sending. If left blank, none of the other Proxy-related parameters will be used, as the Proxy will be disabled. |
Proxy User | proxyUser | Text | User used for authentication in the Proxy for email sending. If left blank, it will not be used. |
SMTP Server | emailSmtp | Text | SMTP server used to send emails from T6 Planning. For example: smtp.T6Planning.com. |
SMTP Server Password | emailSmtpPassword | Text | User password for authentication with the SMTP server. If left blank, it will not be used. |
SMTP Server Port | emailSmtpPort | Number | SMTP server port number for sending emails. If left blank, it will not be used. |
SMTP Server User | emailSmtpUser | Text | User for authentication with the SMTP server. If left blank, it will not be used. |
Name | Code | Possible Values | Description |
---|---|---|---|
Calculus Float | CalculusFloat | Yes / No | Disabled by default; if enabled, calculations use floating point instead of decimal, increasing decimal precision. |
Execute Grouping by Scope | ExecuteGrouppingByScope | Yes / No | Defines whether the system should perform data grouping based on the specified scope, organizing information according to the defined scope or criteria. |
Formula Dependency Check Descendants | FormulaDependencyCheckDescendants | Yes / No | Defines whether the system should check formula dependency, specifically evaluating descendant formulas to ensure all dependency relationships are correctly handled. |
Maximum Formulas Iteration | MaximumFormulasIteration | Number | Maximum number of iterations used to resolve formulas with circular references. It is a maximum number, as T6 Planning will only continue iterating while the resulting values keep changing. The recommended setting for this parameter is always 1, as in most cases, a single iteration is sufficient to resolve the circular reference. |
Sort Formulas in Publication | SortFormulasInSync | Yes / No | Enables automatic sorting of formulas when the model is synchronized. It is highly recommended to always keep this feature enabled, as incorrectly ordered formulas can lead to incorrect results. |
Name | Code | Possible Values | Description |
---|---|---|---|
AAD Authentication ClientID | AADClientID | Text | Unique client identifier registered in Azure Active Directory (AAD), used for application authentication and authorization. |
AAD Authentication Domain | AADDomain | Text | Domain associated with Azure Active Directory (AAD), used for user authentication and authorization in the application. |
AAD Authentication Login URL | ServiceProviderUrlLogin | Text | Login URL for the authentication provider, used to redirect users to the Azure Active Directory (AAD) authentication page or another identity provider to complete the login process. |
AAD Authentication Logout URL | ServiceProviderUrlLogout | Text | Logout URL for the authentication provider, used to redirect users to the Azure Active Directory (AAD) logout page or another identity provider to end the authentication session. |
Authentication TenantID for AAD | AADTenantID | Text | Unique identifier of the Azure Active Directory (AAD) tenant, used for user authentication and authorization within the AAD directory. |
ActiveDirectory Server | ActiveDirectoryServer | Text | Address of the Microsoft Active Directory server. |
ActiveDirectory Server Password | ActiveDirectoryServerPassword | Text | Password for the Active Directory server, used for authentication and secure communication with the directory server for user and permission management operations. |
ActiveDirectory Server Username | ActiveDirectoryServerUsername | Text | Username used for authentication on the Active Directory server, enabling access and management of resources and users within the corporate network. |
ActiveDirectory Sysphera Group | ActiveDirectorySYSPHERAGroup | Text | Name of the group in Sysphera's Active Directory, used to manage permissions and user assignments within the corporate network. |
Authentication Authority for Auth0 | Auth0Authority | Text | URL of the entity responsible for authenticating users and issuing security tokens. |
Auth0 Authentication ClientID | Auth0ClientID | Text | Unique client identifier registered in Auth0, used for application authentication and authorization. |
Auth0 Authentication ClientSecret | Auth0ClientSecret | Text | Secret key associated with the Auth0 ClientID, used for secure authentication and application authorization. |
Customer Code | CustomerCode | Text | Code used to download license information (to obtain the customer code, contact the commercial department). |
Enable ActiveDirectory Login | EnableActiveDirectoryLogin | Yes / No | Activates integration with Microsoft Active Directory. |
Enable Single Sign-On (SSO) | EnableSingleSignOn | Yes / No | Defines whether Single Sign-On (SSO) will be enabled for the application. When activated, SSO allows users to log in once and access multiple applications without additional authentication. |
Integration | Integration | Yes / No | Defines whether integration with other systems or services will be enabled for the application. When activated, the application can communicate or share data with external systems. |
Power Planning Integration | PowerPlanningIntegration | Yes / No | -. (To make the parameter visible in the database, it needs to be enabled at least once.) |
Report - ADFS Url | PowerBIURLADFS | Text | URL of Active Directory Federation Services (ADFS), used for federated authentication with Power BI, allowing users to authenticate through an ADFS server before accessing Power BI resources. |
Report - Api Url | PowerBIURLApi | Text | URL of the Power BI API, used to make API calls and interact with reports, dashboards, and other Power BI platform resources. |
Report - Authority Url | PowerBIURLAuthority | Text | URL of Power BI's authorization endpoint, used to initiate the authentication process and obtain access tokens required to interact with the Power BI API. |
Report - Client Secret | PowerBIClientSecret | Text | Secret key associated with the ClientID in Power BI, used for secure authentication when accessing the Power BI API and generating reports or interacting with service resources. |
Report - ClientID | PowerBIClientID | Text | Unique identifier associated with the Client Secret in Power BI, used for authentication and authorization when accessing the Power BI API and interacting with reports or data. |
Report - Explorer Folder | PowerBIExplorerFolder | Dropdown | Defines the folder in Power BI Explorer where reports and dashboards are stored. Used to organize and easily locate resources within the platform. |
Report - GroupID | PowerBIGroupID | Text | Unique identifier of the group (workspace) in Power BI, used to locate and access specific reports and dashboards within a workspace in Power BI. |
Report - Integration | PowerBIIntegration | Yes / No | Defines whether integration with Power BI will be enabled in the application. When activated, it allows the application to interact directly with Power BI to generate and view reports. |
Report - Password | PowerBIPassword | Text | Defines the password used to access the Power BI reporting service, ensuring authentication and security when accessing the data. |
Report - Resources Url | PowerBIURLResources | Text | URL of Power BI resources, used to access data and reports stored on the Power BI platform via API calls or direct integration. |
Report - TenantID | PowerBITenantID | Text | Unique identifier of the tenant in Power BI, used for authentication and to identify the organization or instance of Power BI to which reports and resources belong. |
Report - Use RLS | PowerBIUseRLS | Yes / No | Defines whether Row-Level Security (RLS) will be enabled for Power BI reports. When activated, RLS allows controlling access to sensitive data by showing different information based on the authenticated user. |
Report - User Name | PowerBIUser | Text | Username used for authentication in Power BI, allowing access to reports and dashboards within the service. |
Service Provider Authentication ClientID | ServiceProviderAuthenticationClientId | Text | Unique client identifier registered in the authentication service provider, used for application authentication and authorization. |
Service Provider Authentication ClientSecret | ServiceProviderAuthenticationClientSecret | Text | Secret key associated with the service provider's ClientID, used for secure authentication and application authorization. |
Service Provider Authentication Domain | ServiceProviderAuthenticationDomain | Text | Domain of the authentication service provider, used for user authentication and authorization in the application. |
Service Provider Authentication Login URL | ServiceProviderAuthenticationUrlLogin | Text | https://name based on full name of AD or FS/ adfs/ls/?wa=wsignout1.0 . |
Service Provider Authentication Logout URL | ServiceProviderAuthenticationUrlLogout | Text | https://name based on full name of AD or FS/ adfs/ls/idpinitiatedSignon.aspx . |
Service Provider Authentication TenantID | ServiceProviderAuthenticationTenantID | Text | Unique identifier of the authentication service provider's tenant, used to authenticate and authorize users within the external service provider. |
Service Provider Authentication Type | ServiceProviderAuthenticationType | Text | Parameter that defines the type of the authentication service provider, specifying which authentication system will be used (SAML). |
Service Provider Certificate | ServiceProviderAuthenticationCertificate | Text | Enter the name of the certificate to encrypt data communication with T6 Planning. |
Sysphera Integration URL | SysUrl | Text | URL for integration with Sysphera, used to connect the application with Sysphera platform services, enabling data exchange and interaction with system resources. |
Sysphera URL | SyspheraWebFormUrl | Text | URL of the Sysphera web interface, used to access Sysphera's portal directly via a browser, facilitating interaction with the platform. |
Sysphera URL Service | SyspheraWebFormInternalUrl | Text | Internal URL for the Sysphera service, used to access specific functionalities and resources within the Sysphera platform, typically available for access within the corporate network or for internal integrations. |
SyspheraUX URL | PowerPlanningUrl | Text | URL of Sysphera UX, used to access the user interface of the Sysphera platform, providing an interface for process planning and management. |
Name | Code | Possible Values | Description |
---|---|---|---|
MicroStrategy AD Integration | MicroStrategyADIntegration | Text | Integration of Active Directory (AD) with MicroStrategy, used to synchronize AD users and groups with the MicroStrategy platform, allowing centralized access and permission management. |
MicroStrategy Command Manager Password | MicroStrategyCommandManagerPassword | Text | Password for the MicroStrategy Command Manager, used for authentication and access to the administration environment and execution of commands within MicroStrategy. |
MicroStrategy Command Manager Path | MicroStrategyCommandManagerPath | Text | Path to the MicroStrategy Command Manager, used to locate the directory where the Command Manager is installed, allowing the execution of commands and automation in the MicroStrategy platform. |
MicroStrategy Command Manager User | MicroStrategyCommandManagerUser | Text | Username used for authentication in the MicroStrategy Command Manager, allowing access and execution of administrative and operational commands within the MicroStrategy platform. |
MicroStrategy Default Theme | MicrostrategyIntegrationProcedures | Text | Defines the default theme for users created via integration with MicroStrategy. |
Integration with MicroStrategy | MicroStrategyIntegration | Yes / No | Enables integration with MicroStrategy. |
MicroStrategy Language | MicroStrategyLanguage | Text | Changes the MicroStrategy language (English, Spanish, and Portuguese). |
MicroStrategy Path | MicroStrategyPath | Yes / No | Name of the MicroStrategy project with which the application in question will integrate. Note that more than one T6 Planning application cannot point to the same MicroStrategy project. |
MicroStrategy Port | MicroStrategyport | Number | Port number used for communication with MicroStrategy, specifying the port through which the application connects to the MicroStrategy server to access the platform’s resources and functionalities. |
MicroStrategy Procedures Integration | MicrostrategyIntegrationProcedures | Yes / No | Enables integration via Procedures/Scripts with MicroStrategy. If this parameter is enabled ('Y'), there is no need to change the "Integration" parameter. |
MicroStrategy Project | MicroStrategyProject | Text | Name of the MicroStrategy project with which the application in question will integrate. Note that more than one T6 Planning application cannot point to the same MicroStrategy project. |
MicroStrategy Project Source | MicroStrategyProjectSource | Text | Source of the MicroStrategy project, used to specify the location or repository where the MicroStrategy project is stored, facilitating access and integration with data and reports. |
MicroStrategy Scenario Attribute | MicroStrategyScenarioAttribute | Text | Name of the column in the scenario dimension that contains the name of the related metric. For example: metric_name . |
MicroStrategy Script and Log Path | MicroStrategyScriptAndLogPath | Text | Path to the MicroStrategy script and logs, used to store or access execution scripts and activity logs of the MicroStrategy platform, facilitating monitoring and troubleshooting. |
MicroStrategy Server | MicroStrategyServer | Text | Address of the MicroStrategy server, used to identify the server where the MicroStrategy platform is hosted, allowing connection to access reports, dashboards, and other tool services. |
MicroStrategy URL | MicroStrategyUrl | Text | URL of the MicroStrategy platform, used to access the reporting environment, dashboards, and other functionalities of the MicroStrategy business intelligence tool. |
MicroStrategy Use Local Command Manager | MicroStrategyLocalCommandManager | Yes / No | Parameter that defines whether the MicroStrategy Command Manager will be executed locally instead of on the centralized server, allowing command execution directly on the user’s local machine. |
Name | Code | Possible Values | Description |
---|---|---|---|
Apply Filter in Member Calculated in Dimension Relationship | ApplyFilterMemberCalculatedInDimensionRelationship | Yes / No | Parameter that defines whether the filter will be applied to calculated members within dimension relationships, allowing filtering of these members when used in reports or calculations. |
Description for Data Type | AttributeDescriptionDataType | Text | Data type for description-type attributes. For example: varchar(max). |
Dimension Share | DimensionShare | Yes / No | Indicates whether the application allows dimension sharing. |
Maximum length characters for file name to upload | DataFileMaximumUploadFileName | Number | Defines the maximum allowed length for a file name when uploaded to the system, limiting the number of characters in the file name. |
Maximum file size for the note's document | NoteDocumentMaximumSize | Number | Lifetime in seconds of the report cache that uses SDP. |
Maximum size for the names of members | MaximumMemberName | Number | Parameter that defines the maximum allowed length for member names in the system, controlling the extension of names and ensuring they do not exceed the configured limit. |
MergeFact | MergeFact | Yes / No | Performs insert, update, or delete operations on a target table based on the results of the join with the source table. For example, you can synchronize two tables by inserting, updating, or deleting rows in a table based on differences found in the other table. Used only when the application does not use the writeback table. |
Not Applicable Dimension Code | NotApplicableDimensionCode | Number | Code for not applicable members, should never be changed unless recommended by T6 Planning. For example: -1. |
Not Applicable Dimension Description | NotApplicableDimensionDescription | Text | Description text for not applicable members. For example: Not Applicable. |
Selection Data Type | AttributeSelectionDataType | Text | Data type for selection-type attributes. For example: varchar(500). |
Update fact table using inser and delete in intermediate table | FactUpdateInsertAndDeleteInIntermediateTable | Yes / No | Defines whether Fact Table data will be updated using inserted and removed data from an intermediate table, facilitating change management during the data update process. |
Update fact table using intermediate table | FactUpdateIntermediateTable | Yes / No | Defines whether Fact Table data will be updated using an intermediate table, facilitating data manipulation before applying updates to the main Fact Table. |
Update fact table using update against delete | FactUpdateDeleteAsUpdate | Yes / No | Defines whether Fact Table data will be updated using the update operation instead of deletion, keeping existing records and modifying only the necessary data. |
Update Fact table with table in memory | FactUpdateTableInMemory | Yes / No | Defines whether the Fact Table data will be updated using data stored in memory, optimizing query performance and update operations. |
Name | Code | Possible Values | Description |
---|---|---|---|
Mobile Report URL | MobileReportURL | Text | URL used to access mobile reports, which are optimized versions of reports designed for viewing on mobile devices. |
Report Builder URL | ReportBuilderURL | Text | URL of the Report Builder. For example: http://server/reportbuilder. |
Reporting Services API URL | ReportingServicesAPIUrl | Text | URL of the Reporting Services API, used to establish communication and interaction with the resources and data available through the API. |
Reporting Services Cache | reportingServicesCache | True / False | Activates the cache for reports using the SDP. |
Reporting Services Cache Log | reportingServicesCacheLog | True / False | Activates the log for SDP reports for situations where debugging the application is desired. |
Reporting Services Data Set Name Template | ReportingServicesDataSetName | Text | Name template to be used for the data sets. Supports 2 parameters. {0} = Form Code and {1} = Form Name. Example: {0} - {1}. Default value: {0} - |
Reporting Services Data Set Path Template | ReportingServicesDataSetPath | Text | Directory where data sets will be published in Reporting Services. By default, the directory will be: /Datasets. |
Reporting Services Data Source Enabled | ReportingServicesDataSource | Yes / No | Enables the publication of data sources and data sets in Reporting Services. To enable: "Yes". |
Reporting Services Data Source Name Template | ReportingServicesDataSourceName | Text | Name template to be used for the data sources. Supports 1 parameter. {0} = Application Code. Example: App{0}. Default value: App. |
Reporting Services Data Source Path Template | ReportingServicesDataSourcePath | Text | Directory where data sources will be published in Reporting Services. By default, the directory will be: /DataSources. |
Reporting Services Explorer Folder | ReportingServicesExplorerFolder | Dropdown | Folder in the Explorer where reports and files related to Reporting Services are organized and stored, facilitating access and management of files within the system. |
Reporting Services Life Time | reportingServicesCacheLifeTime | Number | Lifetime in seconds for the cache of reports using the SDP. |
Reporting Services Password API Authentication | ReportingServicesPassword | Text | Password used for authentication in the Reporting Services API, necessary to ensure secure access to report services and related operations. |
Reporting Services URL | ReportServicesURLString | Text | URL of the Microsoft Report Server portal. For example: http://server/reportserver. |
Reporting Services User API Authentication | ReportingServicesUser | Text | Username used for authentication in the Reporting Services API, necessary to access and interact with the API resources securely. |
Save SDP Log in Event Viewer | SaveSDPLogInEventViewer | Yes / No | If the parameter value is Yes, errors and warnings related to the SDP will be saved in a specific entry in the Event Viewer of the server where T6 Planning is installed. |
Name | Code | Possible Values | Description |
---|---|---|---|
Build Number | BuildNumber | Number | Identifies the specific version of the application (This field should not be changed!). |
Cardinality Estimation Old | CardinalityEstimation70 | Yes / No | Defines whether the cardinality estimate should be calculated using the old methodology, used in earlier versions of the system or database, instead of the latest version. |
Check Valid Images | ImagesCheck | Yes / No | Parameter that defines whether the system should check if uploaded images are valid, i.e., whether they have a format and content compatible with the system's requirements. |
Compress XML Cube | PARM_CompressXMLCube | Text | Compresses the Cube information before persisting it in the repository. |
Compress XML Dimension | PARM_CompressXMLDimension | Text | Compresses the Dimension information before persisting it in the repository. |
Database Jobs VIEW | DatabaseJobsVIEW | Text | Defines the name of the VIEW that will be used to list the automatic routines (Jobs). This VIEW should contain the following fields: JobID, JobName, and JobDescription. |
Debug | Debug | Yes / No | Provides more details when an error occurs in the Application. |
Delayed Durability | DelayedDurability | Yes / No | Uses SQL Server 2014 or higher functionalities. |
Disable Compatibility Mode | DisableCompatibilityMode | Yes / No | Disables Compatibility Mode on the Server side, ensuring that T6 Planning always renders pages with the correct version of Internet Explorer, disregarding the browser's Compatibility Mode on the client side. |
Enable Logs | EnableLogs | Yes / No | Enable Logs. |
Enable Security Audit Trail | EnableSecurityAuditTrail | Yes / No | Enables audit and tracking of T6 Planning security. |
Enable Use of Temporary Table for Explorer Cache | EnableUseTemporaryTableForExplorerCache | Yes / No | Parameter that defines whether a temporary table will be used to store the Explorer cache, improving performance when accessing and retrieving frequently used data. |
Excel Temporary Folder | ExcelLoadPath | Text | Path to the temporary folder used for loading and exporting data from Excel files. This path must end with a backslash, e.g., C:\TMP. |
Export/Import Folder | ExportAndImportTMPPath | Text | Path to the temporary folder used for importing and exporting applications. This path must end with a backslash, e.g., C:\TMP. |
File Extensions | FileExtensions | Text | List of allowed or supported file extensions by the system for upload or processing, defining which types of files can be handled. |
Image Host Addresses | ImageHostsUrl | Text | Addresses of image hosts, i.e., URLs of the servers where the images used in the system are stored, allowing display and access to these images. We can add more than one domain as an image host, simply separate the URLs using ";" or "** **". (https://exemplourl.com.br; https://urlexemplo.com) |
Indez Rebuild | IndexRebuild | Number | If the logical fragmentation percentage in the fact/write-back tables is higher than this parameter's value, all indexes of the table are recreated. This happens automatically during manual formula execution or cube publishing. The value should be an integer between 0 and 100, representing the maximum fragmentation percentage allowed. For more information on "Reorganizing and Rebuilding indexes" see: http://technet.microsoft.com/en-us/library/ms189858(v=sql.105).aspx. |
Index Reorganize | IndexReorganize | Number | If the logical fragmentation percentage in the fact/write-back tables is higher than this parameter's value, all indexes of the table are reorganized. This happens automatically during manual formula execution or cube publishing. The value should be an integer between 0 and 100, representing the maximum fragmentation percentage allowed. For more information on "Reorganizing and Rebuilding indexes" see: http://technet.microsoft.com/en-us/library/ms189858(v=sql.105).aspx. |
Last Update BuildNumber | LastUpdateBuildNumber | Text | This parameter is required to inform the version number for T6 Planning compatibility. |
LGPD | LGPD | Yes / No | Indicates whether the system is configured to require user consent in compliance with the General Data Protection Law (LGPD), ensuring that personal data is collected and processed with the user's consent. |
Log Retention | LogRetention | Number | Defines the number of months that log records will be kept in the system before being deleted or archived, helping to manage storage and compliance with data retention policies. |
Login regular expression message | loginRegularExpression | Text | Regular expression to validate user passwords. For example, \w{8,}. |
Minify | Minify | Yes / No | If enabled, reduces the size of JavaScript files, decreasing data traffic. |
Multifactor Authentication | MultifactorAuthentication | Dropdown | Enables multifactor authentication, currently with the options none and email. |
Number of Login Attempts | NumberOfAttempts | Number | Defines the number of login attempts before blocking the user's access to the system. |
Operations Minimally Logged | OperationsMinimallyLogged | Yes / No | Defines whether operations in the system should be logged minimally, i.e., with limited information, to optimize performance and reduce the volume of logs generated. |
Password Expiration Time | PasswordExpirationTime | Number | Defines the time (in days) after which the user's password will expire and need to be updated to ensure system security. |
Password History Check | PasswordHistoryCheck | Number | Defines the number of previous passwords the system will check to ensure the user does not reuse old passwords when creating a new one. |
Period of inactivity after last login that the password will need to be reset (days) | PasswordExpirationLastLoginTime | Number | Defines the inactivity period (in days) after the last login, after which the user's password needs to be reset for security reasons. |
Regular expression to login | loginRegularExpressionMessage | Text | Message shown to the user if the regular expression validating the password is not followed. |
Serialize FastJson | SerializationFastJason | Yes / No | Defines whether object serialization should be performed using the JSON serialization library (FastJson), aiming to optimize data conversion into JSON format. |
Session Expiration Interval | SessionExpirationInterval | Number | Defines the time interval in minutes for which the user's session will remain active before expiring, requiring a re-login. |
Time Zone | Timezone | Dropdown | Click the dropdown to display timezones and select the desired one. |
Update Statistics Rows Change | UpdateStatisticsRowsChange | Number | Defines the minimum number of rows changed in the writeback during a transaction for the SQL Server query optimization statistics update to be triggered. |
VisualStudio Version | VisualStudioVersion | Number | Should be filled with the version of BIDS used for report creation. The default value is 2008. |
Name | Code | Possible Values | Description |
---|---|---|---|
Days Before Workflow Deadline | daysBeforeDeadlineWorkflow | Number | Number of days before a task or entity deadline expires to send an email notifying the responsible party. |
Emulate Workflow | WorkflowEmulation | Yes / No | If enabled, the workflow view will try to emulate the process to foresee future tasks. It will essentially simulate splits, conditionals, and responsible parties. |
Enable Workflow E-mails | WorkflowSendEmail | Yes / No | Activates the sending of emails with workflow statuses. |
Workflow Problem Days | WorkflowProblemDays | Number | When a task is about to expire and it is a concerning date, the task's planning symbol, for example, will turn red. This warning will start occurring in the number of days defined in this parameter before the task's due date. |
Workflow Warning Days | WorkflowWarningDays | Number | Similar to ProblemDays, but here the image turns yellow, meaning the due date is approaching but has not yet passed. |
To configure the application parameters, switch to the Application tab and click the dropdown to select the desired application.
When you click the dropdown, the list of available applications will be displayed for selection. Once an application is selected, the parameters will be displayed for configuration:
Name | Code | Possible Values | Description |
---|---|---|---|
E-mail sender | EmailSender | Text | Sender of the emails sent by T6 Planning. For example, T6Planning@T6Planning.com. |
SMTP Server | EmailSmtp | Text | SMTP server used to send emails from T6 Planning. For example: smtp.T6Planning.com. |
Name | Code | Possible Values | Description |
---|---|---|---|
Calculus Float | CalculusFloat | Yes / No | By default, this is disabled; when enabled, calculations use floating point instead of decimal, increasing decimal precision. |
Execute grouping by scope | ExecuteGrouppingByScope | Yes / No | Defines if the system should group data based on the specified scope, organizing information according to the defined scope context or criterion. |
Formula Dependency Check Descendants | FormulaDependencyCheckDescendants | Yes / No | Defines if the system should check formula dependencies, specifically evaluating descendant formulas to ensure all dependency relationships are correctly handled. |
Maximum Formula Iterations | MaximumFormulasIteration | Number | The maximum number of iterations used to resolve formulas with circular references. It is the maximum number, as T6 Planning will only continue iterating while resulting values are being changed by execution. Ideally, this parameter should always remain 1, as most circular references can be resolved with a single iteration. |
Sort Formulas in Publication | SortFormulasInSync | Yes / No | Enables auto sorting of formulas when the model is synchronized. It is highly recommended that this feature always remain enabled, as formulas in the wrong order can lead to incorrect results. |
Name | Code | Possible Values | Description |
---|---|---|---|
Active Directory Sysphera Group | ActiveDirectorySYSPHERAGroup | Number | Name of the group in Sysphera's Active Directory used to manage user permissions and assignments within the corporate network. |
Integration | Integration | Yes / No | Defines if integration with other systems or services will be enabled for the application. When enabled, the application can communicate or share data with external systems. |
Name | Code | Possible Values | Description |
---|---|---|---|
MicroStrategy Integration | MicroStrategyIntegration | Yes / No | Enables integration with MicroStrategy. |
MicroStrategy Language | MicroStrategyLanguage | Text | Changes the MicroStrategy language (English, Spanish, and Portuguese). |
MicroStrategy Path | MicroStrategyPath | Yes / No | Name of the MicroStrategy project with which the application will integrate. Note that there cannot be more than one T6 Planning application pointing to the same MicroStrategy project. |
MicroStrategy Procedures Integration | MicroStrategyIntegrationProcedures | Yes / No | Enables integration via Procedures/Scripts with MicroStrategy. If this parameter is active ('Yes'), there is no need to change the "Integration" parameter. |
MicroStrategy Project | MicroStrategyProject | Text | Name of the MicroStrategy project with which the application will integrate. Note that there cannot be more than one T6 Planning application pointing to the same MicroStrategy project. |
MicroStrategy Server | MicroStrategyServer | Text | Address of the MicroStrategy server, used to identify the server where the MicroStrategy platform is hosted, allowing the connection to access reports, dashboards, and other services of the tool. |
MicroStrategy URL | MicroStrategyUrl | Text | URL of the MicroStrategy platform, used to access the reporting, dashboards, and other business intelligence features of MicroStrategy. |
MicroStrategy Use Local Command Manager | MicroStrategyLocalCommandManager | Yes / No | Parameter that defines whether the MicroStrategy Command Manager will run locally, rather than on the centralized server, allowing commands to be executed directly on the user's local machine. |
Name | Code | Possible Values | Description |
---|---|---|---|
Apply Filter in Member Calculated in Dimension Relationship | ApplyFilterMemberCalculatedInDimensionRelationship | Yes / No | Parameter that defines whether the filter will be applied to calculated members within the dimension relationship, allowing these members to be filtered when used in reports or calculations. |
Dimension Share | DimensionShare | Yes / No | Indicates if the application allows dimension sharing. |
Maximum size for the names of members | MaximumMemberName | Number | Parameter that defines the maximum allowed length for member names in the system, controlling the extension of names and ensuring they do not exceed the configured limit. |
Merge Fact Data | MergeFact | Yes / No | Performs insertion, update, or deletion operations in a target table based on the results of a join with the source table. For example, you can synchronize two tables by inserting, updating, or deleting rows in one table based on differences found in the other table. Used only when the application does not use the writeback table. |
Update Fact table Using Insert and Delete in Intermediate Table | FactUpdateInsertAndDeleteInIntermediateTable | Yes / No | Defines if the Fact Table data will be updated using inserted and deleted data from an intermediate table, facilitating the management of changes during the data update process. |
Update fact table esing intermediate table | FactUpdateIntermediateTable | Yes / No | Defines if the Fact Table data will be updated using an intermediate table, facilitating the manipulation of data before applying updates to the main Fact Table. |
Update fact table using update against of delete | FactUpdateDeleteAsUpdate | Yes / No | Defines if the Fact Table data will be updated using the update operation instead of delete, maintaining existing records and modifying only the necessary data. |
Update Fact table with table In-Memory | FactUpdateTableInMemory | Yes / No | Defines if the Fact Table data will be updated using in-memory data, optimizing the performance of queries and update operations. |
Name | Code | Possible Values | Description |
---|---|---|---|
Reporting Services Data Set Name Template | ReportingServicesDataSetName | Text | Name template to be used for datasets. Supports 2 parameters. {0} = Form Code and {1} = Form Name. Ex.: {0} - {1}. Default value: {0} - . |
Reporting Services Data Set Path Template | ReportingServicesDataSetPath | Text | Directory where datasets will be published in Reporting Services. By default, the directory will be: /Datasets. |
Reporting Services Data Source Enabled | ReportingServicesDataSource | Yes / No | Enables publishing of data sources and datasets in Reporting Services. To enable: "Yes". |
Reporting Services Data Source Name Template | ReportingServicesDataSourceName | Text | Name template to be used for data sources. Supports 1 parameter. {0} = Application Code. Ex.: App{0}. Default value: App. |
Reporting Services Data Source Path Template | ReportingServicesDataSourcePath | Text | Directory where data sources will be published in Reporting Services. By default, the directory will be: /DataSources. |
Name | Code | Possible Values | Description |
---|---|---|---|
Cardinality Estimation Old | CardinalityEstimation70 | Yes / No | Defines if the cardinality estimation should be calculated using the old methodology, used in previous versions of the system or database, rather than the latest version. |
Compress XML Cube | CompressXMLCube | Yes / No | Compresses Cube information before persisting it in the repository. |
Compress XML Dimension | CompressXMLDimension | Yes / No | Compresses Dimension information before persisting it in the repository. |
Index Rebuild | IndexRebuild | Number | If the logical fragmentation percentage in fact/write-back tables is higher than this parameter's value, all indexes of the table will be rebuilt. This happens automatically during the manual execution of formulas or during cube publishing. The value should be an integer from 0 to 100, representing the desired maximum fragmentation percentage. For more information on "Reorganizing and Rebuilding indexes," see: http://technet.microsoft.com/en-us/library/ms189858(v=sql.105).aspx. |
Index Reorganize | IndexReorganize | Number | If the logical fragmentation percentage in fact/write-back tables is higher than this parameter's value, all indexes of the table will be reorganized. This happens automatically during the manual execution of formulas or during cube publishing. The value should be an integer from 0 to 100, representing the desired maximum fragmentation percentage. For more information on "Reorganizing and Rebuilding indexes," see: http://technet.microsoft.com/en-us/library/ms189858(v=sql.105).aspx. |
Operations Minimally Logged | OperationsMinimallyLogged | Yes / No | Defines if operations in the system should be logged minimally, i.e., with limited information, to optimize performance and reduce the volume of generated logs. |
Update Statistics Rows Change | UpdateStatisticsRowsChange | Number | Defines the minimum number of rows altered in the writeback during a transaction for the SQL Server query optimization statistics to be triggered. |
Name | Code | Possible Values | Description |
---|---|---|---|
Enable Workflow E-mails | WorkflowSendEmail | Yes / No | Enables sending emails with the workflow statuses. |
Workflow Problem Days | WorkflowProblemDays | Number | When a task is about to expire, and the date is already concerning, the planning task symbol, for example, will turn red. This warning will start to occur based on the number of days defined in this parameter before the task's due date. |
Workflow Warning Days | WorkflowWarningDays | Number | Similar to ProblemDays, but here the image turns yellow, meaning the due date is approaching but has not yet passed. |