Save Form Input File

This file, referenced in requirement.csv to support the saving of forms, includes POV, and cell input values in the following format. If business rules are associated with the form, this file also includes the runtime prompts for those business rules:

A sample input file:

pov=[DIM 1:MEMBER1],[DIM 2:MEMBER2],[DIM 3:MEMBER3],…;cells=[CELL COLUMN HEADER 1 -> CELL COLUMN HEADER 2 -> CELL COLUMN HEADER 3 ->.. | CELL ROW HEADER 1-> CELL ROW HEADER 2-> CELL ROW HEADER 3->..| CELL 1 DATA], [CELL COLUMN HEADER 11 -> CELL COLUMN HEADER 22 -> CELL COLUMN HEADER 33 ->.. | CELL ROW HEADER 11-> CELL ROW HEADER 22-> CELL ROW HEADER 33->..| CELL 2 DATA];rtp=[BUSINESS RULE NAME1[RTP1:VALUE1][RTP2:VALUE2]],[BUSINESS RULE2[RTP3:VALUE3]]..

In this example:

• DIM indicates the name of a dimension and MEMBER indicates a dimension member value.
• CELL COLUMN HEADER identifies the name of the column header and CELL ROW HEADER identifies the name of a row header.
• BUSINESS RULE NAME indicates the name of the business rule, RTP indicates the runtime prompt name, and VALUE indicates its value. RTP is not required if no business rule is associated with the form or if you want to use the default runtime prompt value present in the form.

For example:

pov=[Version View:Working],[Sales Entity:International Sales];cells=[FY16->x---------x->Pct|P293:Maintenance->4120: Support|1];rtp=[Services Revenue - Forecast[Department:000][Scenario:Plan]],[Allocate Plan Targets[TargetVersion:Baseline]]

Note:

You must also create UserVarMemberMapping.csv if the forms you specify in requirement.csv require user variables to be set. See Creating the UserVarMemberMapping.csv File.

Smart Pushes, if any, associated with the form run automatically.