Features and terminology

RequestManager features and terminology

Sector Profile	RequestManager includes profiles for different sectors, since companies in the same sector would generally collect similar types of information.  Choosing a Sector Profile provides the company with a set of Templates and Data Tags that are relevant for their sector. This a good first step when configuring the system for a new company.   If customizations or additions are made to templates or data tags, these changes can be saved as a custom profile.
Form Templates	Templates (which can also be referred to as ‘Form Templates’ if needed for clarification) are useful when a company needs to manually input the same type of information over and over again. There could be multiple Templates that are tagged with similar Data Tags.  For instance, a company may have different invoices for their various services or products.  So they may have separate Templates for each type of invoice.  But they are all tagged “Invoice”.
Form	The set of input fields that you enter data into in a data request. The difference between‘Form’ and‘Form Template’: The difference is subtle.  When you open a data request, and click on Form Template, it opens a prebuilt form that you can enter data into.  You may wish to add or remove fields for this particular record.  In that case, you’re editing the form, but you are not editing the Template.  When you save the record you created using that form, the Template will not be affected.  Also, sometimes, you may not use a Template at all.  You may enter data manually, which involves building the form as you go. To illustrate: In Excel, you start with a spreadsheet template.  But as soon as you start editing it or entering data, you’re really editing a spreadsheet, not a spreadsheet template. Likewise, in RequestManager, a Form Template is a starting point.  But once you start editing/adding data, you’re now working with a form.
Form Fields	The individual fields in any form.  For instance, a Template designed to collect contact information could include fields such as: address, email, home phone, mobile, Skype, Twitter, etc.   If using the ‘Manual Entry’, the form fields would be added one at a time.
Record	A Record is a set of data added to a Data Request either using a Template, or by adding data manually.  If you start with a Template, as soon as you enter some data into it, it gets saved as a Record.  Now the Template and the record are two separate entities – you can edit the Template, but it won’t affect the record. To illustrate: When you use Excel, you might start with a spreadsheet template.  But then you enter some information, and save it.  Now if Microsoft changes their template, it won’t affect your saved file.  That saved file is equivalent to a Record in RequestManager.
Data Tags	Data Tags are attached to records and files, and are used to indicate the types of information contained (i.e. “Contact”, “Authenticating”, “Demographics”, etc). Every piece of data that is added to RequestManager — whether it be an uploaded file, data imported via API’s, or data that is entered manually — should be assigned at least one Data Tag.  When a Requestor requests his data, they will choose what types of information they would like to request based on a list of Data Tags.  When the company receives the Data Request, they will see the list of Data Tags representing the types of information that the customer has requested.  The person processing the request will need to add all records and files with matching Data Tags.
Categories	Used only on the company side to group form Templates and Records together in a way that makes them easier to find. When choosing Templates from the Template Wizard, they will be grouped according to categories.  When finished, the Templates will now appear under Settings > Templates using the same categorization.  Also, when processing a Data Request, the Templates and Records relevant to that request will appear using the same categorization. Editing or deleting categories will never delete forms, or make them available or unavailable in a Data Request, or impact them in any way other than how they are grouped on the page.  Data Requestors will never see or be affected by Categories.
System Owner	The person who has created the account. The owner is also always an administrator. Ownership (incl. Administrator) can be transferred to another named person. There will therefore always be an Owner (and an Administrator). This secure that we will never be in a “dead-lock”
System Administrator	The person(s) that is the system administrator (setup, user management) There can be more than one Administrator
System Manager	The person who setup system-functionality – and templates/input forms. Apart from this a System Manager are able to perform the same tasks as a System-user
System User	The person who process incoming requests and creates responses System Manager – The person who setup system-functionality – and templates/input forms. Appart from this a System-manager are able to perform the same tasks as a System-user
Consumer	Requesting and receiving data.
API	These are used for development or data collection.
General availability	This general availability for the RequestManager online Services as described in the SLA
Registered user	All users registered on the company side in RequestManager
License	This is the fee
Consumption
Free Version	The RequestManager Free version will give you 31 days to try all our Professional version’s features, then we’ll contact you to check if you’d like to just continue with a more basic free version, or upgrade to keep all the features of our Professional version.
Renewal terms
Customer Data	Is defined as all data that is collected in an incoming request in RequestManager, and sent to the requester
Data Requester	Is an individual that has sent a data request OR the individual that has given consent that data can be requested on his/her behalf
Data Recipient	Is the individual or organisation that will receive the data.
Consent	Is an explicit sanction that the data requester has given for the data to be sent to him/her or the data recipient
SLA	Means the commitments we make regarding delivery and/or performance of an Online Service, as published at xxx xxx, or at an alternate site that we identify.
Request owner	A system user can be a request owner. This happens when he/she is assigned to an incoming request. The ownership of a request can be passed on to another system user if needed
Request Approver	A Request Approver is a Registered user that is assigned by the administrator or by the Request owner, to ensure that the customer data that has been added to the request is correct and sufficient before sending to the data recipient