I'm creating a new Bot with Amazon Lex.
I created and Intent, and a new Slot for it.
I now want to delete it or rename it, is there any way to do this?
To edit the slotName: left click on the colored slot name to begin editing.
To delete a slot: left click the circle with an X on the far right of the slot row.
Jay have written answer on how to remove the slot from the current intent, however it will not delete that slot permanently, which means if you want to use it again it will use same old slot which you made.
To delete the slot permanently, got to Slot types
then click on Actions and select Delete
This will permanently delete the slot from your console.
Related
So, a project that I am working on requires the custom column/silo of 'ready' to indicate that the initial analysis has been done and it ready to be picked up as a development object. When I change the state of an user story to 'ready' it does not show in the appropriate column however when selecting another such as 'new' or 'active' it is displayed. Is there a word restriction on the use of 'ready' as a column (silo)?
Please make sure you have also configured the state mapping for your customized Ready column. Otherwise, if you change the state of work item it will not auto show in the appropriate column.
More detail about this you could take a look at our official tutorial Update Kanban column-to-State mappings
I'm making an app for authors using Filemaker. I posted this question on their forum but still haven't gotten an answer.
My app is basically a place where people can keep track of all the details that go into creating characters and locations. In each book (record) I have a tab control with 4 tabs: Book Details, Character List, Location List and Group List. Within the character list tab I have a portal which shows a list of the characters for that book.
I'm trying to create a button for each row in the portal which takes me to that records details page (the one with the red box around it). Right now, it's set to go to the character details layout. However, whichever row I click on, it takes me to the last visited record. Is there a way to go to each row's record from the portal? If not, do you know of a way to do the same thing through another method? I have a list layout which I used before, however, it doesn't hide the records for different books. For example, if I select book 1, it still shows characters for book 2. Thanks in advance for any help you can give me!
Create a button, attach a script or single command that uses the Go To Related Record script step using the same relationship as the portal.
Make sure the button fits within the row.
I've been looking around everywhere but all I can find is deleting a Zone though the Field Names stay. The only other way I found was you have to log into the CloudKit dashboard and do it manually. Is this the only way?
Thanks in advance for your help.
You must use the Dashboard to make any changes to your schema. It is not possible to modify the schema programatically.
Making schema changes is something you only need to do during development, and the schema is created on demand, so there's no need for client side API to manage the schema.
You don't need to send every possible field when updating a record, so you can just stop using the field you want to delete and clean it up later in the dashboard.
I've just started in FM 14. I have a client table and a project table. When I look at a client entry I have a portal that shows me the titles of the projects they have commissioned. I'd like to be able to click on one of the projects in that portal list and be taken to the layout that contains all of the other fields in that project record. Can this be done? Is this enough information?
Yes. Set the button action as a script step "Go to Related Record". In this script step, set the table as "projects" and select the layout you would like to go.
I would stay away from GoToRelatedRecord. I usually just grab the ID from the item in the portal, then search for that item on a new layout, then do whatever I planned on doing. It's safer. With GoToRelatedRecord you can never really control what happens.
I'm working on an application using Play 2.0.4 in Scala, and one of the features I was asked to implement is to build a form that remembers all of the edit history. Basically, there should be a button next to every field that shows the details of every change, because the app users may want to rollback or use the edit history information later.
The first idea pops up in my mind is to assign a hidden div to every field that appends every change, and only shows the div when users click on the corresponding button. This doesn't sound very hard, but I feel like it may make the HTML a mess (since each user has his own record, each record has many fields). Or I could make a copy of the database and store all the changes inside, with the primary keys changed to be both the id of the form, and the edit time.
Thoughts? Am I overthinking the problem? Is there a more elegant way to store all of the edit history? We estimate that there would only be around 200 people in the company using it, so I guess I can let efficiency slide a little...
Thanks in advance.
I would normalize and persist the record in the database. This would allow you to have history on changes by having a history table for each section that they with to rollback.
This would allow manageability of restorations based on sets of data and significant changes can be tracked. Managing each field separately would be very cumbersome and least pragmatic.