Daily-Dev-Notes

Daily-Dev-Notes-Old

Horizon (Next)

⁠

Table & Field Selection Control⁠

⁠

Form Sidebar Links

Reports

Charts

Short Term Objectives

Ability to do all of the basic Form-Customizer functionality

Configure Sidebar Links

Create Form

Edit Form Properties (Single & Multi-Rec)

⁠

Test Links

⁠

https://localhost:7295/form/106/3/parent/3⁠

⁠

https://localhost:7295/form/field_add/906⁠

⁠

Add Field to the “Test Field Types Table”

⁠

Loose-Ends to Finish & Dependencies

Sidebar-Items - Programmatic Control & Built-In Options

Bug: Devs should be able to modify all of the fields on the "Field Properties"

https://localhost:7295/form/field/100/rec/100061

Options/Sidebar-Links Manager

Setup the Add/Edit Sidebar Form

Custom Gen Form OR We could try to do as a View

But the Selection of which Form, Report or Template is tricky

Setup the TableElement and DataTableElement Control

for showing the “List-Overview” style

since the List-Overview and Sidebar-Links Manager will be the same

(ideally with the Pagination so that only shows 100 items max)

Sidebar Links Service (Programmatic Control)

When we Navigate to a new page that is not a view, we need to have the Options (”SidebarLinks”) reset

otherwise it will just keep it from the last one

“Customizer” Built-In Sidebar links (as a sub-menu)

(Or do we have a “Customizer-View” where we show the field types instead since we could be doing it where we don’t have a record yet!)

“Add Section”

“Add Field” ?

“Form Properties”

“Sidebar-Links”

“Customizer Modification History”

Bug - “Add Field” to Section isn’t adding it in the right order

Also, its allowing duplicates

When we have the “view_id” then we should be able to get the existing ones for the view and exclude them

Gen-HTML - views.“hint” at the top of the form

⁠

Directory-Functionality

The Directory is “group” based, so we use their “default-group” if there isn’t a “group_id/key” passed in via the QS.

Permissions: The “directory-users” don’t have access into the main system, so when they login, it checks for this “is_directory_user” (or “user_type_id”) flag and if so then will redirect them to their “default_group_id” unless there is a “group_id” in the QS when they login, like when they are coming from an email about it (but in those cases, we should be sending them to the “group activity page” or their own profile page so that they can update it.)

Group Creation:

Groups are a “Contact” (since they have all of same social fields, just like an “Org”)

so we have to setup the “contact_type_id”

persons

orgs

groups (essentially an Org, so only separate type so we can make it easier to show different forms for each of them)

see #cover-page functionality which allows us to configure a different form to use per contact based on a filter (maybe just list-attribute for “contact_type” list)

Banner

so we have to allow regular people to have their banner image too

Requires that the user has the permission to “Create Groups”

since this is a premium/paid feature

“Groups”

(”Relationships” Table)

Invited-Date

Started-Date

Ended-Date

Why-Joined/Started

Why-Ended

is_active

(the main key to whether they can still access it)

General Memo

group_permission_id

Invite/Add User Form

(Main switch is between the “is_directory_user” vs internal users)

name

group

if the person is an admin of multiple groups

otherwise it default to the adding users “default-group”

(if they are adding )

“group_permission_id” permission level (when “is_directory_user”)

“Full-Admin”

“Regular User”

memo

ideally if it was completely private

like on the “user” table

so the user never sees it

like “why full-admin” or why was invited

Creates the “relationship” rec

with the invited-date and invited-by

User-Invite-Accept form

(Similar functionality as the Password-Reset)

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.