Rapid application development tutorial 2 Contents

Financial transactions
accumulation register.
Questions, "What is a register? What is its purpose?" immediately arise. 
Below you will find a simple explanation. 
According to project requirements, the application should not only be 
capable of storing a list of friends and tracking events. It also should be 
capable of keeping records of financial transactions. At a minimum, it 
should keep records of cash flow and provide simple financial reports.
Registration of various events related to money income and outcome will 
be implemented by using configuration objects, named 
Documents
. Later, 
you will add a couple of documents to the applied solution.
Together with registering money incomes and outcomes, it is required 
to create some 
reports, 
demonstratively displaying 
what 
happens 
to finances. These reports can be created using data that is contained in 
user input documents. These documents reflect actual receipts and 
expenditures of money. However, imagine that in a month (or a year), for 
example, you decide to supplement your financial records with new 
documents or functionally expand existing ones.
Making configuration changes, as you have already seen, is a simple task. 
However, what will happen with reports in this case? It might turn out that 
financial reports that you created previously will not work properly, because 
they use only income and outgoing records from the old documents as data 
source. This means that you might have to rebuild all related to this 
data reports. Live applied solutions usually contain a large number of 
reports.
To avoid this work, and a large number of errors that may become a result 
of this alteration, 1C:Enterprise uses the following development 
methodology:
To store data regarding activity of accounting subjects, finances for 
example, configuration objects named