Is there a way of saving referenced records automatically.
To create a job I have to
Create a customer
create a bike(to be repaired)
create a job
add items
then press save, save, save, save.
Can the saving process be streamlined?
You could look at reducing the number of subtables if you donโt need a one-to-many relationship
Other than that the only other thing to look art might be a detailed view with editable columns.; But that would only benefit updates to records.
The KPI that I measure my apps against is this - Do I have to enter the same information any more than once, anywhere? If so then that needs imporving.
Hope this helps
They are almost all new records and I am only entering the same info once - but customers own multiple bikes and bikes have multiple jobs.
Something to considerโฆ
Sometimes if itโs a workflow thing you can get pretty craftyโฆ So you just spelled out your workflow for a new customerโฆ So execute that with actionsโฆ Conditionally change the save button to โnextโ or even better โadd bikeโ โadd jobโ then use navigation actions set to on save of the formโฆ Something like a LINKTOFORM can go miles hereโฆ Then you have a special starting view, on probably itโs own sliceโฆ Titled โNew Customerโ
Then basically, after youโve put in the customer details, you would be hitting next, which makes more sense, and kills the inception, also you can cancel the workflow at anytime to bail, while still having had added the customer and their first bikeโฆ I would setup the initial add assuming 1 customer, 1 bike, 1 job w/ multiple itemsโฆ Then you could always go back and add more bikes and jobs after the initial add workflow
That perfect cos its like real life, but its going to challenge my basic skills. I am already stuck on the first bit - [quote=โGrant_Stead, post:4, topic:12170โ]
Conditionally change the save button to โnextโ or even better โadd bikeโ
[/quote] How?
CONTEXT(VIEW) tells you the view nameโฆ
Then in the localization tab, add in your expression. IF context then โadd bikeโ else โsaveโโฆ If you have quite a few then use SWITCH
Sorry you have to be more basic. How do I change the โsaveโ button? Where do I put the expression?
@sales_bikefix Hereโs a video of me muddling it all upโฆ
Thats really the last thing you should doโฆ
The first is to create a set of custom views position REF for that business process, BPโฆ You can create those form views Customer_BP_Form, Bike_BP_Form, Job_BP_Form, etcโฆ
Customer_BP_Form might be a menu view cause that kicks off your business process, and give it cool display name, โNew Customer w/ Jobโ So then when a user clicks that in the menu it will start them out on Customer_BP_Form. That can apply to the localization for the save button.
For the next layer, when you โsaveโ that Customer_BP_Form it actually needs to kick off a navigate action, LINKTOFORM, to Bike_BP_Form, pre-populated with the customer ID in the bike_REF_customer fieldโฆ
Phew! Do you have to do all that in a slice? Is that so you can limit the fields in the input forms? Where do you put the LINKTOFORM? Are these in the actions or the workflow?
You nailed the process. This is exactly what I have to do.
The final link in the chain is the items - When I add an item to the job details form I need to be presented with a drop down for โcategoriesโ which then filters the items in the next drop down, as there are hundreds of them. I have been trying to do it with a VC that reads all the category fields but it doesnโt work or I just donโt know the syntax.
Have you got more videos out there?
I am also thinking a whole new BP for existing customers which takes you from finding the customer, straight to create a new job for the existing bike.
Had a frustrating time with this until I read โForm Saved action is only applied in top level formsโ.
Its OK I can still use the process but not with a slice, which means I have to have all the default fields in the form.
Well, with this new method you shouldnโt have any nested forms that need a form save navigate action.
Youโre statement is misunderstood I think. When you mark a record as IsAPartOf, and then while youโre filling out a form, you can jump right into child records to add themโฆ Thatโs what you WERE doing. We blew that up, and now youโre doing navigate actions, so you need to recycle and kill those so that you donโt even see themโฆ
Also, you could have an initial view that is actually a gallery view of your business processโ that when that you can apply an โOn Record Selectโ action to navigate to the kick off form. Pretty cool way of doing it.
Of course all of this is some pretty advanced stuff. Also you can use that context function to show/hide various columns, etcโฆ
User | Count |
---|---|
37 | |
30 | |
29 | |
22 | |
18 |