Onestream Xf Scenario Properties Workflow We will go more in depth on how each scenario property works. there is a true false option for this property. if the scenario is not loaded into yet, switch to false. for actual scenarios, all time periods is typically chosen. for budget or forecast scenarios, yearly is typically chosen. Configure scenarios: users can define and customize scenarios by specifying future feature values or predicting the occurrence of certain events. run predictions: after scenarios are configured, predictions can be run for each scenario.
Onestream Xf Scenario Properties Workflow When adding creating a new forecast scenario follow the naming convention: txp fcst xxx. recommend having at least one forecast scenario under the txp fcst currentyear parent. many of the scenario properties for a forecast scenario differ from the txp actual scenario. Names of scenario types are irrelevant since none of the default behaviors of the onestream platform are defined by scenario types. this enables you to choose any scenario type, assign it to any scenario, and choose a relevant name applicable to the business problem you're solving. There are 24 pre defined scenario types which include: actual, budget, forecast, etc. these are properties of each scenario member. it also controls how they can be categorized. you are able to have as many scenarios as you want of each scenario type on onestream xf. This function retrieves any dimension member property from the member properties tab in the dimension library. note there are no spaces used when defining property name.
Onestream Xf Scenario Dimensions There are 24 pre defined scenario types which include: actual, budget, forecast, etc. these are properties of each scenario member. it also controls how they can be categorized. you are able to have as many scenarios as you want of each scenario type on onestream xf. This function retrieves any dimension member property from the member properties tab in the dimension library. note there are no spaces used when defining property name. To make an exception for a scenario, you must specify it in the business rule or formula. usually, onestream xf will have the input frequency as monthly (this is the most common setting). however, apps that use weekly scenarios must be changed from monthly to weekly. This property only works with a workflow name of workspace or any selected containing workspace (for example, workspace, certify). use this property to define any dashboard from the application dashboards page when an appropriate workflow name is chosen. Use workflow settings to manage which periods users can view and enter data. for alternate versions or slices, leverage hybrid scenarios to optimize storage and performance. I was just testing around to try and bind the month to a scenario. i don't have an answer for the property for the no input period, but an alternative which i've just tested is using the text1 field.
Onestream Xf Scenario Dimensions To make an exception for a scenario, you must specify it in the business rule or formula. usually, onestream xf will have the input frequency as monthly (this is the most common setting). however, apps that use weekly scenarios must be changed from monthly to weekly. This property only works with a workflow name of workspace or any selected containing workspace (for example, workspace, certify). use this property to define any dashboard from the application dashboards page when an appropriate workflow name is chosen. Use workflow settings to manage which periods users can view and enter data. for alternate versions or slices, leverage hybrid scenarios to optimize storage and performance. I was just testing around to try and bind the month to a scenario. i don't have an answer for the property for the no input period, but an alternative which i've just tested is using the text1 field.
Working With Onestream Xf Workflow Engine Blogs Perficient Use workflow settings to manage which periods users can view and enter data. for alternate versions or slices, leverage hybrid scenarios to optimize storage and performance. I was just testing around to try and bind the month to a scenario. i don't have an answer for the property for the no input period, but an alternative which i've just tested is using the text1 field.
Working With Onestream Xf Workflow Engine Blogs Perficient
Comments are closed.