Delete "save" button when creating new customer

so here is my question is there a way to just show the “create account” button instead of with the option “save” when creating a new customer cause everytime my waiters click “save” but then are baffled that they cant credit the client this would all be resolved if it just showed “create account” only when its a new customer.

i tried it with custom screen but that only lets me customize the search screen not the creating new customer account screen

Probably not in the way you describe, at the point your entering new entity details that entity doesn’t actually exists untill you save so there is no info the create the account for.
You would probably be best to look at a way to automatically create account when entity saved for entity selected where an account is not created…

You could build your own automation and use this:

tried it, but it doesnt work probably cause i have required “custom data” that needs to be filled in to :confounded:

You did notice the Custom Data field right? Its above Create Account.

yes i did but i need the custom data to be different every time

OK so enter different custom data? You can use [?prompt] there and it will give you a prompt for custom data allowing you to enter whatever you need.

or you could be extravagant and create an account by using the ‘Ask Question’ action :smiley:

(i love this action!)

hi thx for the help and srry for the late reply, so i tried the [?prompt] but it still doesnt work any ideas why it isnt working


here are all the settings i used


Use variable in the action and then use that prompt in the rule.

sorry didn’t quite get that :sweat_smile: (feel really stupid at this point) so do i need to put “variable” in the custom data field??

Use something like [:Custom Data] in the action… then in the rule where you have that action put [?Enter Customer Info] Into the action.

Using [:Variable Name] in actions allows you to define what goes in the action via the rule instead of hardcoding it into the action. In fact some functions can only be read into actions like that. As an added benefit it lets you create actions once and you can use them in multiple rules.

oh k i think i follow now so in the rule where it selects the action the constraint should be (in my case):
[?numero client] and in the rule it self it should be [:numero client]?

No there shouldnt be a constraint… let me show you.

I create a simple action Show Message and for Message parameter I use the variable [:Message] It could be anything like [:John Doe] or [:Variable for Message] etc.

Then in the rule I want to use that action I insert the action and expand it. You will see a new parameter named whatever you used for the variable in the actual action. This new parameter is where you enter your [?Blah] expression.

That is what an action Variable does. Maybe now it makes more sense to you. Using variables in actions can also significantly reduce the number of actions you use since you can effectively create generic actions and use them for multiple automation.

It lets you pass rule values etc into the actions parameters.

thx that clarifies alot will test it right away :wink:

so did all that it shows message but it still doesnt create account did i miss something up here


here i enter the acount name and tap the button that should create the new account


now it pops up the message like we wanted
it then shows this message when pressed ok but doesnt create the account


here are the rules and actions i used



is there maybe something i still missed :confounded:

Oh geeze you took me all wrong. I did not mean for you to use Show message … that was an example… and you still did your action wrong. I just used show message action as an example… I meant for you to use the process in your Create Entity action.

lol feel so stupid right now :sweat_smile:

On the plus side you got it to work with Show Message lol.