From 461bbed2ec2c846814be730188229e65509e0fb4 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 24 Nov 2021 00:41:30 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 7cecdaf2..df4565aa 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -16,14 +16,9 @@ - - - -Currently doing global settings doc page - - - -todo: cases for csr and for wo +todo: Look into past features and cases for csr and for wo find anything missing or want to include now + https://www.ayanova.com/RI7ClientwebHelp/index.html?how_to_csr.htm + https://ayanova.com/WBI7ClientWebHelp/index.html?service_request_grid.htm add units?? Only if trusted?? v.next feature?? maybe just focus on replicating what was already there before? I'm kind of digging hiding the status and shit because that could be internal and they can see it in the report anyway so...?? @@ -46,6 +41,9 @@ OUTSTANDING MAJOR AREAS TO BETA v8Migrate completed trial / seeder system docs + See Global Settings form for format for all feature pages + MOST IMPORTANT is the basic stuff about how to use forms and controls and stuff before getting into actual feature pages + this is because beta testers and users will probably already know about each object so the first thing is to get them going with basic usability docs if prioritizing - Has pertinent cases - ROLES need a completely full documentation or some way to view what is accessible for what maybe in code in the UI??? There is no clear ROLES guide and we need one for sure. I like the idea of dynamically generated in the UI so we can change it and it's always accurate and