Release Notes 5.3.0/5.3.1

Valsight Version 5.3.0 adds two changes in the access rights of Valsight and a new formula.

Access Rights

With the 5.3.0 release, Valsight enables Basic Users to promote/demote Workflow submissions and Simulation Users to update Data Sources.

Basic User

Allowing Basic Users to promote and demote Workflow submissions supports the use case that another user (e.g. Simulation User) prepares the Workflow and its scenarios, but another user should also be able to promote or demote Workflow steps.

With the 5.3.0 release, Basic Users can now also be seen as reviewers of a Workflow step and being able to promote and demote it.

To be able to promote and demote Workflow submissions, Basic Users are now also enabled to be assigned permission rights for the states a Workflow step moves through.

This is a necessary requirement for all users to be able to interact with a Workflow submission.

Simulator

Enabling Simulation Users to create/update Data Sources simplifies the process of integrating new data into a Workspace while working and simulating in it.

While being able to create, upload and delete Data Sources, Simulation Users can also rename Data Sources and update/rename Dimensions if the file contains them.

To do so, the Simulation User needs to have Project Admin rights.

So far, this could only be done by Model Users.

Changing the Access Rights of a User can be done in the Valsight Settings under 'Users', selecting the user and then 'Edit Permissions'.

Formula

REBOOK

The REBOOK formula enables users to "book" level value measures between values within the same level of a dimension.

Description	The REBOOK function can be used in all situations where value measures need to be “booked” to a different value in the same level.
Signature	REBOOK('Node', "Level", "OldValue", "NewValue" <, "FilterOperation">)
Parameters	Node: Input node Level: The level in the input node that shall be re-booked. OldValue: The existing value which value measure shall be rebooked (moved). This can either be a single value or a list of values. NewValue: The target value of the rebook. This should be a single string value. FilterOperation: How are the values checked against the filter. "EQ"(equality) - (Default) "NEQ"(Not equals), "GT"(greater than) "GTE"(greater than or equals) "LT"(less than) "LTE"(less than or equals).
Limitations	OldValue and NewValue must be level values of the input Level. If the node contains linked levels, it is not possible to Rebook values of the dimension that is linked too. Rebook the values that is linked from to get all the valid values instead. Important: This function always makes the links from the levels of the specified dimension be the same as in the dimension management. Do not use this function if you want the Node to have different level links as the dimensions.

Example

Revenue:

Year	Segment	Revenue
2020	MINI	100
2020	COMPACT	50
2020	LARGE	10

REBOOK('Revenue', Segment”, “MINI”, “LARGE”) =

Year	Segment	Revenue
2020	MINI	0
2020	COMPACT	50
2020	LARGE	110

With this formula, the value measure of 'MINI' is rebooked to 'LARGE'.

As LARGE already had a revenue of '10', the rebooked value of '100' is added (=110).

Calculation:

Year	Segment	Revenue
2020	MINI	100 (-100)
2020	COMPACT	50
2020	LARGE	10 (+100)

PV

AVAILABLE SINCE 5.3.1

Description	Calculates the present value of a certain sum in the future. It is based on an interest rate, a number of recurring payments in the future, the amount of payment per period, the future value and either ordinary annuity or annuity due (type) indicating whether payments are due at the beginning or the end of period.
Signature	PV('Rate', 'Nper', 'Pmt' [, 'Fv' , "Type"])
Parameters	Rate -> The interest rate Nper -> Number of periods: the number of payments to be made (Needs to be entered as a negative number e.g. -500) Pmt -> Payment per period: the amount per period to be paid Fv -> [Optional] Future value: the future value remaining after the final payment has been made. If not entered, 'fv' is set to 0. Type -> [Optional] type (1=pmt at beginning of period (Annuity Due), 0=pmt at end of period (Ordinary Annuity)). By default 'type' is set to 0.
Notes	Argument 'Pmt' is the guiding input node. Each input node can be single number Providing all inputs with the same dimensionality results in a noticeable performance improvement
Limitations	All other inputs must not contain Levels that are not in the guiding input node 'Pmt' . All Level Values that are in the guiding input node 'pmt', must be in all the other input nodes.

Positive Costs

In case the costs are entered as a positive number within your model, this function needs to be multiplied by (-1).

FV

AVAILABLE SINCE 5.3.1

Description	Calculates the value of a recurring annuity investment at a set point in the future. It is based on an interest rate, a number of recurring payments, the amount of individual payments, the present value and either ordinary annuity or annuity due (type) indicating whether payments are due at the beginning or the end of period.
Signature	FV('Rate', 'Nper', 'Pmt' [, 'Pv' , ["Type"]])
Parameters	Rate -> The interest rate Nper -> Number of periods: the number of payments to be made (Needs to be entered as a negative number e.g. -500) Pmt -> Payment per period: the amount per period to be paid Pv -> [Optional] Present value: the current value of the annuity. If not entered, 'Pv' is set to 0. Type -> [Optional] type (1=pmt at beginning of period (Annuity Due), 0=pmt at end of period (Ordinary Annuity)). By default 'Type' is set to 0.
Notes	Argument 'Pmt' is the guiding input node. Each input node can be single number Providing all inputs with the same dimensionality results in a noticeable performance improvement
Limitations	All other inputs must not contain Levels that are not in the guiding input node 'Pmt'. All Level Values that are in the guiding input node 'Pmt', must be in all the other input nodes.

Positive Costs

In case the costs are entered as a positive number within your model, this function needs to be multiplied by (-1).

PMT

AVAILABLE SINCE 5.3.1

Description	Calculates the periodic payment required for a recurring investment based on a constant interest rate, a number of recurring payments and a present value and either ordinary annuity or annuity due (type) indicating whether payments are due at the beginning or the end of period.
Signature	PMT('Rate', 'Nper', 'Pv' [, 'Fv' , ["Type"]])
Parameters	Rate -> The interest rate Nper -> Number of periods: the number of payments to be made Pv -> Present value: the current value of the annuity Fv -> [Optional] - Future value: the future value remaining after the final payment has been made. If not entered, 'Fv' is set to 0. Type -> [Optional] type (1=pmt at beginning of period (Annuity Due), 0=pmt at end of period (Ordinary Annuity)). By default 'Type' is set to 0.
Notes	Argument 'Pv' is the guiding input node. Each input node can be single number Providing all inputs with the same dimensionality results in a noticeable performance improvement
Limitations	All other inputs must not contain Levels that are not in the guiding input node 'Pv'. All Level Values that are in the guiding input node 'Pv' , must be in all the other input nodes.

NPER

AVAILABLE SINCE 5.3.1

Description	Calculates the number of periods necessary for a recurring investment based on an interest rate, the amount of payment per period, a present value, a future value and either ordinary annuity or annuity due (type) indicating whether payments are due at the beginning or the end of period.
Signature	NPER('Rate', 'Pmt', 'Pv' [, 'Fv' [, "Type"]])
Parameters	Rate -> The interest rate Pmt -> Payment (in each period): the amount of each payment made (Needs to be entered as a negative number e.g. -100) Pv -> Present value: the current value of the annuity Fv -> [Optional] - Future value: the future value remaining after the final payment has been made. If not entered, 'Fv' is set to 0. Type -> [Optional] type (1=pmt at beginning of period (Annuity Due), 0=pmt at end of period (Ordinary Annuity)). By default 'Type' is set to 0
Notes	Argument 'Pv' is the guiding input node. Each input node can be single number Providing all inputs with the same dimensionality results in a noticeable performance improvement
Limitations	All other inputs must not contain Levels that are not in the guiding input node 'Pv' . All Level Values that are in the guiding input node 'Pv' , must be in all the other input nodes.

Positive Costs

In case the costs are entered as a positive number within your model, this function needs to be multiplied by (-1).

Further Notifications

Global Admins are now able to cancel all queued pending jobs that have not been executed so far (Valsight Settings > Async Queries > Cancel Pending Jobs)
When duplicating Models, users are now able to assign new names and descriptions to the duplicates
The Workspace validation and its settings can now also be triggered in the Scenario Manager
The ‘Save’ and the ‘Discard’ function for Workspaces will be deprecated with the 5.4.0 release
- Workspaces are saved automatically, so there is no need to worry about losing changes.
- In case of questions, please do not hesitate to contact customer support at +49 30 46799042 or support@valsight.com.