Projects:Single Record UI Pattern/Functional Specifications

Contents 1 Single Record UI Pattern - Functional Specifications 1.1 Overview 1.1.1 Purpose 1.1.2 Scope 1.2 Functional Requirements 1.2.1 User roles & profiles 1.2.2 Functional requirements based on business processes

Single Record UI Pattern - Functional Specifications

Overview

Some tables should be updateable by the user but only the existent record(s), users should not be able to create or delete them. These records are created somehow by other processes.

Purpose

Currently this pattern is not supported by WAD, the purpose of this project is to support it.

Scope

Once the pattern is implemented it will affect the tables which should not allow to create or remove records, this includes heart beat, client and organization information.

Functional Requirements

User roles & profiles

System Administrator role will make use of this pattern which will be applicable at a table level.

Functional requirements based on business processes

Requirement	Importance	Status	Estimated time
Implement Single Record UI Pattern in WAD	Must have	To be started	2d
Look for the existent tables in the dictionary that should follow this pattern and apply it.	Should have	To be started	4h