hasadna/reportit-script-builder

Chatbot editor for ReportIt

reportit-script-builder

Chatbot editor for ReportIt

Development

Open /webapp to see more

reportit-script-builder's Issues

Split "Infocards", "Organizations", "Task Templates" content (and editing) into separate tabs

create a separate view (and a radio button) for each of the following data types:

• info cards
• organizations
• task_templates

each of them will be edited on a different view (outside of the agent view).

add in-script navigation

@akariv as a first exercise, let's add:

1. a quick jump link, from any goto block:

2. Ofer already implemented a referral 'back' link on each block, but instead of showing the concrete referring snippet name, the label shows the type of the referring block:

Please fix the label to "referring from: [snippet name]"

3. Split "Infocards", "Organizations", "Task Templates" content (and editing) into separate tabs:

4. a side navigator, listing all snippets with a color indicator for the active/on focus snippet (will be handled seprately on #23).

can't add first relevant scenarios to an organization

when trying to add a first relevant scenario block to an organization, nothing happens, except for the following console.log message:

see justice_ministry_admission_committee (slug) for example.

Block view scrolls all the way to the top after returning from YAML view

A common behaviour is to take a peek in the YAML view to ensure that the script looks like what we wanted.

However, when going back to block view it scrolls back to the top, making it difficult to find our way back to where we were editing beforehand.

improve task-template block editor

reorder fields:

1. title: should be a mandatory field
2. slug: should be a mandatory field
3. description
4. Infocard slugs

improve relevant scenarios editing for never/general org display

script editor should be more explicit regarding the scenarios in which each of the organizations shown/used.

1. fix first button label to "הצגת הארגון לפי מאפייני פניה"
2. add new button: "הכללת הארגון בכל סוגי הפניות" (this will ensure the organization to be included in all automatic loop functions.

notice that clicking on each of these buttons should cancel the other one functionality. This can be shown to the user in (at least) two ways:

a. include a small 'V' indicator if one of the buttons was clicked and turned on
b. add a scenario block if the 2nd button was clicked (something like {script: all}. This will be automatically deleted when the first button is clicked.

improve organization block editor

reorganize the fields order in the from:

1. name: should be a mandatory field
2. slug: should be a mandatory field
3. description
4. organization type: turn into a select list: ארגון חברה אזרחית, יחידה ממשלתית, יחידה ממשלתית רוחבית לתיאום
5. contact person 1
6. email 1: should be validated being either empty or an email address
7. phone 1: should be validated being either empty or a phone number
8. contact person 2
9. email 2: should be validated being either empty or an email address
10. phone 2: should be validated being either empty or a phone number
11. phone response details: turn into a multi-line input field
12. Reception details: turn into a multi-line input field
13. mail address
14. Website url 1: should be validated being empty or a URL
15. Website label 1
16. Website url 2: should be validated being empty or a URL
17. Website label 2
18. scenarios

remove the field Scenarios Relevancy

scripts validation, pre-publish

List of checks to run and block users trying to save/publish a script with illegal parts. I believe these validators should be checked over the YAML, after clicking on publish(hasadna/reportit-scripts#15) , showing an explaination for the deploy failure, when relevant:

1. user is trying to save the value to a variable that is never being called/mentioned later.
2. user is trying to save a value to a constant variable (report field) name that does not exist.
3. script includes a goto points to a nonexisting block name
4. user is trying to create a temporary variable name (represented on YAML with _) with a constant variable name (field record name).
5. user is trying to create a temporary variable name (represented on YAML with _) with a saved word: (i.e. 'do', 'goto', etc.).

scenario blocks layout to horizental

change scenario blocks layout to horizontal arrangement instead of the current vertical layout. Notice to keep the indentation.

Can't insert blocks in the middle of a script

If I want to add a block in the middle of an existing script, it's not possible at the moment.

Two options for implementation -

• Allow adding only in the end but enable reordering of blocks (e.g using drag and drop or a set 'move up/move down' buttons)
• Allow adding inbetween blocks - e.g. when hovering on the space between existing blocks show a 'add new block here' button

fix the label to "referring from: [snippet name]"

Ofer already implemented a referral 'back' link on each block, but instead of showing the concrete referring snippet name, the label shows the type of the referring block:

Please fix the label to "referring from: [snippet name]"

(originally published on #21)

add in-script orientation side panel

show on the side an indication to the current view/scope of the general script. Being able to navigate through this pane would be a nice feature, something like this:

Give adam and noam admin access to app's firebase console

imrpove infocard block editor

turn the content field into a text-area field:

also, title and slug should be mandatory fields

add a quick jump link, from any goto block

(originally published on #21)