This commit is contained in:
2020-04-07 23:59:14 +00:00
parent 91cde6c798
commit 07451c5318
2 changed files with 4 additions and 8 deletions

View File

@@ -4,13 +4,6 @@ SEARCH SPECS
CASES
//NOPE: this one deprecated to priority 2, not really required and may be problematic
//SEARCH: - to have ability to filter by client
//https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1503
SEARCH:UI:GENERAL: - Search in V8: should be integrated, not a separate form
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1672
SEARCH:NEW: - Search dictionary: Auto remove orphaned words
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1878
@@ -41,6 +34,7 @@ REQUIREMENTS
- ? USE-CASE: In-object text search for the typeandid that user is in, e.g. when in Client info form can search on that client.
- This is problematic because it seems to require searching for related objects but that's deprecated to priority 2
- Maybe more ideally is a search that can be something like "search all workorders FOR THIS CLIENT" or search all units "FOR THIS CLIENT"
- UPDATE: For the above this is really a feature specific to this object, not a general search issue so not part of search at all
- USE-CASE: Picklist / chooser Search for text of a specific type of object, e.g. find all Clients that contain "squirrel" to drive picklists everywhere
- USE-CASE: No snippet (excerpts) just name and type. I think for the initial release I'm *not* going to include snippets with result for several reasons:

View File

@@ -41,7 +41,9 @@ todo: Server ops EMAIL address for server to send health messages to!!!!
DO CLIENT STUFF NOW COME BACK TO THIS STUFF LATER
todo: add a post backup maintenance job (or very long periodic built in job that rarely runs) which does the following:
SEARCH:NEW: - Search dictionary: Auto remove orphaned words
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1878
*** BEFORE NEXT UPDATE TO DEVOPS SERVER:::::::
TODO: 2019-06-07 10:47:57.8894|WARN|Microsoft.AspNetCore.Cors.Infrastructure.CorsService|The CORS protocol does not allow specifying a wildcard (any) origin and credentials at the same time.